It's almost bedtime here. I'll check this one out in the morning.
>I checked - stunnel.exe itself is built with -static-libgcc - if
>gcc1.dll is the problem, it must be causing issues with one of the
>dependencies.
This is almost certainly the case. Here's the list I posted earlier from
one of my systems:
Loading DLL 'libc066' --> D:\USR\LIB\LIBC066.DLL.
Loading DLL 'libcn0' --> D:\USR\LIB\LIBCN0.DLL.
All DLL's used by 'D:\USR\LIB\LIBCN0.DLL' could be loaded.
All DLL's used by 'D:\USR\LIB\LIBC066.DLL' could be loaded. Loading DLL
'libcx0' --> D:\USR\LIB\LIBCX0.DLL.
Loading DLL 'libcn0' --> D:\USR\LIB\LIBCN0.DLL.
Loading DLL 'gcc1' --> D:\USR\LIB\GCC1.DLL.
Loading DLL 'libcn0' --> D:\USR\LIB\LIBCN0.DLL.
All DLL's used by 'D:\USR\LIB\GCC1.DLL' could be loaded.
All DLL's used by 'D:\USR\LIB\LIBCX0.DLL' could be loaded.
Loading DLL 'pthr01' --> D:\USR\LIB\PTHR01.DLL.
Loading DLL 'libcn0' --> D:\USR\LIB\LIBCN0.DLL.
Loading DLL 'libcx0' --> D:\USR\LIB\LIBCX0.DLL.
Loading DLL 'gcc1' --> D:\USR\LIB\GCC1.DLL.
All DLL's used by 'D:\USR\LIB\PTHR01.DLL' could be loaded.
gcc1.dll is loaded by libcn0 and pthr01.
If I were a betting man, I'd bet Massimo did not realize he had two copies
of gcc1.dll installed. Based on his last message, It's likely he did not
understand what we were saying about the copy he had installed in
c:\util\lib. Maybe he does now.
While I used to build with -static-libgcc at one time, I've moved away
from this since any complex app is going to require a number of DLLs that
require gcc1.dll.
Back when gcc492.dll and friends contained the runtime code it made sense
to pull it into the executable. It saved shared memory. Now that
gcc1.dll exists and gcc492.dll and friends are only forwarders, there's
really no savings.
back to list