Graham Keeling wrote:
> On Fri, Jun 26, 2009 at 03:52:05PM +0100, Graham Keeling wrote:
>
>> 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).
>>
>
> For the record, I now know what my problem with openssl and zlib was.
>
> The build-depkgs-mingw-w64 script that was added to SVN recently does some
> additional things, including this:
>
> sed -i 's/CC=/CC=mingw32-gcc #/' crypto/comp/Makefile
> sed -i 's/AR=/AR=mingw32-ar r #/' crypto/comp/Makefile
> sed -i "s:^CFLAGS=:CFLAGS= -I${DEPPKG_DIR}/include:" crypto/comp/Makefile
> (the sed changes to the Makefile could be part of openssl-w64.patch)
>
In fact, this is a bit hard to patch non existing files.... Those files
and variables are generated by
the configure script, so they don't exist at the patch time.
So, to fix this, you need to patch the configure file, and bacula's
configure is enough for me :)
Feel free to report this bug to the openssl team (this is clearly a bug
in their configure file).
Bye
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
