Re: Warning when compiling GNUstep

[Richard Frith-Macdonald]

On Monday, July 28, 2003, at 08:31 PM, Pete French wrote:

> > Also ... the bundle is typically not even loaded unless your
> > code tries to access an https URL, so even if the linking of
> > libraries into bundles is going wrong somehow, it seems unlikely
> > that anything to do with this bundle is causing errors in the gui.

Actually, I checked, and I think the bundle gets loaded if NSURL is
used at all ... so the gui could well be loading it.

> Linking these libraries is a bit odd on BSD - if you dont add the
> -lcrypto then it will still link using a different library which
> it gets from somewhere. But the errors are only produced when the 
> actual
> executable is generated. I had this with my own Objective C home grown
> foundation kit, and the fix was to add -lcrypto.

Can this be done for the bundle and left out of the link instruction for
code that merely uses the bundle?

We need to be able to detect this situation using autoconf, so we can
Looking at the configure.ac, it seems that -lcrypto is used if
CRYPTO_malloc is defined in it.  Perhaps we need to find another
function to look for to check for the presence of the library?