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

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

[Paul C. Leopardi]

Hi all,
I have recently downloaded, configured, bootstrapped and tested gcc 4.0.1 and 
found the same problem that I reported for gcc 3.4.0 as PR/15356.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15356
See also the threads "gcc testsuite apparently can't find g++" 
http://gcc.gnu.org/ml/gcc-help/2004-05/msg00050.html
and "gcc 3.4.0 testsuite gives over 5000 g++ errors"
http://gcc.gnu.org/ml/gcc-help/2004-05/msg00034.html
At that time, as now, the g++ tests invoked via "make -k check" used my 
previously installed g++ rather than the newly bootstrapped g++.
PR/15356 was resolved as WORKSFORME, so I am reluctant to file another bug 
report.

I have checked and re-checked my configuration and the configuration seems OK, 
but the error condition persists.

I have reported this to the suse-amd64 mailing list, thinking that the problem 
may be specific to that architecture.
http://lists.suse.com/archive/suse-amd64/2005-Jul/0156.html
http://lists.suse.com/archive/suse-amd64/2005-Jul/0171.html

How do I make the tests find the bootstrapped g++? Shouldn't the test just do 
this automatically? How is the test supposed to find find the bootstrapped 
g++? Is it done via an environment variable? Which environment variable? What 
sets the value of this variable? Is it a script or a program?

What have I configured wrong, if anything? If this really is a bug, then why 
does the test work for Andreas Jaeger and not for me?
http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00112.html

Should I file another bug report and hope that I don't kust get WORKSFORME?
Best regards

Excerpt from my test summary: 
 
                === 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) 

Excerpt from "ps f" while g++ test is running:
...
CXX="g++"; 
...

Excerpt from output of 'make check-c++ RUNTESTFLAGS="-v -v"
...
compiler is /home/leopardi/src/gcc/gcc-4.0.1-obj/gcc/xgcc
...
doing compile
Invoking the compiler as 
g++ /home/leopardi/src/gcc/gcc-4.0.1/gcc/testsuite/g++.dg/bprob/g++-bprob-1.C  
...

 

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

[Paul C. Leopardi]

Hi all,
I did not receive a reply to my earlier message. Have I posted it to the wrong 
list? If so, what is the right list for this message?
Thanks

On Sat, 23 Jul 2005 07:23 pm, Paul C. Leopardi wrote:
> How do I make the tests find the bootstrapped g++? Shouldn't the test just
> do this automatically? How is the test supposed to find find the
> bootstrapped g++? Is it done via an environment variable? Which environment
> variable? What sets the value of this variable? Is it a script or a
> program?
>
> What have I configured wrong, if anything? If this really is a bug, then
> why does the test work for Andreas Jaeger and not for me?
> http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00112.html
>
> Should I file another bug report and hope that I don't kust get WORKSFORME?
> Best regards

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

[Ian Lance Taylor]

"Paul C. Leopardi" <leopardi@bigpond.net.au> writes:

> Hi all,
> I did not receive a reply to my earlier message. Have I posted it to the wrong 
> list? If so, what is the right list for this message?
> Thanks
> 
> On Sat, 23 Jul 2005 07:23 pm, Paul C. Leopardi wrote:
> > How do I make the tests find the bootstrapped g++? Shouldn't the test just
> > do this automatically? How is the test supposed to find find the
> > bootstrapped g++? Is it done via an environment variable? Which environment
> > variable? What sets the value of this variable? Is it a script or a
> > program?
> >
> > What have I configured wrong, if anything? If this really is a bug, then
> > why does the test work for Andreas Jaeger and not for me?
> > http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00112.html
> >
> > Should I file another bug report and hope that I don't kust get WORKSFORME?
> > Best regards

This is probably the right list.  It's just that nobody happened to
reply.  gcc is a volunteer effort, particularly when it comes to
answering questions on the mailing lists.

In this case, it's hard to write a useful reply since you didn't
provide any informative details.  It is true that running the
testsuite will normally use a newly built compiler, without requiring
it to be installed.  However, you didn't provide critical information
like precisely what you did, precisely what happened, what you
expected to happen instead, what version of the compiler you were
building, and what host you were running on.  So it's hard to know
what to say.

Or, in other words, WORKSFORME.

Ian

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

[Mike Stump]

