This is the mail archive of the
mailing list for the GCC project.
Re: FW: I hate to ask this question (.la files and depends)
- From: Phil Edwards <phil at jaj dot com>
- To: "James A. Cleland" <jcleland at jamescleland dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 1 Mar 2002 02:02:32 -0500
- Subject: Re: FW: I hate to ask this question (.la files and depends)
- References: <NEBBJFOJGLJIOCPHIHEDIEMMCJAA.email@example.com>
On Wed, Feb 27, 2002 at 03:17:45PM -0500, James A. Cleland wrote:
> I have read there are some paths from the build tree, etc that get added to
> .la files unnecessarily when building gcc. I have also heard this is a
> libtool 'side-effect'. I would never have noticed unless I started to see
> libtool-created links that contained HUNDREDS of references to gcc_s, gcc,
> c, and m, among other things.
> Here's what my /usr/lib/libstdc++.la depend line looks like:
Yep, libstdc++ is one of the most visible cases of this problem. The thing
is, we have to tell libtool which directories to search, and there's no way
for it to know which directories are "transient" and shouldn't be remembered.
It's a well-known problem and people would love for it to be solved.
(Got any spare time?)
> What files should I be correcting (if any) besides
The .la files are the only place where these paths are recorded.
> 2.) I also see this alot:
> libtool: link: warning:
> `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.0.3/../../../libstdc++.la' seems to be
> What does this mean?
I have no idea. I don't think I've ever seen that before.
There is a separate mailing list for libtool, linked from its homepage,
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams