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
Message-ID: <402492EB.4040601@cwilson.fastmail.fm>
Date: Sat, 07 Feb 2004 02:25:31 -0500
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030630
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: gcc packaging bug [Was: Re: libtool linking problem]
References: <loom DOT 20040207T011935-144 AT post DOT gmane DOT org> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040206193742 DOT 038ef040 AT 127 DOT 0 DOT 0 DOT 1>
In-Reply-To: <6.0.1.1.0.20040206193742.038ef040@127.0.0.1>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Larry Hall wrote:

>>libtool: link: cannot find the library `/GCC/gcc-3.3.1-3/.inst/package-
>>gcc/usr/lib/./libstdc++.la'
>>

> It's hard to work with partial problem reports.
> 
> My WAG is that you didn't install the gcc-g++ package.  If that's true, do
> so.  If it's not, do a 'cygcheck -c gcc-g++'.  If the "Status" isn't
> "OK", reinstall the gcc-g++ package.  If it is "OK" already, I don't 
> know what to think beyond pointing you at the link above and suggesting
> you follow the procedures it outlines.

Nope, not really.  The *real* problem is that /usr/lib/libstdc++.la 
specifies the wrong dependency_libs and libdir.  Old libtools (such as 
the one still used by gcc & binutils) didn't handle DESTDIR-based 
installs very well, so you have to munge the .la files by hand (or by 
script; whatever).

Newer libtools, (1.5 and later) DO handle DESTDIR correctly, and it is 
hoped that the current effort that the gcc folks are doing to update the 
gcc tree to use the latest autotools will eventually mean that this 
problem will go away.

For now:

  short term: end-users can hand-edit the .la files (change the 
dependency_libs and libdir to the obvious thing)

  medium term: GCC maintainer add logic to his packaging script to "do 
the right thing" to the installed .la files

  long term: wait for the gcc developers to finish updating their tree 
to use modern autotools.

--
Chuck


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/