This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug testsuite/38820] During "make -i check" we set GCC_EXEC_PREFIX="/usr/local/lib/gcc/"
- From: "rob1weld at aol dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 27 Jan 2009 15:38:35 -0000
- Subject: [Bug testsuite/38820] During "make -i check" we set GCC_EXEC_PREFIX="/usr/local/lib/gcc/"
- References: <bug-38820-13830@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from rob1weld at aol dot com 2009-01-27 15:38 -------
(In reply to comment #2)
> It's not a bug that GCC EXEC_PREFIX is defined when the testsuite is run, as
> explained in these patches:
>
> http://gcc.gnu.org/ml/gcc-patches/2006-10/msg00708.html
> http://gcc.gnu.org/ml/gcc-patches/2006-12/msg01493.html
>
> When testing in the build tree the compiler is invoked with -B, which takes
> precendence over GCC_EXEC_PREFIX. That allows getting start files from
> GCC_EXEC_PREFIX while the GCC support itself comes from the build tree. It
> doesn't matter if $GCC_EXEC_PREFIX contains an old installation.
>
OK for "RESOLVED INVALID" but I do not see that it was tested cross-target.
One example is host i386-unknown-linux-gnu target x86_64-unknown-linux-gnu
in the case where you want to upgrade from 32 bit based Operating System
to a 64 bit based system.
Another untested situations is where host and target are i386-unknown-linux-gnu
but the build is configured using "--with-tune=k8 --with-cpu=k8
--with-arch=k8".
Yet another is where you want to change your start files over from elf to
dwarf.
etc ...
I will test some of those sometime this year and re-open this if needed.
Thanks,
Rob
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38820