And like I hoped all gems are being build with the config that ruby was build with. So hpricot from macports and libxml from rubygems both build universal extensions :) So all the ports that are rubygems based, should they by default have: "universal_variant no"? Because they will be build in the same manner as ruby was build nonetheless. Eloy On 7/13/07, Eloy Duran <eloy.de.enige@gmail.com> wrote:
As you can see the differences start to occur from: "have_library: checking for SSL_library_init() in -lssl...". Which returns yes for /usr but no for /opt/local. Also it says this in the log for /opt/local: /usr/bin/ld: warning can't open dynamic library: /Developer/SDKs/MacOSX10.4u.sdk/opt/local/lib/libz.1.dylib referenced from: /opt/local/lib/libcrypto.dylib (checking for undefined symbols may be affected) (No such file or directory, errno = 2)
Uhmmmm..... Is this why it fails to build?? I mean that path can't be correct can it? But that path doesn't really seem to be in there so I don't think that's the cause:
$ strings /opt/local/lib/libcrypto.0.9.8.dylib | grep Developer cc -fPIC -fno-common -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -O3 -fomit-frame-pointer -fno-common -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386
Could anybody offer any tips on where I should look??? I'm so close, it's getting frustrating! hahahahaha ;)
The path /Developer/SDKs/MacOSX10.4u.sdk/opt/local/lib/libz.1.dylib is wrong, to be sure. It should be looking in /opt/local/lib/libz. 1.dylib. I believe I read that it means someone is interpreting the - isysroot parameter incorrectly, but I didn't get to the final solution. But if you search Google for the following two quoted strings you'll see many other instances of the problem.
"can't open dynamic library" "/Developer/SDKs"
Perhaps one of those threads indicates the solution.
http://www.google.com/search?hl=en&q=%22can%27t+open+dynamic+library% 22+%22%2FDeveloper%2FSDKs%22&btnG=Search
I think this one sums it all up: http://lists.apple.com/archives/darwin-dev/2006/Apr/msg00042.html
And guess what..... It builds yihaa! So thanks for the pointer.
But then this raises the question off how to accomplish this with macports. As in:
Should I create a symlink in pre-build like: $ ln -s /opt /Developer/SDKs/MacOSX10.4u.sdk/opt And then remove it in post-build?
Or should this be created at installation time of macports? Because like you said, that search yields a lot more than one result....
Cheers, A very happy Eloy