From: "Kurt D. Starsinic" <[EMAIL PROTECTED]>
Subject: Re: Portable linker flags
Date: Mon, 17 Apr 2000 16:04:45 -0400
Message-ID: <[EMAIL PROTECTED]>
kstar> On Mon, Apr 17, 2000 at 08:14:17PM +0200, Richard Levitte - VMS Whacker wrote:
kstar> > kstar> is sufficient. On another particular FreeBSD system with RSAREF,
`-lcrypto
kstar> > kstar> -lRSAglue -lrsaref' is required. What's the right way to figure out
the
kstar> > kstar> flags from an autoconf/metaconfig script?
kstar> >
kstar> > I think that if you do the latter you'll be fine in all cases, 'cause
kstar> > unless I'm misinformed, stuff from a library will only be used if
kstar> > there's an actual reference to them, otherwise they'll just be
kstar> > ignored.
kstar> >
kstar> > Of course, that means you might need to have dummies where libRSAglue.a
kstar> > and librsaref.a do not exist.
kstar>
kstar> That is, in fact, the case. What I'm trying to find out is if I
kstar> can probe libcrypto at configure time to find out if it needs the
kstar> additional libraries, so that I only include the -l options I need for
kstar> that platform.
I still think it's not needed, but look for a reference to the symbol
RSA_PKCS1_RSAref. At least, that's the only symbol I can think of
right now that makes a difference.
--
Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
Redakteur@Stacken \ SWEDEN \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
