[Bug driver/35300] References to original ${prefix} paths in relocated toolchain and /lib and /usr/lib search paths appear in cross toolchain.

drow at false dot org gcc-bugzilla@gcc.gnu.org
Sat Feb 23 17:46:00 GMT 2008



------- Comment #10 from drow at gcc dot gnu dot org  2008-02-23 17:45 -------
Subject: Re:  References to original ${prefix} paths in
        relocated toolchain and /lib and /usr/lib search paths appear in
        cross toolchain.

On Sat, Feb 23, 2008 at 08:54:56AM -0000, kkylheku at gmail dot com wrote:
> What to do to close this bug? Someone should investigate the behavior of
> current gcc maybe. If you build a cross toolchain and relocate it, what is the
> output of -print-search-dirs? Are all the paths under the toolchain, or do some
> point back to the original build or install directory? Does a cross-compiling
> toolchain refer to build machine material in /usr/lib/gcc or /usr/libexec/gcc?

I understand that you have to work with 4.1, but the first step is
still to look at HEAD and see what other people have already fixed.
For instance:

  /* If not cross-compiling, search well-known system locations.  */
  if (*cross_compile == '0')
    {
#ifndef OS2
      add_prefix (&exec_prefixes, standard_exec_prefix_1, "BINUTILS",
                  PREFIX_PRIORITY_LAST, 2, 0);
      add_prefix (&exec_prefixes, standard_exec_prefix_2, "BINUTILS",
                  PREFIX_PRIORITY_LAST, 2, 0);
#endif
      add_prefix (&startfile_prefixes, standard_exec_prefix_2, "BINUTILS",
                  PREFIX_PRIORITY_LAST, 1, 0);
    }

So no, a cross toolchain will not refer to /usr.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35300



More information about the Gcc-bugs mailing list