Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Thu, 18 Jul 2002 19:28:25 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Available for test: gcc-3.1.1-3, gcc2-2.95.3-9, gcc-mingw-3_1-20020516-2
Message-ID:	<20020718232825.GD15374@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<FAC87D7C874EAB46A847604DA4FD5A642076B9 AT crtsmail DOT corp DOT riotinto DOT org> <000201c22d97$438ed160$0200a8c0 AT lifelesswks>
Mime-Version:	1.0
In-Reply-To:	<000201c22d97$438ed160$0200a8c0@lifelesswks>
User-Agent:	Mutt/1.3.23.1i

On Wed, Jul 17, 2002 at 11:38:41PM +1000, Robert Collins wrote:
>
>
>> -----Original Message-----
>> From: cygwin-owner AT cygwin DOT com 
>> [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Billinghurst, 
>> David (CRTS)
>> Sent: Wednesday, 17 July 2002 11:26 PM
>> To: cygwin AT cygwin DOT com
>> Subject: RE: Available for test: gcc-3.1.1-3, gcc2-2.95.3-9, 
>> gcc-mingw-3_1-20020516-2
>> 
>> 
>> The latest g77 seems fine.  LAPACK testsuite results are similar
>> to 2.95 and my own builds of 3.[012].
>> 
>> There is a problem with:
>>  - /usr/lib/libstdc++.la
>>  - /usr/lib/libsupc++.la
>>  - /usr/lib/libgcj.la
>> The paths that are hardcoded into the dependency_libs line
>> don't exist on my machine, so attempts to use c++ with libtool
>> fail.  (Just deleting the *.la files seems to solve the problem,
>> but I expect there are more subtle fixes.)  Once the libtool 
>> problem was overcome I could build ImageMagick including the 
>> c++ libraries.
>
>Hmm, I smell a libtool problem in the generation of the .la files.
>
>Sigh, I'll add this to my list of libtool bugs to review.

I know zero about libtool, but libtool is obviously taking my local
configury (below) and placing it into libstdc++\.la.  I don't know if
that is right or wrong but it seems strange -- especially when the tools
are cross-compiled.

I'm going to remove all of the .la files from the release for now.
I could rectify the dependency_libs but looking at what it is including,
even with the paths fixes, I don't think it really is very useful.

cgf

dependency_libs=' -L/cygwin/lib/gcc-lib/i686-pc-cygwin/3.1.1 -L/cygwin/lib/gcc-lib/i686-pc-cygwin/3.1.1/../../../../i686-pc-cygwin/lib -L/netrel/native/gcc3/i686-pc-cygwin/libstdc++-v3/src -L/netrel/native/gcc3/i686-pc-cygwin/libstdc++-v3/src/.libs -L/netrel/native/gcc3/gcc -L/cygwin/i686-pc-cygwin/bin -L/cygwin/i686-pc-cygwin/lib -lgcc -lcygwin -luser32 -lkernel32 -ladvapi32 -lshell32 -lgcc -lgcc -lcygwin -luser32 -lkernel32 -ladvapi32 -lshell32 -lgcc -lgcc -lcygwin -luser32 -lkernel32 -ladvapi32 -lshell32 -lgcc -lgcc -lcygwin -luser32 -lkernel32 -ladvapi32 -lshell32 -lgcc -lgcc -lcygwin -luser32 -lkernel32 -ladvapi32 -lshell32 -lgcc /cygwin/lib/gcc-lib/i686-pc-cygwin/3.1.1/libstdc++.la -lgcc -lcygwin -luser32 -lkernel32 -ladvapi32 -lshell32 -lgcc -lgcc -lcygwin -luser32 -lkernel32 -ladvapi32 -lshell32 -lgcc -lgcc -lcygwin -luser32 -lkernel32 -ladvapi32 -lshell32 -lgcc'

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -