On Fri, Jun 26, 2009 at 03:52:05PM +0100, Graham Keeling wrote:
> zlib, pcre, and pthreads all seem to build and install fine.
> The first problem with depkg-mingw64 is that openssl does not work. It
> complains about not being able to find zlib.h when trying to compile c_zlib.c.
>
> openssl-w64.patch seems to contain a lot of irrelevant lines. For example,
> it creates Configure.orig and sha512.c.orig from scratch, both of which are
> (I assume) not used in the build.
> I have been giving --with-zlib-include to the Configure script, and I have
> checked that I have a zlib.h in the right directory
> (depkgs-mingw-w64/include).
>
> I eventually realised that openssl.patch (rather than openssl-w64.patch)
> contains patches that add the --with-zlib-include functionality. So I thought
> that perhaps I needed to use both patch files. This is not the case, as some
> patches fail when I tried that.
> So I ended up combining various patches from each patch file to get openssl to
> build.
I still have this problem.
What options should I be giving to openssl's Configure?
I have been trying to use this:
./Configure --prefix=${DEPPKG_DIR} \
shared zlib-dynamic \
threads \
--with-zlib-include=${DEPPKG_DIR}/include \
mingw64 > make.log 2>&1
However, that is not going to work, because openssl-w64.patch does not
change Configure to understand --with-zlib-include=.
But Kern says that he used openssl-w64.patch.
Does this mean that everybody else has been using openssl without zlib?
For example...?
./Configure --prefix=${DEPPKG_DIR} \
shared \
threads \
mingw64 > make.log 2>&1
------------------------------------------------------------------------------
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
