Re: Bugs in sysroot patches resulting in $(local_include)/include always searched, ../-expansion broken

[Daniel Jacobowitz <drow@mvista.com>]

On Tue, Mar 04, 2003 at 04:19:11PM -0300, Alexandre Oliva wrote:
> On Feb 22, 2003, Daniel Jacobowitz <drow@mvista.com> wrote:
> 
> > The change was that when you run gcc
> > from outside the installation prefix, nothing inside the installation
> > prefix will be searched.
> 
> Not even the original (unrelocated) installation prefix?  This sounds
> wrong to me.  If I read you correctly, this means that the sys-root
> isn't searched during the GCC build process.  Is this the effect of
> your change?  If so, I don't agree it's the right thing to do.

In theory it could mean that, but there's something else involved that
we discussed: we only relocate the sysroot if (the sysroot was inside
the prefix and) the new directory would exist.  If you happen to have
something matching the sysroot location from inside the build tree,
then I assume it's deliberate.

This is pretty important.  Consider:

  /opt/manufacturer/bin/gcc
  /opt/manufacturer/target/usr/include/version2.h

  /opt/manufacturer-old/bin/gcc
  /opt/manufacturer-old/target/usr/include/version1.h

I believe that (even though both were configured for
/opt/manufacturer), the one in /opt/manufacturer-old should not search
there and autoconf checks for version2.h should fail.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer