OK, I'm ready to look at what remains of this ticket. I've got a question:
[levitte - Fri Dec 13 16:19:05 2002]:
> > * When linking the libraries, make sure that libssl finds libcrypto
> > and that they both find all their external dependencies at run time.
> > This is accomplished by the -R, -rpath or --rpath flags which behave
> > just like the -L flag. It is not necessary when all libraries can be
> > found using the default paths. To recap: giving --prefix to config
> > should automatically add -R${prefix}/lib and giving -L... to config
> > should automatically generate the same -R...
> > (Which flag to use depends on which compiler one is using.)
Isn't there a case when the -L and the -R arguments have different arguments?
For example, the openssl program is linked against libssl and libcrypto in the parent
directory, so the linking command includes -L.. . However, the -R switch would
indicate where the libraries are found by default, so adding such a switch should look
like this, roughly: -R${prefix}/lib, even when we have a -L.. . Right?
--
Richard Levitte
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
