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: "H . J . Lu" <hjl at valinux dot com>
- Subject: Re: http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html
- From: Alexandre Oliva <aoliva at cygnus dot com>
- Date: 21 May 2000 20:43:32 -0300
- Cc: Mark Mitchell <mark at codesourcery dot com>, gcc-patches at gcc dot gnu dot org, binutils at sourceware dot cygnus dot com
- Organization: Cygnus Solutions, a Red Hat Company
- References: <20000520093135A.mitchell@codesourcery.com><orhfbt9nwh.fsf@tamanduatei.dcc.unicamp.br><20000520095133R.mitchell@codesourcery.com><20000520220957.A25977@valinux.com>
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?
> For ia64, binutils changed a few times. If we have -B./
> -B$(build_tooldir)/bin/ and -B$$r/gcc -B$(build_tooldir)/bin/, the
> old one in $(build_tooldir)/bin/ will be used. As the result, we get
> some strange errors.
This is really strange. There must be something wrong with -B
handling, then.
--
Alexandre Oliva Enjoy Guaranį, see http://www.ic.unicamp.br/~oliva/
Cygnus Solutions, a Red Hat company aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org} Write to mailing lists, not to me