Charles Wilson wrote:
> OTOH, I never have understood why tools insist on including such
things as
> "-lcygwin" or "-lc" on a linker command line.
There's a good reason for libtool to do so, but it escapes me at the
moment. Trust Me(tm).
Since gcc already includes libcygwin and libgcc and su
On Tue, Feb 01, 2005 at 11:02:18PM -0500, Igor Pechtchanski wrote:
>On Tue, 1 Feb 2005, Charles Wilson wrote:
>>Christopher Faylor wrote:
>>>OTOH, I never have understood why tools insist on including such things
>>>as "-lcygwin" or "-lc" on a linker command line.
>>
>>There's a good reason for lib
On Tue, 1 Feb 2005, Charles Wilson wrote:
> Christopher Faylor wrote:
>
> > OTOH, I never have understood why tools insist on including such things as
> > "-lcygwin" or "-lc" on a linker command line.
>
> There's a good reason for libtool to do so, but it escapes me at the moment.
> Trust Me(tm).
Christopher Faylor wrote:
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.
DING! We HAVE a winner!
The installed libtool has been configured -- by virtue of the fact that
I ran the build in a cygwin environment -
Dave Korn wrote:
-Original Message-
From: Vladius [mailto:[EMAIL PROTECTED]
I have found a solution to hack this issue.
1.Goto usr/autotool/devel/bin/
2.Open "libtool" file with a text editor(vim).
3.Search for "postdeps" initialisation. ("postdeps=" string)
4.Remove "-lcygwin"
Dave Korn wrote:
-Original Message-
From: Vladius [mailto:[EMAIL PROTECTED]
I have found a solution to hack this issue.
1.Goto usr/autotool/devel/bin/
2.Open "libtool" file with a text editor(vim).
3.Search for "postdeps" initialisation. ("postdeps=" string)
4.Remove "-lcygwin"
On Tue, Feb 01, 2005 at 06:15:50PM -, Dave Korn wrote:
>> -Original Message-
>> From: cygwin-owner On Behalf Of Christopher Faylor
>> Sent: 01 February 2005 17:27
>
>> Has it been established that the cygwin version of libtool is *supposed*
>> to handle mingw? I'd be rather surprised i
> -Original Message-
> From: cygwin-owner On Behalf Of Christopher Faylor
> Sent: 01 February 2005 17:27
> 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.
Nope, I just assumed that it could be made
> -Original Message-
> From: Vladius [mailto:[EMAIL PROTECTED]
> I have found a solution to hack this issue.
> 1.Goto usr/autotool/devel/bin/
> 2.Open "libtool" file with a text editor(vim).
> 3.Search for "postdeps" initialisation. ("postdeps=" string)
> 4.Remove "-lcygwin" initialis
On Tue, Feb 01, 2005 at 03:56:17PM -, 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 resu
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 libcommon.la
common.lo
Output:
rm -fr .libs/libcommon.a .libs/libcommon.la .libs/libcommon.lai
g++ -share
> -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.
>
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 libcommon.la
common.lo
Output:
rm -fr .libs/libcommon.a .libs/libcommon.la .libs/libcommon.lai
g++ -shared
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 libcommon.la common.lo
Output:
rm -fr .libs/libcommon.a .libs/libcommon.la .libs/libcommon.lai
g++ -shared -nostdlib /usr/
14 matches
Mail list logo
