Re: [Swig-user] Undefined symbol for architecture i386 on linking SWIG C++ Wrapper Object for Ruby compiled with -m32 option

[jwilson <jwi...@gm...>]

In this case, it turns out that the problem was that Xcode had installed a
64-bit version of Ruby and put it on the system path. In order to resolve
the issue, I had to explicitly specify the path to the 32-bit version of the
Ruby binary on the link line:

/g++ -arch i386 -shared -fPIC -o ../lib/cppexample.so
./bin/CPPExampleWrapper.o
../qa_cpp_utils/bin/CPPExampleObject.o
../qa_cpp_utils/bin/CPPExampleCallbackFunctor.o
../qa_cpp_utils/lib/libcppexamplearchive.a -L/PATH/TO/32BIT/RUBY -framework
CoreFoundation
-lpthread//


This was not a problem in Linux, because the version of Ruby on the system
path was built for the architecture being linked.

- James



--
View this message in context: http://swig.10945.n7.nabble.com/Undefined-symbol-for-architecture-i386-on-linking-SWIG-C-Wrapper-Object-for-Ruby-compiled-with-m32-on-tp13093p13136.html
Sent from the swig-user mailing list archive at Nabble.com.