On Jul 27, 2005, at 5:21 PM, Paul C. Leopardi wrote:
>> How do I make the tests find the bootstrapped g++?

You don't it already does.

>> Shouldn't the test just do this automatically?

Yes.

>> How is the test supposed to find find the bootstrapped g++?

Carefully, see the source code.

>> Is it done via an environment variable?

Sorta but not really.

>> Which environment variable?

GXX_UNDER_TEST is an example of one of the variables that plays into  
this, it happens to be an environment variable.

>> 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.

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.

>> Is it a script or a program?

Yes, more a script.

>> What have I configured wrong, if anything?

Don't know.

>> If this really is a bug, then why does the test work for Andreas  
>> Jaeger and not for me?

Don't know.

>> http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00112.html
>>
>> Should I file another bug report and hope that I don't kust get  
>> WORKSFORME?

No.


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

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

[Paul C. Leopardi]

Hi Lance,
Thanks for your prompt reply. Point by point, below.
Best regards, Paul Leopardi
On Thu, 28 Jul 2005 10:26 am, Ian Lance Taylor wrote:
> "Paul C. Leopardi" <leopardi@bigpond.net.au> writes:
> > Hi all,
> > I did not receive a reply to my earlier message. Have I posted it to the
> > wrong list? If so, what is the right list for this message?
> > Thanks
> >
> > On Sat, 23 Jul 2005 07:23 pm, Paul C. Leopardi wrote:
> > > How do I make the tests find the bootstrapped g++? Shouldn't the test
> > > just do this automatically? How is the test supposed to find find the
> > > bootstrapped g++? Is it done via an environment variable? Which
> > > environment variable? What sets the value of this variable? Is it a
> > > script or a program?
> > >
> > > What have I configured wrong, if anything? If this really is a bug,
> > > then why does the test work for Andreas Jaeger and not for me?
> > > http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00112.html
> > >
> > > Should I file another bug report and hope that I don't kust get
> > > WORKSFORME? Best regards
>
> This is probably the right list.  It's just that nobody happened to
> reply.  gcc is a volunteer effort, particularly when it comes to
> answering questions on the mailing lists.

OK. I understand this. I also know that getting my problem resolved is going 
to be a cooperative effort, probably involving hours and hours of work on my 
part. I have already spent many hours on this, having bootstrapped and tested 
g++ 3.4 and 4.0.1 numerous times. It's just that I don't know enough about 
how the test code is supposed to work to be able to resolve a problem when I 
see it. In paricular, I have not seen a detailed example of the c++ test 
working, and so cannot compare with my own case.

> In this case, it's hard to write a useful reply since you didn't
> provide any informative details.  

I gave links to threads on this and other mailing lists, and referenced bug 
15356. I also gave excerpts of test output. Other than that, I did not want 
to bombard the list with megabytes of "-v -v" test output which may not be 
needed. Rather I wanted to wait for guidance on what details to provide.

> It is true that running the 
> testsuite will normally use a newly built compiler, without requiring
> it to be installed.  However, you didn't provide critical information
> like precisely what you did, 

I said (via the URL links) that I bootstrapped gcc 4.0.1 on SUSE Linux 9.2 
AMD64, and tested gcc and g++, and that gcc worked and g++ did not work.

Contents of http://lists.suse.com/archive/suse-amd64/2005-Jul/0156.html

From: "Paul C. Leopardi" <leopardi@bigpond.net.au>
Date: Thu, 21 Jul 2005 11:49:54 +1000
Message-Id: <200507211149.55554.leopardi@bigpond.net.au>
Subject: [suse-amd64] Configuring gcc 4.0.1


 Hi all, 
 I'm using SUSE 9.2 AMD64, and have downloaded the latest gcc and am about to 
 bootstrap. Is there anyone who can help me with configuration, bootstrap, 
 test and install? I've run into problems with the testsuite and I don't know 
 whether I have done something wrong or am seeing a bug. I also don't know if 
 what I see is specific to SUSE AMD64, or specific to the current state of my 
 PC. 
 
First question: Is there anything wrong with the parameters I am giving to 
 configure? (see below) 
 Best regards 
 
My current gcc: 
 
