Most of my systems do not have pkgconfig. The variable passed to cURL was LDFLAGS=-L<lib>, where lib is OpenSSL platform specific, e.g. -L<prefixdir>/lib64 for Linux. With older openssl versions, cURL was happy with the openssl prefixdir, and assumed that the headers were in <opensslprefixdir>/include and libraries in <opensslprefixdir>/lib.
I've tried with PKG_CONFIG_PATH before, but that did not work if nog pkgconfig is on a system. Thanks, Kees > -----Original Message----- > From: Andy Polyakov via RT [mailto:[email protected]] > Sent: Friday, 16 July, 2010 10:32 > To: Kees Dekker > Cc: [email protected] > Subject: Re: [openssl.org #2307] building cURL with OpenSSL 1.0.0a on > 64-bit Unix flavors is almost impossible > > > cURL uses --prefix to find the include files as well and assumes that > > the libraries are in <prefixdir>/lib. Till now, cURL has a > > possibility to say where the library reside (with LDFLAGS environment > > variable). The problem is (but I'm not 100% sure) that the pkgconfig > > dir is also not in a fixed place. If the pkgconfig dir is always > > under <prefixdir>/lib (I don't know whether this is possible), some > > problems may be solved. You may like to check some more details of > > the problem at: > > > https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3029420&gr > oup_id=976 > > The information on the URL in question incomplete in a sense that there > is suggestion to "pass on environment variable" and that "it helped", > but no specifics, which is frustrating. For reference, I attempted to > build curl-7.21.0 on Linux with PKG_CONFIG_PATH pointing to "multilib" > directory and it worked all the way, without need to fiddle with > LDFLAGS. > > Either way, as already mentioned I recognize the problem and suggested > solution is http://cvs.openssl.org/chngview?cn=19772. A. > ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
