On Mar 10, 2012, at 10:37, Phil Dobbin wrote: > Regarding this problem, again today I did some work using nodejs in a > shell which rvm had allocated as Ruby 1.9.3 (the value of `which ruby` > confirmed this before I started with node) & after finishing work on > node running `which ruby` returned /opt/local/bin/ruby. > > Nodejs is installed into /opt/local. > > Running otool -L on both Ruby versions returns: > > `[Sat Mar 10 16:29:15 dobbin@darkstar:~ ] $ otool -L > /Users/dobbin/.rvm/rubies/ruby-1.9.3-p0/bin/ruby > /Users/dobbin/.rvm/rubies/ruby-1.9.3-p0/bin/ruby: > /Users/dobbin/.rvm/rubies/ruby-1.9.3-p0/lib/libruby.1.9.1.dylib > (compatibility version 1.9.1, current version 1.9.1) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current > version 125.2.11) > /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version > 227.0.0) > [Sat Mar 10 16:29:35 dobbin@darkstar:~ ] $ otool -L /opt/local/bin/ruby > /opt/local/bin/ruby: > /opt/local/lib/libruby.dylib (compatibility version 1.8.0, current > version 1.8.7) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current > version 125.2.11) > /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version > 227.0.0)` > > If anyone could shed any light on what's happening here I'd be grateful.
Something that is unrelated to MacPorts is happening. Installing a MacPorts port only installs files into /opt/local. It does not touch your environment. Just running node or most other programs should not alter your shell environment either. I don't know how rvm works, but it sounds like it's fragile. I'd talk to the developers of rvm for insight. _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
