On Thu, Jul 30, 2009 at 11:36:22PM +0200, Sven de Vries wrote: > Hi, > > > IIRC, new alpine needs openssl098 whereas OS X comes with openssl097. > > that's a bit surprising to me, since: > > *Alpine-2.0 has been out since around august 2008. and on the alpine > web-page, i can't find any reference to a more recent version.
openssl098 first landed in fink in June 2008 as version 0.9.8g, so openssl098 was clearly available for alpine developers to start using by their release months later. > *also, alpine-2.0-1 was building fine and running fine on my 10.5.7 MBP. > (and picking up the ssl-stuff from /System/Library/OpenSSL/) The switch to using fink's paths pointing to fink's openssl098 was done to resolve this bug: http://permalink.gmane.org/gmane.os.apple.fink.general/28869 The BIO_method_type symbol, used directly by alpine-2.00 sources, is not present in openssl097 (not in fink's package of it nor in the one that comes with OS X 10.4 or 10.5). Therefore I don't see any possible way for alpine to compile unless it links against an openssl that supplies the required symbol. Either your system openssl is more feature-ful than mine (possible) or while you think the paths were set a certain way, you weren't *actually* linking against apple's at all--one of the difficulties in getting flag orders correct is that one can get mixtures of linking the same lib and headers from multiple places. The solution that makes alpine usable for all our users it to cleanly use fink's openssl098. That makes a simple package with Depends that are sane and self-consistent. You are welcome to hack the package to build your own local copy with whatever options you prefer, using whatever less-than-current version of whatever libs at whatever paths you like--you seem to already know the .info file layout and settings in it that give the behavior you want. I think htodd's decision to have the package be tuned to be buildable (vs reproducibly not, for many users) is a wise choice, at minimal pain for end-users. I would also note that many other fink packages also use fink's openssl (and presumably all want their certs in the same fink place), so you annoyance at alpine in particular is mis-aimed...it's just the first place you have encountered a package that needs it (and a change that is easy for you to adjust to). dan -- Daniel Macks dma...@netspace.org http://www.netspace.org/~dmacks ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
