Pb running on a Mac (sed errors + failure to detect the distribution) about rez HOT 10 CLOSED

Hey sorry I think I've been referring to sed the wrong way around -
standard Linux sed is GNU, whereas osx is BSD. Rez works with GNU-sed but
not BSD-sed. Just clarifying.

A

On Wed, Aug 14, 2013 at 3:18 PM, bsergean [email protected] wrote:

So with the init.csh and the mktemp fix I'm a little further, but now that
I'm doing real stuff it fails. I can now see the GNU sed errors, I'll try
to see how to debug them, and see if something easy can be done to detect
the distribution

panzani rez$ uname -a
Darwin panzani.local 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64

panzani rez$ uname -a | awk '{ print $3 }'
12.3.0

Errors below.

[venv] panzani rez$ ./examples/demo/run_demo

INSTALLING REZ LOCALLY...

Detecting operating system...
Operating system is: Darwin

detecting shell...
Shell is: tcsh

detecting OS distribution...
Could not identify OS distribution - either specify manually in configure.sh, or set $REZCONFIG_DISTRO
Setting to DISTRO_UNKNOWN-0!

detecting cmake...
found cmake binary: /usr/bin/cmake

detecting cpp compiler...
found cpp compiler: /usr/bin/c++, id: GNU
cpp compiler version: 4.2.1

detecting python...
found python binary: /Users/bsergean/src/rez/venv/bin/python
python version: 2.7.2

detecting pyyaml...
found pyyaml at /Users/bsergean/src/rez/venv/lib/python2.7/site-packages

detecting pydot...
found pydot at /Users/bsergean/src/rez/venv/lib/python2.7/site-packages

detecting pyparsing...
found pyparsing at /Users/bsergean/src/rez/venv/lib/python2.7/site-packages

There were 1 issues, please review above. Note that installation has still succeeded.
rez.configured written.
Now run ./install.sh

rez 1.6.9 installed successfully.

READYING TEST PACKAGES...

sed: -e: No such file or directory
sed: -e: No such file or directory
sed: -e: No such file or directory
sed: -e: No such file or directory
sed: -e: No such file or directory
sed: -e: No such file or directory
sed: -e: No such file or directory
sed: -e: No such file or directory
sed: -e: No such file or directory
sed: -e: No such file or directory
sed: -e: No such file or directory
sed: -e: No such file or directory
sed: -e: No such file or directory

BUILDING TEST PACKAGES...

BUILDING: hello_world_py-1.0.0

rez-build: invoking rez-config with args:
--time=1376457195
requested packages: python-!PYVER!
package search paths: /Users/bsergean/src/rez/examples/demo/build/published_packages
Invalid version: Invalid version '!PYVER!'
rez-build failed - an environment failed to resolve.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/24
.

from rez.

Ok. The sed errors I'm seeing when running run_demo should be easy to fix. It looks like BSD sed does not support the -i (replace in place) flag. I'll just create a tmp file ; I'll submit a patch soon.

from rez.

I got the full ./examples/demo/run_demo to run and complete nicely :)

from rez.

from rez.

Great news! This week I'll be rolling everything up to head. It'll take a
few days though, there are two different branches of development to merge
now and I need to do a bunch of integration testing. Rally wish I'd written
some unit tests now :P

I'd also like to get onto a feature I've been wanting to implement for
ages... A new version sub module, separated out from Rez and available as a
separate python library. This would bring full alphanumeric versioning
support to Rez, as well as ironing out a few ambiguous edge cases.

Thanks again for the mac port, looking forward to getting this all merged.

Cheers
A

On Sunday, August 18, 2013, bsergean wrote:

I got the full ./examples/demo/run_demo to run and complete nicely :)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/24#issuecomment-22821024
.

from rez.

Sounds good. I'll be very happy too if what I coded manage to get integrated ! I think
you'll be able to tweak the README and say that Mac really works :)

I have one thing to cleanup where I changed sed to gsed (the GNU sed I installed on my box)
but I could do a python trick here. This is to removing trailing - I think to get the unversioned name
for a package (this was my "long-standing" issue)

The one where I'm not sure is a sed -i which is invoked form a CMake file.

The last thing I should investigate is why I had to manually install python;

Cheers !

• Benjamin

On Aug 17, 2013, at 4:14 PM, allan johns [email protected] wrote:

Great news! This week I'll be rolling everything up to head. It'll take a
few days though, there are two different branches of development to merge
now and I need to do a bunch of integration testing. Rally wish I'd written
some unit tests now :P

I'd also like to get onto a feature I've been wanting to implement for
ages... A new version sub module, separated out from Rez and available as a
separate python library. This would bring full alphanumeric versioning
support to Rez, as well as ironing out a few ambiguous edge cases.

Thanks again for the mac port, looking forward to getting this all merged.

Cheers
A

On Sunday, August 18, 2013, bsergean wrote:

I got the full ./examples/demo/run_demo to run and complete nicely :)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/24#issuecomment-22821024
.

—
Reply to this email directly or view it on GitHub.

from rez.

OK the last gnu sed pb I had was inside a CMake file where sed was used to
uppercase something. I think I can do something like that to solve this.

execute_process(
  COMMAND cat "/tmp/lowercase"
  COMMAND tr "[:lower:]" "[:upper:]"
  COMMAND tee "/tmp/lowercase"
)

from rez.

I tried very hard but couldn't get this to work. I wonder if someone other than me could see that one.

I also tried to use perl which is kinda more portable (behaves the same way on mac + linux and comes as a default on both but I couldn't get the escaping in CMake to work.

perl -p -e 's,(\w),\U$1,g;' /tmp/lowercase

from rez.

I just tested the merge_osx branch today by running ./examples/demo/run_demo on a fresh checkout of the code and it's working perfectly on my Mac :)

from rez.

Works nicely in the osx branch, closing.

from rez.