leopardi@linfinit:~/src/gcc/gcc-4.0.1-obj> gcc -v 
 Reading specs from /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.4/specs 
 Configured with: ../configure --enable-threads=posix --prefix=/usr 
 --with-local-prefix=/usr/local --infodir=/usr/share/info 
 --mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java,ada 
 --disable-checking --libdir=/usr/lib64 --enable-libgcj 
 --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib64 
 --with-system-zlib --enable-shared --enable-__cxa_atexit x86_64-suse-linux 
 Thread model: posix 
 gcc version 3.3.4 (pre 3.3.5 20040809) 
 
I've run configure in the directory ~/src/gcc/gcc-4.0.1-obj as 
 
leopardi@linfinit:~/src/gcc/gcc-4.0.1-obj> ../gcc-4.0.1/configure 
 --prefix=/usr/local/gcc/gcc-4.0.1 --enable-threads=posix --disable-libgcj 
 --with-system-zlib --enable-shared --enable-__cxa_atexit 
 --enable-languages=c,c++ x86_64-suse-linux 
 
This looks like it worked, but gave the warning: 
 
configure: warning: x86_64-suse-linux: invalid host type 
----
Contents of http://lists.suse.com/archive/suse-amd64/2005-Jul/0171.html
 
From: "Paul C. Leopardi" <leopardi@bigpond.net.au>
Date: Sat, 23 Jul 2005 00:59:47 +1000
Message-Id: <200507230059.47813.leopardi@bigpond.net.au>
Subject: [suse-amd64] Testing gcc 4.0.1


 Hi all, 
 This is a follow-up to "Configuring gcc 4.0.1". 
 
I made sure that I no longer had CXX defined in my .bashrc, and then started 
 from scratch: 
 Created gcc-4.0.1-obj 
 Ran ./configure 
 Ran make bootstrap 
 Ran make -k check 
 
The gcc result looks OK. 
 The g++ result does not. 
 
                === 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) 
 
The test is using /usr/bin/g++ instead of the 4.0.1 compiler I just built! 
 This looks like the problem I saw in g++ 3.4.0 
 http://gcc.gnu.org/ml/gcc-help/2004-05/msg00031.html 
 http://gcc.gnu.org/ml/gcc-help/2004-05/msg00087.html 
 
Does anyone have any ideas why this keeps happening? 
 Thanks 
----
> precisely what happened, 

gcc worked. g++ did not work.
 
                === 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) 

> what you  
> expected to happen instead, 
 
The test is using /usr/bin/g++ instead of the 4.0.1 compiler I just built! 
 This looks like the problem I saw in g++ 3.4.0 
 http://gcc.gnu.org/ml/gcc-help/2004-05/msg00031.html 
 http://gcc.gnu.org/ml/gcc-help/2004-05/msg00087.html 

> what version of the compiler you were 
> building, 
 
I've run configure in the directory ~/src/gcc/gcc-4.0.1-obj as 
 
leopardi@linfinit:~/src/gcc/gcc-4.0.1-obj> ../gcc-4.0.1/configure 
 --prefix=/usr/local/gcc/gcc-4.0.1 --enable-threads=posix --disable-libgcj 
 --with-system-zlib --enable-shared --enable-__cxa_atexit 
 --enable-languages=c,c++ x86_64-suse-linux 

> and what host you were running on.  
 
configure: warning: x86_64-suse-linux: invalid host type 

> So it's hard to know  
> what to say.
>
> Or, in other words, WORKSFORME.
>
> Ian

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

[Ian Lance Taylor]

"Paul C. Leopardi" <leopardi@bigpond.net.au> writes:

> leopardi@linfinit:~/src/gcc/gcc-4.0.1-obj> ../gcc-4.0.1/configure 
>  --prefix=/usr/local/gcc/gcc-4.0.1 --enable-threads=posix --disable-libgcj 
>  --with-system-zlib --enable-shared --enable-__cxa_atexit 
>  --enable-languages=c,c++ x86_64-suse-linux 
>  
> This looks like it worked, but gave the warning: 
>  
> configure: warning: x86_64-suse-linux: invalid host type 

This is not good, of course, though I doubt it is causing any of your
problems.  In general if you are building a native compiler you should
not need to specify any configuration triplet at all.

Can you confirm that the executables gcc/g++ and gcc/cc1plus exist?
What does site.exp look like in the gcc/testsuite subdirectory?  Does
it have the line "set TESTING_IN_BUILD_TREE 1"?  Which version of
dejagnu do you have installed?

