I guess this is a bit late, but I think it worked and you can ignore these messages. See below for details.
> So, yeah, when I run the command as sudo, here's what I get: > > ranlib -sf /usr/local/lib/libfreeimage.a > ranlib: archive library: /usr/local/lib/libfreeimage.a will be fat > and ar(1) will not be able to operate on it > ranlib: for architecture: ppc file: /usr/local/lib/libfreeimage.a > (FreeImageC.o-ppc) has no symbols ..snip.. > ranlib: for architecture: i386 file: /usr/local/lib/libfreeimage.a > (pngvcrd.o-i386) has no symbols > ln -sf libfreeimage-3.9.3.dylib /usr/local/lib/libfreeimage.3.dylib The ranlib warnings are because ranlib/ar are going away... see 'man ranlib': "Libtool with -static is intended to replace ar(5) and ranlib." and "-f Warns when the output archive is universal and ar(1) will no longer be able to operate on it." The "has no symbols" errors might be due to that fact that some code is conditionally not compiled on os x... In fact, running libtool gets rid of the ar warnings, but the symbols are still missing. I get the same messages when I run ranlib/libtool on libfreeimage.a installed via macports in /opt/local/lib Brian _______________________________________________ Sdruby mailing list [email protected] http://lists.sdruby.com/mailman/listinfo/sdruby
