----- Original Message ----- From: <[EMAIL PROTECTED]>
.
.
How do I tell ./config where zlib.h is located ?
With Configure you may add something like:
 --with-zlib-lib=/path
 --with-zlib-include=/path

I find that when I run ./config.... the operating system "i686-whatever-mingw" is detected. And that seems to work quite well in general.

If I run /Configure.... I usually get a message requesting that I specify the OS/compiler. I'm also given a list of options, but I don't see "i686-whatever-mingw" mentioned anywhere in that list. Consequently I've been avoiding ./Configure.... , preferring instead to run ./config.....

Is there anything to be gained by running Configure instead of config ?

I tried:
./config no-shared zlib --with-zlib-include=/usr/local/include --with-zlib-lib=/usr/local/lib --prefix/usr/local/depot/static

I also tried:
./config no-shared zlib --with-zlib-include=/c/_32/msys//local/include --with-zlib-lib=/c/_32/msys/local/lib --prefix/usr/local/depot/static

zlib.h is in C:/_32/msys/local/include (and the msys shell regards that location as /usr/local/include) so either incantation should work. However, I always end up with the error "zlib.h: No such file or directory" - followed by a number of syntax errors arising from the inability to find zlib.h.

When I look at the actual gcc command that is being run I don't see an -I switch that includes the relevant location for zlib.h so I guess it's no surprise that zlib.h can't be found.

I've also tried "CPPFLAGS=-I/usr/local/include" - which usually works for me (wrt other libraries), but no joy in this instance.

I suspect that if I were to place zlib.h in my MinGW/include folder and libz.a in MinGW/lib folder, then it would work. But I would prefer (if possible) to be able to build without doing that.

Cheers,
Rob
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to