Problems creating "-mno-cygwin" DLLs with libtool.

Max Bowsher
Tue Feb 1 15:35:00 GMT 2005

Vladius wrote:
> I have problems compiling DLLs with -mno-cygwin flag, using libtool.
> Command is: libtool --mode=link --tag=CXX g++ -rpath
> /Projects/Tests/libtool -mno-cygwin -no-undefined -o 
> common.lo
> Output:
> rm -fr  .libs/libcommon.a .libs/ .libs/libcommon.lai
> g++ -shared -nostdlib /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/crtbegin.o
> .libs/common.o  -L/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3
> -L/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../.. -lstdc++ -lgcc -lcygwin
> -luser32 -lkernel32 -ladvapi32 -lshell32 -lgcc
> /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/crtend.o  -mno-cygwin -o
> .libs/cygcommon-0.dll -Wl,--image-base=0x10000000
> -Wl,--out-implib,.libs/libcommon.dll.a
> ar cru .libs/libcommon.a  common.o
> ranlib .libs/libcommon.a
> creating
> (cd .libs && rm -f && ln -s ../
>    As U can see... it automatically passes -lcygwin flag to the
> linker(g++). When cygcheck'ing resulting DLL it lists cygwin DLL as one
> of its dependencies.
> I heard somewhere that cygwin is requierd for DLL initialisation, is it
> true?
> The interesting thing is that linking against resulting DLL with
> so-called "-mno-cygwin -lcygwin" mix results in program startup
> failure(no errors, it just hangs).
>    Any ideas on how to create cygwin independent DLL with libtool?

But unless it *directly* relates to the special courtesy provision 
of -mno-cygwin, it's a matter independent of cygwin, and thus independent of 
this mailing list!

mingw-users might be a better forum.


Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list