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

Christopher Faylor
Tue Feb 1 17:26:00 GMT 2005

On Tue, Feb 01, 2005 at 03:56:17PM -0000, Dave Korn wrote:
>> -----Original Message-----
>> From: cygwin-owner On Behalf Of Max Bowsher
>> Sent: 01 February 2005 15:35
>> Vladius wrote:
>> >    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?
>  I dunno, but I see lotsa references to something called
>'_cygwin_noncygwin_dll_entry@12' which sounds fairly suggestive.... then again,
>you can't always tell what a subroutine does from the name.
>> > 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?
>> Perhaps.
>> 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!
>  If the cygwin port of libtool passes two conflicting flags (-mno-cygwin and
>-lcygwin) to the underlying compiler, then it's a cygwin problem, surely?

Has it been established that the cygwin version of libtool is *supposed*
to handle mingw?  I'd be rather surprised if that was a goal.

OTOH, I never have understood why tools insist on including such things as
"-lcygwin" or "-lc" on a linker command line.


Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list