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: Markus Weissmann <email@hidden>
- Date: Thu, 21 Jul 2005 23:05:25 +0200
Hi,
I already fixed this problem for DarwinPorts [1]; you may find the
Portfile and the
patches here [2].
cheers,
-Markus
[1] http://darwinports.opendarwin.org/
[2] http://darwinports.opendarwin.org/darwinports/dports/devel/openssl/
On 19.07.2005, at 22:18, OpenMacNews wrote:
hi all,
fwiw, i'm closer, but not 'there' yet ...
cref: <http://marc.theaimsgroup.com/?l=openssl-
dev&m=112180411301985&w=2>
> They screwed this up, go back and slap them.
I'd rather slap Apple for having an ancient, weird binary format and
toolchain that makes them so hard to support.
> Looks like a case of progressive dementia.
Its no wonder MacOSX specific brokenness creeps into OpenSource
projects where the primary development is on non-MacOSX platforms.
[]
seems there's a 'relevant (?) history' w.r.t OpenSSL "vs" Apple
here ...
from openssl-0.9.8-src/PROBLEMS:
" ...
* System libcrypto.dylib and libssl.dylib are used by system ld on
MacOS X.
NOTE: The problem described here only applies when OpenSSL isn't
built
with shared library support (i.e. without the "shared"
configuration
option). If you build with shared library support, you will
have no
problems as long as you set up DYLD_LIBRARY_PATH properly at all
times.
This is really a misfeature in ld, which seems to look for .dylib
libraries
along the whole library path before it bothers looking for .a
libraries. This
means that -L switches won't matter unless OpenSSL is built with
shared
library support.
The workaround may be to change the following lines in apps/
Makefile and
test/Makefile:
LIBCRYPTO=-L.. -lcrypto
LIBSSL=-L.. -lssl
to:
LIBCRYPTO=../libcrypto.a
LIBSSL=../libssl.a
It's possible that something similar is needed for shared library
support
as well. That hasn't been well tested yet.
Another solution that many seem to recommend is to move the libraries
/usr/lib/libcrypto.0.9.dylib, /usr/lib/libssl.0.9.dylib to a different
directory, build and install OpenSSL and anything that depends on your
build, then move libcrypto.0.9.dylib and libssl.0.9.dylib back to
their
original places. Note that the version numbers on those two libraries
may differ on your machine.
As long as Apple doesn't fix the problem with ld, this problem
building
OpenSSL will remain as is.
..."
<grumble> i agree. a major PITA! </grumble>
richard
_______________________________________________
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
---
Markus W. Weissmann
http://www.mweissmann.de/
http://www.opendarwin.org/~mww/
_______________________________________________
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