From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27539 invoked by alias); 16 Dec 2002 14:34:28 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 27523 invoked from network); 16 Dec 2002 14:34:20 -0000 Received: from unknown (HELO mail.oarcorp.com) (216.107.91.226) by sources.redhat.com with SMTP; 16 Dec 2002 14:34:20 -0000 Received: (qmail 5943 invoked from network); 16 Dec 2002 14:34:19 -0000 Received: from unknown (HELO OARcorp.com) (136.205.65.100) by 0 with SMTP; 16 Dec 2002 14:34:19 -0000 Message-ID: <3DFDE46C.952C6222@OARcorp.com> Date: Mon, 16 Dec 2002 06:40:00 -0000 From: Joel Sherrill Organization: OAR Corporation X-Accept-Language: en MIME-Version: 1.0 To: Ben Elliston CC: gcc@gcc.gnu.org Subject: Re: problem running test_installed suite was Re: more on mips-elf test installed References: <3DF9EAFD.74E57893@OARcorp.com> <3DFA143D.C973B2A1@OARcorp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-12/txt/msg00879.txt.bz2 Ben Elliston wrote: > > >>>>> "Joel" == Joel Sherrill writes: > > Joel> Executing on host: gcc /usr/share/dejagnu/testglue.c -c -o > Joel> /usr3/ftp_archive/gnu/gcc/ss/b-3.2.1/r-arm-elf/testglue.o (timeout = > Joel> 300) > > Joel> Notice that testglue.c is being compiled by the NATIVE > Joel> compiler -- not the cross!!! What needs to be set to make > Joel> runtest use the correct compiler on testglue.c? > > What target_board have you told DejaGnu you're testing on? I have been trying two configurations with the same results: mips-elf with DejaGNU target board mips-sim arm-elf with DejaGNU target board arm-sim Both produce vey good test results when I test inside the tree but if I run the tests from somewhere else, testglue.c is always compiled with the native "gcc". The tests that do not link against testglue.c all appear to be passing. Inside the tree, I do this: make RUNTESTFLAGS="--target_board=${sim}" check check-gcc check-g++ Outside the tree, I do this: ${gccpath}/contrib/test_installed --srcdir=${gccpath} \ --with-gcc=${1}-gcc \ --without-g++ \ --without-g77 \ --with-target=${sim} where $1 is the gcc target which gets mapped to a simulator target a few lines above in the wrapper script I am using. My test_installed is modified to take the --with-target option so runtest ends up being invoked like this: runtest --tool gcc -v --target_board arm-sim I am sure it is a 1-liner somewhere. I think runtest or the gcc test suite scripts assume some variable besides GCC_UNDER_TEST is set to tell it about the compiler to test. I ran into this months ago and asked on the list with no fix. I would really like to nail this one shut. :) Thanks. > Ben -- Joel Sherrill, Ph.D. Director of Research & Development joel@OARcorp.com On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985