-C flag required for RVM Ruby installation on Mac OS X 10.7.4 #1039

Closed
andrewjl opened this Issue Jul 4, 2012 · 7 comments

Comments

Projects
None yet
3 participants
@andrewjl

andrewjl commented Jul 4, 2012

If I type in the following to install Ruby 1.9.3

rvm install 1.9.3 --with-readline-dir=$rvm_path/usr

I get these errors:

clang: error: unsupported option '--with-readline'
clang: error: unsupported option '--with-opt-dir=/Users/andrewjl/.rvm/usr'

However all is well when I do this:

rvm install 1.9.3 -C "--with-readline-dir=$HOME/.rvm/usr"

It was pointed out to me by Remear that it's a bug to require, so I am bringing it to the attention of RVM group.

Here are my system details:

rvm 1.14.3 (master)

Apple clang version 3.1 (tags/Apple/clang-318.0.61) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin11.4.0
Thread model: posix

andrewjl$ /usr/bin/gcc -v
Using built-in specs.
Target: i686-apple-darwin11
Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2336.922/src/configure --disable-checking --enable-werror --prefix=/Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2 --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin11 --enable-llvm=/private/var/tmp/llvmgcc42/llvmgcc42-2336.922/dst-llvmCore/Developer/usr/local --program-prefix=i686-apple-darwin11- --host=x86_64-apple-darwin11 --target=i686-apple-darwin11 --with-gxx-include-dir=/usr/include/c++/4.2.1
Thread model: posix
gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.9.00)

See here for addt'l details: http://stackoverflow.com/questions/11249711/ruby-1-9-3-installation-not-working-due-to-clang/11255314#comment14902058_11255314

@ghost ghost assigned mpapis Jul 4, 2012

@mpapis

This comment has been minimized.

Show comment Hide comment
@mpapis

mpapis Jul 4, 2012

Owner

both options are supported by rvm and are passed to ruby where they are parsed by gnu gcc,

the issue here is you are using clang, it is not yet fully supported, it looks like this should reported to MRI developers. I'm sorry you had to do additional reporting here.

as for the option it's interesting why it works with -C, could you provide rvm --trace ... for both commands?

Owner

mpapis commented Jul 4, 2012

both options are supported by rvm and are passed to ruby where they are parsed by gnu gcc,

the issue here is you are using clang, it is not yet fully supported, it looks like this should reported to MRI developers. I'm sorry you had to do additional reporting here.

as for the option it's interesting why it works with -C, could you provide rvm --trace ... for both commands?

@jasperf

This comment has been minimized.

Show comment Hide comment
@jasperf

jasperf Jul 14, 2012

I just compiled 1.9.3 with RVM using clang to make the compiling work on OSX 10.7.4 Lion and I did get this error clang: error: unsupported option '--with-libyaml'running rvm install 1.9.3 --reconfigure --debug -C --enable-pthread --with-gcc=clang. It did built and wpscan worked with it with only a small hickup Nokogiri was built against LibXML version 2.7.8, but has dynamically loaded 2.7.3 and I see update_terminal_cwd; all the time now. And when I change directory I see bash scripts: http://pastebin.com/UAm38Vcm

jasperf commented Jul 14, 2012

I just compiled 1.9.3 with RVM using clang to make the compiling work on OSX 10.7.4 Lion and I did get this error clang: error: unsupported option '--with-libyaml'running rvm install 1.9.3 --reconfigure --debug -C --enable-pthread --with-gcc=clang. It did built and wpscan worked with it with only a small hickup Nokogiri was built against LibXML version 2.7.8, but has dynamically loaded 2.7.3 and I see update_terminal_cwd; all the time now. And when I change directory I see bash scripts: http://pastebin.com/UAm38Vcm

@mpapis

This comment has been minimized.

Show comment Hide comment
@mpapis

mpapis Jul 14, 2012

Owner

@jasperf your issue seams unrelated, it looks like shell issue, please open a new ticket, btw. you are using clang - see my above comment regarding it.

Owner

mpapis commented Jul 14, 2012

@jasperf your issue seams unrelated, it looks like shell issue, please open a new ticket, btw. you are using clang - see my above comment regarding it.

@andrewjl

This comment has been minimized.

Show comment Hide comment
@andrewjl

andrewjl Jul 14, 2012

I went ahead and installed 1.9.2, here's the trace: https://gist.github.com/3113867 and here;s the trace of an unsuccessful 1.9.1 install: https://gist.github.com/3113876

I went ahead and installed 1.9.2, here's the trace: https://gist.github.com/3113867 and here;s the trace of an unsuccessful 1.9.1 install: https://gist.github.com/3113876

@mpapis

This comment has been minimized.

Show comment Hide comment
@mpapis

mpapis Jul 14, 2012

Owner

@andrewjl can you provide gist of full output of rvm install 1.9.3 --with-readline-dir=$rvm_path/usr - it seams that clang was picked instead of gcc-4.2, which would explain the warnings, the issue seams to be hear picking clang.

Owner

mpapis commented Jul 14, 2012

@andrewjl can you provide gist of full output of rvm install 1.9.3 --with-readline-dir=$rvm_path/usr - it seams that clang was picked instead of gcc-4.2, which would explain the warnings, the issue seams to be hear picking clang.

@jasperf

This comment has been minimized.

Show comment Hide comment
@jasperf

jasperf Jul 15, 2012

Yeah, I read some more and discussed some more on Stack Exchange. Was more of a Shell issue than a RVM issue. Thanks for this great tool!

jasperf commented Jul 15, 2012

Yeah, I read some more and discussed some more on Stack Exchange. Was more of a Shell issue than a RVM issue. Thanks for this great tool!

@mpapis

This comment has been minimized.

Show comment Hide comment
@mpapis

mpapis Jul 28, 2012

Owner

closing as there was no response in two weeks, I will reopen if/when there is still something to do.

Owner

mpapis commented Jul 28, 2012

closing as there was no response in two weeks, I will reopen if/when there is still something to do.

@mpapis mpapis closed this Jul 28, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment