This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
g++ Problems
- To: gcc-bugs at gcc dot gnu dot org
- Subject: g++ Problems
- From: David Ronis <ronis at montroll dot chem dot mcgill dot ca>
- Date: Wed, 12 Jan 2000 13:55:03 -0500
- CC: gcc at gcc dot gnu dot org
- Reply-to: ronis at onsager dot chem dot mcgill dot ca
I've been having some problems with g++ on an i686 Slackware-7.0
system. I reported a simple testcase in
http://gcc.gnu.org/ml/gcc-bugs/2000-01/msg00269.html
but I've realized that the problem may be something else. If I try my
test on another machine (i586, linux-2.2.14, gcc-2.2.95, glibc-2.1.2)
there are no problems.
In addition, I've posted testresults for the lastest snapshot on this
machine and on an i586 at
http://gcc.gnu.org/ml/gcc-testresults/2000-01/msg00078.html
and
http://gcc.gnu.org/ml/gcc-testresults/2000-01/msg00095.html
respectively. There is a huge difference in g++ failures on the two
machines. I used gcc-2.95.2 to build glibc-2.1.2 on the i586 but have
used the default Slackware glibc-2.1.2 on the i686 (compiled with
egcs-1.1.2, the default compiler, I presume).
Presumably some library is no longer compatible. Any idea what? Of
course, if it's the glibc-2.1.2 library, how do I go about fixing this
without breaking everything else on my system?
David