Bug #3353
closedBuilding 32-bit only on Snow Leopard (dylib failed to build)
Description
=begin
Okay, I know this isn't all THAT helpful, but I was trying to build ruby 1.9.1 on Snow Leopard, but 32-bit only. I had CFLAGS, LDFLAGS, CXXFLAGS, and DLDFLAGS all set to '-arch i386'
Everything would be fine, all *.o files would be built i386, but when it came time to create libruby.1.9.1.dylib, the -arch i386 flag was not present. I'm no autoconf genius, so I have absolutely NO idea how to patch this. But all I did was re-run the failing command and manually added the -arch i386 command, and it worked.
A minor point, but kind of annoying nonetheless.
I have attached the relevant output of 'make'.
=end
Files
Updated by shyouhei (Shyouhei Urabe) over 13 years ago
- Status changed from Open to Assigned
=begin
=end
Updated by randy_parker (Randy Parker) over 12 years ago
This bug continues to prevent 32-bit builds on OSX Lion in 1.9.3 preview1.
It blocks use of the 32-bit version of Oracle InstantClient, which is the only InstantClient that works on OSX 10.7 Lion.
Updated by naruse (Yui NARUSE) over 12 years ago
- Project changed from Backport191 to Ruby master
- Category changed from build to build
Updated by naruse (Yui NARUSE) over 12 years ago
- Assignee changed from yugui (Yuki Sonoda) to mrkn (Kenta Murata)
Updated by nobu (Nobuyoshi Nakada) over 12 years ago
- Status changed from Assigned to Feedback
Try --with-arch=x86_64 option.
Updated by nobu (Nobuyoshi Nakada) over 12 years ago
Sorry, it should be --with-arch=i386, of course.
Updated by randy_parker (Randy Parker) over 12 years ago
Do you mean just "-arch=i386" ? I have tried that as a directive in .rvmrc. It results in the build failure originally described by Bryan Ross. Replacing "-arch=i386' with '--with-arch=i386" as an rvm directive causes immediate build abort.
Where should the "--with-arch=i386" be specified if not in .rvmrc?
Updated by mame (Yusuke Endoh) over 11 years ago
- Status changed from Feedback to Assigned
"--with-arch=i386" should be specified in ./configure, I guess.
Mrkn, do you know the status of this issue? Do you think this issue should be fixed before 2.0.0?
--
Yusuke Endoh mame@tsg.ne.jp
Updated by mrkn (Kenta Murata) almost 11 years ago
- Status changed from Assigned to Closed
I maintain the CI for 32-bit OS X.
You can check the result of it in http://rubyci.org/