[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: another 1.5 release?
From: |
Ralf Wildenhues |
Subject: |
Re: another 1.5 release? |
Date: |
Wed, 2 Feb 2005 14:49:18 +0100 |
User-agent: |
Mutt/1.4.1i |
* Ralf Wildenhues wrote on Mon, Jan 31, 2005 at 08:16:57AM CET:
> * Daniel Reed wrote on Sat, Jan 29, 2005 at 07:31:41PM CET:
> > On 2005-01-28T22:03+0100, Ralf Wildenhues wrote:
> > ) This is a misunderstanding. Think libstdc++.la in a custom gcc
> > ) installation, say, in $HOME/local.
> > )
> > ) If your patch was applied, the following happens:
> > ) Libtool finds it in the search paths that are checked _before_
> > ) gcc -print-file-name
> > ) will even be tried for finding it.
> > )
> > ) For one of -m32/-m64, things will break.
> > )
> > ) I have such a setup at work, BTW.
> >
> > I am not convinced this isn't a broken setup, though.
>
> Yes, after retrying what I tried to do back then, I think you are right
> on this one.
Nope, not right. compiler_lib_search_path will contain both
directories:
compiler_lib_search_path="-L/tmp/gcc-test/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.0.0
-L/tmp/gcc-test/bin/../lib/gcc
-L/tmp/gcc-test/lib/gcc/x86_64-unknown-linux-gnu/4.0.0
-L/tmp/gcc-test/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.0.0/../../../../lib64
-L/tmp/gcc-test/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.0.0/../../..
-L/tmp/gcc-test/lib/gcc/x86_64-unknown-linux-gnu/4.0.0/../../../../lib64
-L/tmp/gcc-test/lib/gcc/x86_64-unknown-linux-gnu/4.0.0/../../.. -L/lib/../lib64
-L/usr/lib/../lib64"
You'd have too weed that out, else libtool won't work with this locally
installed compiler.
The user has not added any `-L' options in this case.
Regards,
Ralf
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: another 1.5 release?,
Ralf Wildenhues <=