Re: any insights? upgrade from OpenSSL v0.9.7 --> 0.9.8 changes linking behavior on OSX
Re: any insights? upgrade from OpenSSL v0.9.7 --> 0.9.8 changes linking behavior on OSX
- Subject: Re: any insights? upgrade from OpenSSL v0.9.7 --> 0.9.8 changes linking behavior on OSX
- From: Andrew Gallatin <email@hidden>
- Date: Tue, 19 Jul 2005 11:02:53 -0400 (EDT)
OpenMacNews writes:
>
> i'll try _another_ clean rebuild ... tho, several to date have resulted in the
> same problem ...
So why would you expect another one to help? ;)
> > I bet the install names are wrong
>
> suggestions as to what/where in the openssl source to check for any
> mis-assignments of the install names? i thought -- perhaps naiively -- that
> libtool takes care of these ....
If openssl is GNU configure based, try explicitly specifying
--prefix=/usr/local to configure.
My understanding of what's happening is that MacOSX libs embed the
path to their installation location inside themselves. Then when
something links against it, it uses this embedded path to later find
the library when its run. This works sort of like
"-Wl,-rpath=/some/path" does on ELF toolchains, but its pretty
weird to people used to the ELF toolchains on linux/solaris/*BSD.
Your problem seems to be that the openssl installation must not be
setting this path, or is only setting it to libname, rather than
$prefix/lib/libname. I beleive the argument to gcc which sets this is
--install_name. I'm not sure what libtool calls it.
As a workaround, you could try setting DYLD_LIBRARY_PATH to
/usr/local/lib.
Drew
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden