This is the mail archive of the
mailing list for the GCC project.
Re: GCC 3.2 on Mandrake 8.2
- From: Janis Johnson <janis187 at us dot ibm dot com>
- To: Ján Karabás <6karabas at fpv dot umb dot sk>
- Cc: gcc at gnu dot org
- Date: Fri, 23 Aug 2002 09:29:06 -0700
- Subject: Re: GCC 3.2 on Mandrake 8.2
- References: <email@example.com>
On Fri, Aug 23, 2002 at 09:21:11AM +0200, Ján Karabás wrote:
> [root@jk build]# /opt/TEMP/gcc-3.2/config.guess
> GCC VERSION
> [root@jk build]# /opt/gcc-3.2/bin/gcc -v
> Reading specs from /opt/gcc-3.2/lib/gcc-lib/i686-pc-linux/3.2/specs
> Configured with: /opt/TEMP/gcc-3.2/configure --target=i686-pc-linux
> --prefix=/opt/gcc-3.2 --enable-shared --enable-threads=posix
> Thread model: posix
> gcc version 3.2
> full installation, all languages except Ada
> Mandrake Linux release 8.2 (BlueBird) for i586
> Kernel 2.4.18-6mdk on an i686
> [root@jk build]# uname -a
> Linux jk.imi.sk 2.4.18-6mdk #1 Fri Mar 15 02:59:08 CET 2002 i686 unknown
> [root@jk build]# rpm -q glibc
Thanks! Your message is linked from the GCC 3.2 build status list at
> GCC seems to be OK, but testsuite crashes every run. I am not able to mail
> testresults, script test_summary fails:
Does it really crash, or does the make fail? You need to use "make -k".
> [root@jk build]# /opt/TEMP/gcc-3.2/contrib/test_summary -p ./gcc_32.txt -m
> firstname.lastname@example.org | sh
> tail: /opt/TEMP/gcc-3.2/LAST_UPDATED: Adresár alebo súbor neexistuje %%(File
> or directory does not exist)
Hmmm, the file LAST_UPDATED is in a CVS tree but not in a release tree.
This script works for most people, though; perhaps your shell settings
are different? You could comment out the part of test_summary that
looks at that file and then look at the generated script rather than
executing it immediately to see how far it got.
> I have installed GCC 3.2 two times. Many fails in test of Java.
The Java failures are probably due to a known problem in the test suite
that will be fixed in 3.2.1, and that can be worked around by doing
"make install" before "make -k check".