Ian

Re: 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++" ?

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

[Ian Lance Taylor]

"Paul C. Leopardi" <leopardi@bigpond.net.au> writes:

> 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++" ?

No.  (Although --tool_executable=g++ would.)  But --tool g++ is
correct.  GXX_UNDER_TEST is normally set by the clauses after the ones
you showed.

> 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++" ?

GXX_UNDER_TEST has been set to /usr/bin/g++.

Ian

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

[H. J. Lu]

On Thu, Jul 28, 2005 at 10:53:02AM +1000, Paul C. Leopardi wrote:
> leopardi@linfinit:~/src/gcc/gcc-4.0.1-obj> ../gcc-4.0.1/configure 
>  --prefix=/usr/local/gcc/gcc-4.0.1 --enable-threads=posix --disable-libgcj 
>  --with-system-zlib --enable-shared --enable-__cxa_atexit 
>  --enable-languages=c,c++ x86_64-suse-linux 
>  
> This looks like it worked, but gave the warning: 
>  
> configure: warning: x86_64-suse-linux: invalid host type 

It is a known issue:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=122570

It shouldn't cause any problems.


H.J.

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

[Paul C. Leopardi]

Hi all, a quick follow-up below.
Best regards, Paul Leopardi
On Thu, 28 Jul 2005 12:04 pm, Paul C. Leopardi wrote:
> 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?
...
> 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?

I checked http://gcc.gnu.org/install/prerequisites.html
Under "Tools/packages necessary for modifying GCC" it has 

autogen version 5.5.4 (or later)

My fault, but... I'm just testing my bootstrap and am not intending to modify 
gcc, so I didn't pay attention to this section. Especially since the boostrap 
of gcc and g++ seemed to go OK this time. I now see that many of the other 
packages listed are also prerequsites for testing gcc and not only 
prerequisties for modifying gcc.

Maybe the heading should say:

"Tools/packages necessary for testing or modifying GCC" 

to save newbies like me from hours and hours of pain and frustration? 

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

[Ian Lance Taylor]

"Paul C. Leopardi" <leopardi@bigpond.net.au> writes:

> I checked http://gcc.gnu.org/install/prerequisites.html
> Under "Tools/packages necessary for modifying GCC" it has 
> 
> autogen version 5.5.4 (or later)
> 
> My fault, but... I'm just testing my bootstrap and am not intending to modify 
> gcc, so I didn't pay attention to this section. Especially since the boostrap 
> of gcc and g++ seemed to go OK this time. I now see that many of the other 
> packages listed are also prerequsites for testing gcc and not only 
> prerequisties for modifying gcc.
> 
> Maybe the heading should say:
> 
> "Tools/packages necessary for testing or modifying GCC" 
> 
> to save newbies like me from hours and hours of pain and frustration? 

No, autogen is generally not required to test the compiler.  That
isn't the problem you are encountering.

Ian

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

[Paul C. Leopardi]

Hi Ian, My replies are below, Best regards. Paul
On Thu, 28 Jul 2005 11:05 am, Ian Lance Taylor wrote:
> "Paul C. Leopardi" <leopardi@bigpond.net.au> writes:
> > leopardi@linfinit:~/src/gcc/gcc-4.0.1-obj> ../gcc-4.0.1/configure
> >  --prefix=/usr/local/gcc/gcc-4.0.1 --enable-threads=posix
> > --disable-libgcj --with-system-zlib --enable-shared --enable-__cxa_atexit
> >  --enable-languages=c,c++ x86_64-suse-linux
> >
> > This looks like it worked, but gave the warning:
> >
> > configure: warning: x86_64-suse-linux: invalid host type
>
> This is not good, of course, though I doubt it is causing any of your
> problems.  In general if you are building a native compiler you should
> not need to specify any configuration triplet at all.

OK

> Can you confirm that the executables gcc/g++ and gcc/cc1plus exist?

Yes, they exist.

leopardi@linfinit:~/src/gcc/gcc-4.0.1-obj/gcc> ls -l g++
-rwxr-xr-x  1 leopardi users 291700 2005-07-22 23:35 g++
leopardi@linfinit:~/src/gcc/gcc-4.0.1-obj/gcc> ls -l cc1plus
-rwxr-xr-x  1 leopardi users 21018697 2005-07-22 23:35 cc1plus

> What does site.exp look like in the gcc/testsuite subdirectory?
 
## these variables are automatically generated by make ##
# Do not edit here. If you wish to override these values
# add them to the last section
set rootme "/home/leopardi/src/gcc/gcc-4.0.1-obj/gcc"
set srcdir "/home/leopardi/src/gcc/gcc-4.0.1/gcc"
set host_triplet x86_64-suse-linux-gnu
set build_triplet x86_64-suse-linux-gnu
set target_triplet x86_64-suse-linux-gnu
set target_alias x86_64-suse-linux
set libiconv ""
set CFLAGS ""
set CXXFLAGS ""
set HOSTCC "gcc"
set HOSTCFLAGS "-g -O2"
set TESTING_IN_BUILD_TREE 1
set HAVE_LIBSTDCXX_V3 1
set tmpdir /home/leopardi/src/gcc/gcc-4.0.1-obj/gcc/testsuite
set srcdir "${srcdir}/testsuite"
## All variables above are generated by configure. Do Not Edit ##

> Does it have the line "set TESTING_IN_BUILD_TREE 1"?  

Yes

> Which version of dejagnu do you have installed?

dejagnu version 1.4.4
expect version 5.41
tcl version 8.4.7

leopardi@linfinit:~/src/gcc/gcc-4.0.1-obj/gcc/testsuite> rpm -q dejagnu 
dejagnu-1.4.4-3
leopardi@linfinit:~/src/gcc/gcc-4.0.1/gcc/testsuite/lib> rpm -q expect
expect-5.41-2
leopardi@linfinit:~/src/gcc/gcc-4.0.1/gcc/testsuite/lib> rpm -q tcl
tcl-8.4.7-3

(SOLVED) Re: GCC 4.0.1 testsuite uses installed g++ instead of newly bootstrapped g++

[Paul C. Leopardi]

Hi all, 
I've solved this. Thanks to Ian Lance Taylor, H. J. Lu and Mike Stump.
See below.
Best regards, Paul

I checked the output of make check-c++ RUNTESTFLAGS="-v" and noticed the line:
Found ~/.dejagnurc

In ~/.dejagnurc I found:
set GXX_UNDER_TEST "g++"

Judging form the modification date of the file, this is a hangover from May 
last year, when I reported "gcc 3.4.0 testsuit gives over 5000 g++ errors"
http://gcc.gnu.org/ml/gcc-help/2004-05/msg00008.html
It was still there later when I reported bug 15356, and has apparently been 
there ever since. At the time, I was using the Intel compiler as well as gcc 
and I was used to switching between the two via environment flags in .bashrc. 
I don't remember adding this line to .dejagnurc, but there it was.

I renamed .dejagnurc to old.dejagnurc. Running "make check-c++" in the gcc 
directory now results in:

(rootme=`${PWDCMD-pwd}`; export rootme; \
srcdir=`cd ../../gcc-4.0.1/gcc; ${PWDCMD-pwd}` ; export srcdir ; \
cd testsuite; \
EXPECT=`if [ -f ${rootme}/../expect/expect ] ; then echo 
${rootme}/../expect/expect ; else echo expect ; fi` ; 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 ; \
`if [ -f ${srcdir}/../dejagnu/runtest ] ; then echo 
${srcdir}/../dejagnu/runtest ; else echo runtest; fi` --tool g++ )
Test Run By leopardi on Fri Jul 29 01:18:57 2005
Native configuration is x86_64-suse-linux-gnu

		=== g++ tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for 
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /home/leopardi/src/gcc/gcc-4.0.1/gcc/testsuite/config/default.exp as 
tool-and-target-specific interface file.
Running /home/leopardi/src/gcc/gcc-4.0.1/gcc/testsuite/g++.dg/bprob/bprob.exp ...
Running /home/leopardi/src/gcc/gcc-4.0.1/gcc/testsuite/g++.dg/charset/charset.exp ...
Running /home/leopardi/src/gcc/gcc-4.0.1/gcc/testsuite/g++.dg/compat/compat.exp ...
Running /home/leopardi/src/gcc/gcc-4.0.1/gcc/testsuite/g++.dg/debug/debug.exp ...
Running /home/leopardi/src/gcc/gcc-4.0.1/gcc/testsuite/g++.dg/dg.exp ...
Running /home/leopardi/src/gcc/gcc-4.0.1/gcc/testsuite/g++.dg/gcov/gcov.exp ...
Running /home/leopardi/src/gcc/gcc-4.0.1/gcc/testsuite/g++.dg/pch/pch.exp ...
Running /home/leopardi/src/gcc/gcc-4.0.1/gcc/testsuite/g++.dg/special/ecos.exp ...
Running /home/leopardi/src/gcc/gcc-4.0.1/gcc/testsuite/g++.dg/tls/tls.exp ...
Running /home/leopardi/src/gcc/gcc-4.0.1/gcc/testsuite/g++.dg/vect/vect.exp ...
Running /home/leopardi/src/gcc/gcc-4.0.1/gcc/testsuite/g++.old-deja/old-deja.exp ...
XPASS: g++.old-deja/g++.other/init5.C execution test

		=== g++ Summary ===

# of expected passes		10894
# of unexpected successes	1
# of expected failures		69
# of unsupported tests		90
/home/leopardi/src/gcc/gcc-4.0.1-obj/gcc/testsuite/../g++  version 4.0.1

make: [check-g++] Error 1 (ignored)

Re: (SOLVED) Re: GCC 4.0.1 testsuite uses installed g++ instead of newly bootstrapped g++

[Joe Buck]

On Fri, Jul 29, 2005 at 01:46:12AM +1000, Paul C. Leopardi wrote:
> Hi all, 
> I've solved this. Thanks to Ian Lance Taylor, H. J. Lu and Mike Stump.
> See below.
> Best regards, Paul
> 
> I checked the output of make check-c++ RUNTESTFLAGS="-v" and noticed the line:
> Found ~/.dejagnurc
> 
> In ~/.dejagnurc I found:
> set GXX_UNDER_TEST "g++"

Glad you found this.  Your experience is why I've always objected when
someone suggests a .gccrc or a GCC_OPTIONS environment variable or the
like; people will forget that they have such files and report
unreproducible bugs.

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

[Mike Stump]

On Jul 27, 2005, at 7:04 PM, Paul C. Leopardi wrote:
> OK. Looks like a long term project.

Should be as easy as debugging three lines of code.  Insert a couple  
of printf's and voila.

>> Wild ass guess, did you type make -k check?
>
> Yes. Is there something wrong with that?

No, that is the right command.

> 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?

No.  I suspect you clobbered the timestamps on your files some how.   
Either, re-extract the tar ball preserving the times, or run contribe/ 
gcc_update -t to update them to be correct.  cvs update and cvs co  
will also yield the wrong times.

Should't hurt too much to do this, though, it can.

> 9.2. Should I just stop now, install autogen and try again?

No.

> Is the command "runtest --tool g++" correct?

cd gcc && make check-g++ is the canonical way to run it.

make RUNTESTFLAGS=old-deja.exp=eh6.C check-g++ will run it much faster.

configure the compiler with --prefix=/tmp/new, then add /tmp/new/bin  
to your path, then run the testsuite again.  Add /tmp/new/lib to  
LD_LIBRARY_PATH if thing still don't work.  Try again.

Type sh -c 'set' and review your environment for funny things.  Get  
rid of all the funny things.

Beyond that, either take our word for it that it is good, or roll up  
your sleeves and debug the tcl code near where it checks  
CXX_UNDER_TEST and find out why it is doing what it is doing.

Re: (SOLVED) Re: GCC 4.0.1 testsuite uses installed g++ instead of newly bootstrapped g++

[Nix]

On 28 Jul 2005, Joe Buck announced authoritatively:
> Glad you found this.  Your experience is why I've always objected when
> someone suggests a .gccrc or a GCC_OPTIONS environment variable or the
> like; people will forget that they have such files and report
> unreproducible bugs.

Instead, people can wrap GCC in shell scripts, use site-config files,
use automated build infrastructures... we already *have* ways to do
this, some with all the downsides of a .gccrc: the only advantage
is that things like specs files are ill-documented, so people don't
mess with them unless they know what they're doing.

Fundamentally, what we want is `gcc -v' output :) don't the bug
reporting guidelines already ask for this?

-- 
`Tor employs several thousand editors who they keep in dank
 subterranean editing facilities not unlike Moria' -- James Nicoll