Re: Possible issue with static win32 gsasl

[Lothar May]

Simon,

2010/10/5 Simon Josefsson <address@hidden>:
> Lothar May <address@hidden> writes:
>
>> Using static linking of gsasl (removing the other files from the lib
>> directory) I get errors:
>>
>> -- cut here --
>> C:\Projects\pokerth_mingw64\gsasl\examples>gcc -I..\include -L..\lib 
>> client.c -l
>> gsasl -o client
>> c:/projects/pokerth_mingw64/mingw/bin/../lib/gcc/x86_64-w64-mingw32/4.5.1/../../
>> ../../x86_64-w64-mingw32/bin/ld.exe: Dwarf Error: Offset (7872) greater than 
>> or
>> equal to .debug_abbrev size (601).
>> ..\lib/libgsasl.a(vasnprintf.o):vasnprintf.c:(.text+0x96): undefined 
>> reference t
>> o `___chkstk'
>> collect2: ld returned 1 exit status
>> -- cut here --
>
> I wonder if static linking can work at all under Windows when you are
> mixing compilers?  I was using MinGW-w64 based on GCC 4.5.1 to build the
> x86 binaries, but it is not certain that it is completely compatible
> with TDM-GCC.  The 'chkstk' stuff is not something from gsasl or gnulib,
> and looks likes some compiler internal stuff.  Hm.   Indeed, searching
> for 'chkstk' and MinGW suggests this is a common problem.  I didn't see
> any obvious solution though.
>

It seems that both the gsasl x64 static lib as well as the dll contain
debug information. Is this intended? After running strip.exe on it,
libgsasl-7.dll has only around 100kB, and still seems to work. Maybe
the link problem is related to debug information (the DWARF error
suggests it). However, running strip.exe on a static lib does not seem
to work.

Regards,
Lothar