GCC 4.0.1 testsuite uses installed g++ instead of newly bootstrapped g++

[Paul C. Leopardi]

Mike,
Thanks. Reply below.
Best regards, Paul Leopardi

On Thu, 28 Jul 2005 10:40 am, Mike Stump wrote:
> On Jul 27, 2005, at 5:21 PM, Paul C. Leopardi wrote:
> >> What sets the value of this variable?
>
> We will expect you to be able to find the code and read it.  The code
> you want to read is over in gcc/gcc/testsuite/lib/g++.exp, you should
> be able to tell us what sets it and when after you spend 10 seconds
> reading the code.

From what I see in that file, proc g++_init sets the compiler via 
GXX_UNDER_TEST, proc g++_target_compile uses GXX_UNDER_TEST to invoke the 
compiler, and proc g++_version can be used to print and therefore verify the 
compiler version.

> In addition to that code, check out *.exp, and ../.*/*.exp and then
> dejagnu/lib/*.exp and dejagnu/config/*.exp, after that, you'll be an
> expert.

OK. Looks like a long term project.

> Wild ass guess, did you type make -k check?

Yes. Is there something wrong with that?

In output of make -k check, I did notice that autogen is missing, causing an 
"Error 2", but the test carries on regardless. Is this OK?

make[1]: Entering directory `/home/leopardi/src/gcc/gcc-4.0.1-obj/fixincludes'
autogen 
-T ../../gcc-4.0.1/fixincludes/check.tpl ../../gcc-4.0.1/fixincludes/inclhack.def
make[1]: autogen: Command not found
make[1]: *** [check] Error 127
make[1]: Leaving directory `/home/leopardi/src/gcc/gcc-4.0.1-obj/fixincludes'
make: *** [check-fixincludes] Error 2
make[1]: Entering directory `/home/leopardi/src/gcc/gcc-4.0.1-obj/gcc'
Making a new config file...

SUSE packaged autogen for SUSE Linux 9.3, but not for my version, SUSE Linux 
9.2. Should I just stop now, install autogen and try again?
http://www.novell.com/products/linuxpackages/professional/autogen.html
http://rpm.pbone.net/index.php3/stat/4/idpl/1805805/com/autogen-5.6.5-3.i586.rpm.html

Also, gcc summary says:

		=== gcc Summary ===

# of expected passes		34550
# of unexpected successes	1
# of expected failures		105
# of untested testcases		28
# of unsupported tests		433
/home/leopardi/src/gcc/gcc-4.0.1-obj/gcc/xgcc  version 4.0.1

I guess that the last line of gcc summary is printed by proc 
default_gcc_version in gcc.exp.

The preamble to g++ testing says:

make[1]: [check-gcc] Error 1 (ignored)
(rootme=`${PWDCMD-pwd}`; export rootme; \
srcdir=`cd ../../gcc-4.0.1/gcc; ${PWDCMD-pwd}` ; export srcdir ; \
cd testsuite; \
EXPECT=expect ; export EXPECT ; \
if [ -f ${rootme}/../expect/expect ] ; then  \
   TCL_LIBRARY=`cd .. ; cd ../../gcc-4.0.1/gcc/../tcl/library ; 
${PWDCMD-pwd}` ; \
    export TCL_LIBRARY ; fi ; \
runtest --tool g++ )
Test Run By leopardi on Sat Jul 23 00:05:15 2005
Native configuration is x86_64-suse-linux-gnu

Is the command "runtest --tool g++" correct? I noticed that proc g++_init 
contains the code:
    if ![info exists GXX_UNDER_TEST] then {
	if [info exists TOOL_EXECUTABLE] {
	    set GXX_UNDER_TEST $TOOL_EXECUTABLE;
Does "runtest --tool g++" set TOOL_EXECUTABLE to "g++" ?

Finally, in the output of "make -k check", g++ summary says:

		=== g++ Summary ===

# of expected passes		9113
# of unexpected failures	2166
# of unexpected successes	16
# of expected failures		54
# of unresolved testcases	61
# of untested testcases		54
# of unsupported tests		90
/usr/bin/g++  version 3.3.4 (pre 3.3.5 20040809)

I guess that the last line of g++ summary is printed by proc g++_version in 
g++.exp. Does this imply that proc g++_init has set the compiler via 
GXX_UNDER_TEST to either "/usr/bin/g++" or more likely, "g++" ?