Use target_alias in validate_failures.py

Rainer Orth ro@CeBiTec.Uni-Bielefeld.DE
Mon Apr 16 10:32:00 GMT 2012


When I tried contrib/testsuite-management/validate_failures.py for the
first time this weekend, I ran into the following problem: while it
works fine for a i386-pc-solaris2.11 bootstrap, it fails instead for a
amd64-pc-solaris2.11 bootstrap:

      error: 11-gcc-64/build is not a valid GCC top level build directory.

The problem is that while the toplevel Makefile has

target=x86_64-pc-solaris2.11

the build was configured with --target=amd64-pc-solaris2.11 and the
target libraries live below the amd64-pc-solaris2.11, using the target
alias instead of the canonical target name.  Therefore the script thould
use

target_alias=amd64-pc-solaris2.11

to work in such a case.

The following patch does just that.

Ok for mainline?

Btw., it occured to me that it might be useful to add an option to
locate out-of-tree manifests.  I often have several source trees
(unmodified sources, ones with local patches) and would like to share
manifests between them.  While this can be achieved with symlinks, a
--manifest_dir or similar option might be an alternative.  Thoughts?

	Rainer


2012-04-15  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>

	* testsuite-management/validate_failures.py (GetBuildData): Use
	target_alias.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: validate_failures-target_alias.patch
Type: text/x-patch
Size: 1006 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20120416/a599b00b/attachment.bin>
-------------- next part --------------

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University


More information about the Gcc-patches mailing list