Re: Fwd: Problem with bzip2

On Tue, 13 May 2008, Vasileios Anagnostopoulos wrote:

> The copy I checked out from CVS does not compile and unfortunately my laptop
> power supply has failed. In the event I replace it I will keep the thread
> informed about the progress. However some preliminary tests with version 1.2
> reveal that even if I remove the default install of bzip2 and compile the
> new version of bzip2 as a static library with mingw gcc-3.4.5-20060117-3
> bzip2 is not recognized. I believe this is fixed in the CVS. The bonus is
> that I have compiled libwmf and it is recognized properly. I also found out
> that the same procedure (static library from source) gives an undetectable
> zlib. When I fix my laptop I will tell you
> more.**<http://sourceforge.net/forum/forum.php?forum_id=815819>

I am afraid that I don't quite understand the meaning of what you say 
above.  Hopefully a replacement power supply will lead to 
clarification.

It seems that with MinGW, packages which are explicitly instrumented 
to be Windows DLLs cause more harm than good.  The bzip2 header causes 
more harm than good since its defaults are not correct for usage of 
the DLL library (defaults to symbol import rather than export).  A 
dependent package can not intelligently know if the library will be 
(is) static or DLL. Autoconf does not make any provision for including 
additional header files when testing for library symbols.

I am glad to hear that libwmf works for you.

Bob
======================================
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/