Mail Archives: cygwin-apps/2001/02/05/17:29:58
"Dr. Volker Zell" wrote:
>
> In case anybody has build the following packages with libpng-1.0.8, I
> found that the new
> version breaks also the following executables (because of missing
> png_init_io entry point):
[embarrassingly long list of broken programs snipped]
>
> But recompilation fiexes everything.
^&@(!)#$&!@#%!@#$
All I can say is, XEmacs still worked. Compiled with the old lib, used
with the new lib. I guess XEmacs is not such a great test case, after
all.
!@#%*@(#)!~
I'm really, *really* sorry about this. Unfortunately, there's very little
I can do about it. I considered the following:
(1) beat the png-developers into submission so that they change the .def
file to match the (semi-random) export table result cygwin's gcc generated
for the unspecified exports back in 1.0.8-3. However, that won't match
the (semi-random) export table generated back in 1.0.8-3 by msvc for the
unspecified exports in the native build dll. I give you three guesses
which one they did match, have matched, and will match -- and the first
two guesses don't count. Nothing against png-develop, but msvc/native is
a much bigger market than cygwin.
(2) change the dll name, so that the old dll stays "cygpng2.dll" and the
new dll is "cygpng3.dll." Well, yeah --- possible --- but we just
finished a huge flamefest on the png list about dll naming synchonization
between msvc/native "libpngX.dll" and cygwin "cygpngX.dll". I really
don't want to upset the apple cart on that issue now.
(3) go home and hide. I gave this one serious consideration.
--Chuck
- Raw text -