On Fri, 11 Oct 2002, Bjorn Wiren wrote:

> I still have no luck with my non-standard zlib path (see the thread
> "Compilation error from `urldata.h'").

I didn't realize you still had problems with this.

> #!/bin/sh
> CC=cc; export CC
> ./configure --prefix=/home/etxbwir/curl --with-ssl=/home/etxbwir/openssl
> --with-zlib=/home/etxbwir/xemacs/aux/zlib

Is that zlib path the prefix of that zlib installation? I mean, is appending
include and lib the correct thing to do to find the header and the lib?

That's what the configure script does to check.

> Again, if I explicitly define `HAVE_ZLIB_H' in `urldata.h' and set the zlib
> include and lib paths via CFLAGS and LDFLAGS it works.

Right, that's how it is supposed to work. Good that some things do as they're
meant at least! ;-)

> BTW, I had to add my non-standard path to openssl/lib too to "LDLIBS",
> don't remember doing that for 7.10.

The ssl check hasn't been modified since 7.10 so it should work quite the
same as before! ;-)

That check does about the same operation like the zlib one, it prepends the
given prefix to "lib" to check for the lib and "include/openssl" (*) to check
for the headers. How are the ssl headers/libs stored in your given ssl prefix
"/home/etxbwir/openssl" ?

Checking out your config.log and seeing how the failed checks look like might
give some clues.

(*) = it also appends just "include" to the given prefix in fact, as that was
      how to find SSLeay and early OpenSSL headers.

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf