This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 4.0.1 testsuite uses installed g++ instead of newly bootstrapped g++
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