This is the mail archive of the
binutils@sourceware.cygnus.com
mailing list for the binutils project.
Re: http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html
- To: Alexandre Oliva <aoliva at cygnus dot com>
- Subject: Re: http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html
- From: "H . J . Lu" <hjl at valinux dot com>
- Date: Sun, 21 May 2000 16:50:55 -0700
- Cc: Mark Mitchell <mark at codesourcery dot com>, gcc-patches at gcc dot gnu dot org,binutils at sourceware dot cygnus dot com
- References: <20000520093135A.mitchell@codesourcery.com> <orhfbt9nwh.fsf@tamanduatei.dcc.unicamp.br> <20000520095133R.mitchell@codesourcery.com> <20000520220957.A25977@valinux.com> <orbt1z5v17.fsf@tamanduatei.dcc.unicamp.br>
On Sun, May 21, 2000 at 08:43:32PM -0300, Alexandre Oliva wrote:
> On May 21, 2000, "H . J . Lu" <hjl@valinux.com> wrote:
>
> > Ok, here is the patch. I also swapped the order of -B./ | -B$$r/gcc
> > and -B$(build_tooldir)/bin/ since the last one will be used and we want
> > to use the one in gcc.
>
> AFAIK, multiple -B flags accumulate, and they're searched
> left-to-right. Therefore, the change is actually arranging for
> installed binaries to be preferred over non-installed ones, which is
> obviously wrong. BTW, wouldn't it cause the installed `cpp' driver to
> be found when what we want is the actual preprocessor, in the gcc
> build directory?
I have verified that the last valid -B will be used, at least it
is the case for gcc 2.95 and ia64 gcc. I don't think it is changed
in gcc 3.0.
You can put some dummy "as" in some directories. Those dummy "as"
just echo something you can tell them apart. Then use -B to see
which one is called.
H.J.