[Bug bootstrap/26377] gcc 4.1.0 RC1 failes to bootstrap

2006-07-18 Thread pinskia at gcc dot gnu dot org
--- Comment #11 from pinskia at gcc dot gnu dot org 2006-07-19 03:44 --- This works for me and many other people. Also no feedback in 3 months so closing. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

Re: GCC 4.1.0 RC1

2006-02-23 Thread Rainer Emrich
Jim Wilson schrieb: Rainer Emrich wrote: /SCRATCH/gcc-build/Linux/ia64-unknown-linux-gnu/install/bin/ld: unrecognized option '-Wl,-rpath' This looks like PR 21206. See my explanation at the end. I see this on some of our FreeBSD machines, but I've never seen it on an IA-64 linux

Re: GCC 4.1.0 RC1

2006-02-23 Thread Bob Wilson
I ran the testsuite for an xtensa-elf target and it looks OK: http://gcc.gnu.org/ml/gcc-testresults/2006-02/msg01243.html There are a few failures but they are not regressions. --Bob

Re: GCC 4.1.0 RC1

2006-02-22 Thread Rainer Emrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Wilson schrieb: Rainer Emrich wrote: /SCRATCH/gcc-build/Linux/ia64-unknown-linux-gnu/install/bin/ld: unrecognized option '-Wl,-rpath' This looks like PR 21206. See my explanation at the end. I see this on some of our FreeBSD machines,

successful build of mingw hosted arm-elf GCC 4.1.0 RC1

2006-02-22 Thread Dave Murphy
output of config.guess $ gcc-4.1.0-20060219/config.guess i686-pc-mingw32 $ arm-elf-gcc -v Using built-in specs. Target: arm-elf Configured with: ../../gcc-4.1.0-20060219/configure --enable-languages=c,c++ --with-cpu=arm7tdmi --enable-interwork --enable-multilib --with-gcc --with-gnu-ld

Re: GCC 4.1.0 RC1

2006-02-21 Thread Grigory Zagorodnev
Mark Mitchell wrote: GCC 4.1.0 RC1 is here: ftp://gcc.gnu.org/pub/gcc/prerelease-4.1.0-20060219 Please download, build, and test. Please use these tarballs, rather than the current SVN branch, so that we test packaging, and other similar issues. If you find problems, please do not send me

Re: GCC 4.1.0 RC1

2006-02-21 Thread Andrew Pinski
On Feb 21, 2006, at 6:09 AM, Grigory Zagorodnev wrote: Hi! My spec cpu2000 run shows 252.eon miscompared with i686-redhat-linux 4.1.0 20060221 (prerelease) compiler. Optimization level is -O2. Spec reported miscompare of pixels_out.kajiya. Has anybody seen this before? Yes this is PR 323,

Re: GCC 4.1.0 RC1

2006-02-21 Thread Paolo Bonzini
Hi! My spec cpu2000 run shows 252.eon miscompared with i686-redhat-linux 4.1.0 20060221 (prerelease) compiler. Optimization level is -O2. Spec reported miscompare of pixels_out.kajiya. Has anybody seen this before? You should use -ffast-math for eon. Paolo

Re: GCC 4.1.0 RC1

2006-02-21 Thread H. J. Lu
On Tue, Feb 21, 2006 at 02:09:43PM +0300, Grigory Zagorodnev wrote: Mark Mitchell wrote: GCC 4.1.0 RC1 is here: ftp://gcc.gnu.org/pub/gcc/prerelease-4.1.0-20060219 Please download, build, and test. Please use these tarballs, rather than the current SVN branch, so that we test packaging

Re: GCC 4.1.0 RC1

2006-02-21 Thread Jim Wilson
Rainer Emrich wrote: /SCRATCH/gcc-build/Linux/ia64-unknown-linux-gnu/install/bin/ld: unrecognized option '-Wl,-rpath' This looks like PR 21206. See my explanation at the end. I see this on some of our FreeBSD machines, but I've never seen it on an IA-64 linux machine. -- Jim Wilson, GNU

Re: GCC 4.1.0 RC1

2006-02-20 Thread Greg Schafer
Mark Mitchell wrote: Please download, build, and test. Please use these tarballs, rather than the current SVN branch, so that we test packaging, and other similar issues. Here it looks good so far on i686-pc-linux-gnu http://gcc.gnu.org/ml/gcc-testresults/2006-02/msg01036.html Regards Greg

RE: GCC 4.1.0 RC1

2006-02-20 Thread Rainer Emrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bootstrap failure in libjava on ia64-unknown-linux-gnu. Failure in building jv-convert: /bin/sh ./libtool --tag=GCJ --mode=link /disk1/SCRATCH/gcc-build/Linux/ia64-unknown-linux-gnu/gcc-4.1.0-RC1/gcc-4.1.0-RC1/gcc/gcj - -B/disk1/SCRATCH/gcc-build

Re: GCC 4.1.0 RC1

2006-02-20 Thread Laurent GUERBY
On Mon, 2006-02-20 at 19:40 +1100, Greg Schafer wrote: Mark Mitchell wrote: Please download, build, and test. Please use these tarballs, rather than the current SVN branch, so that we test packaging, and other similar issues. Here it looks good so far on i686-pc-linux-gnu

Re: GCC 4.1.0 RC1

2006-02-20 Thread Andrew Pinski
On Feb 20, 2006, at 6:30 PM, Laurent GUERBY wrote: one libstdc++ amd64 FAIL: FAIL: abi_check That is because you did not supply --enable-__cxa_atexit to configure. This has been mentioned so many times it might as well enabled it by default for GNU/Linux. -- Pinski

Re: GCC 4.1.0 RC1

2006-02-20 Thread Ulrich Weigand
Mark Mitchell wrote: GCC 4.1.0 RC1 is here: ftp://gcc.gnu.org/pub/gcc/prerelease-4.1.0-20060219 Looking fine on s390-ibm-linux and s390x-ibm-linux: http://gcc.gnu.org/ml/gcc-testresults/2006-02/msg01094.html http://gcc.gnu.org/ml/gcc-testresults/2006-02/msg01095.html except for the recently

Re: GCC 4.1.0 RC1

2006-02-20 Thread Laurent GUERBY
On Mon, 2006-02-20 at 18:34 -0500, Andrew Pinski wrote: On Feb 20, 2006, at 6:30 PM, Laurent GUERBY wrote: one libstdc++ amd64 FAIL: FAIL: abi_check That is because you did not supply --enable-__cxa_atexit to configure. This has been mentioned so many times it might as well enabled

Re: GCC 4.1.0 RC1

2006-02-20 Thread Eric Botcazou
http://gcc.gnu.org/ml/gcc-testresults/2006-02/msg01095.html FAIL: cc1010b Artifact or real failure? -- Eric Botcazou

Re: GCC 4.1.0 RC1

2006-02-20 Thread Ulrich Weigand
Eric Botcazou [EMAIL PROTECTED] wrote on 21.02.2006 01:10:58: http://gcc.gnu.org/ml/gcc-testresults/2006-02/msg01095.html FAIL: cc1010b Artifact or real failure? One of the usual artifacts ... Mit freundlichen Gruessen / Best Regards Ulrich Weigand -- Dr. Ulrich Weigand GNU

Re: GCC 4.1.0 RC1

2006-02-20 Thread Eric Botcazou
One of the usual artifacts ... Thanks. I've personally got them on Linux only, never ever on Solaris. -- Eric Botcazou

Re: GCC 4.1.0 RC1

2006-02-20 Thread Jakub Jelinek
On Tue, Feb 21, 2006 at 12:45:15AM +0100, Ulrich Weigand wrote: except for the recently introduced test case FAIL: gcc.dg/20060218-1.c (test for errors, line 6) FAIL: gcc.dg/20060218-1.c (test for excess errors) This one should be already fixed on gcc-4_1-branch (after RC1 was released I

[Bug bootstrap/26377] New: gcc 4.1.0 RC1 failes to bootstrap

2006-02-20 Thread xtv at tveith dot homelinux dot com
gcc 4.1.0 rc1 failes to bootstrap on my amd64 gentoo-box; the last release gcc-4.1.0-20060217 bootstraps fine so it seems to be rc1 and not my gentoo setup. ../gcc-4.1.0-20060219/configure --prefix=/home/xtv --program-prefix=x --program-suffix=41rc1 --enable-languages=c,c++,objc,obj-c++,fortran

[Bug bootstrap/26377] gcc 4.1.0 RC1 failes to bootstrap

2006-02-20 Thread themis_hv at yahoo dot co dot uk
--- Comment #1 from themis_hv at yahoo dot co dot uk 2006-02-20 09:19 --- GCC here is expecting ld to be located at /home/xtv/bin/xld Try adding --with-ld=/path/to/ld and --with-as=/path/to/as to configury See if this makes any difference --

[Bug bootstrap/26377] gcc 4.1.0 RC1 failes to bootstrap

2006-02-20 Thread xtv at tveith dot homelinux dot com
--- Comment #2 from xtv at tveith dot homelinux dot com 2006-02-20 09:52 --- (In reply to comment #1) GCC here is expecting ld to be located at /home/xtv/bin/xld Try adding --with-ld=/path/to/ld and --with-as=/path/to/as to configury See if this makes any difference The

[Bug bootstrap/26377] gcc 4.1.0 RC1 failes to bootstrap

2006-02-20 Thread xtv at tveith dot homelinux dot com
--- Comment #3 from xtv at tveith dot homelinux dot com 2006-02-20 12:33 --- Without --program-prefix it bootstraps fine. So it seems to be a problem with the configure-machinery. Shall I close this bug and open a new one regarding configure? --

[Bug bootstrap/26377] gcc 4.1.0 RC1 failes to bootstrap

2006-02-20 Thread pinskia at gcc dot gnu dot org
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-02-20 13:06 --- If this worked with 20060217 and does not with the RC1, this actually does not make sense as there have been no configuring changes made between that time. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26377

[Bug bootstrap/26377] gcc 4.1.0 RC1 failes to bootstrap

2006-02-20 Thread themis_hv at yahoo dot co dot uk
--- Comment #5 from themis_hv at yahoo dot co dot uk 2006-02-20 13:12 --- --program-prefix works fine on i686-pc-linux with GCC 4.1.0 RC 1 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26377

[Bug bootstrap/26377] gcc 4.1.0 RC1 failes to bootstrap

2006-02-20 Thread pinskia at gcc dot gnu dot org
--- Comment #6 from pinskia at gcc dot gnu dot org 2006-02-20 19:54 --- I just tried to reproduce this with exactly the options you used and I could not. I then tried with a different prefix of /home/pinskia (my home directory) and it still worked. Is there something special with your

[Bug bootstrap/26377] gcc 4.1.0 RC1 failes to bootstrap

2006-02-20 Thread xtv at tveith dot homelinux dot com
--- Comment #7 from xtv at tveith dot homelinux dot com 2006-02-20 20:24 --- Hi.. whenever I use --program-prefix, bootstrap fails / otherwise it works just perfect. To illustrate, this time i used the following configure: ../gcc-4.1.0-20060219/configure --prefix=/home/xtv

[Bug bootstrap/26377] gcc 4.1.0 RC1 failes to bootstrap

2006-02-20 Thread themis_hv at yahoo dot co dot uk
--- Comment #8 from themis_hv at yahoo dot co dot uk 2006-02-20 20:57 --- Do you have any of the following variables set before building GCC: LD DEFAULT_LINKER ORIGINAL_LD_FOR_TARGET CONFIG_SITE ? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26377

[Bug bootstrap/26377] gcc 4.1.0 RC1 failes to bootstrap

2006-02-20 Thread xtv at tveith dot homelinux dot com
--- Comment #9 from xtv at tveith dot homelinux dot com 2006-02-20 21:05 --- (In reply to comment #8) Do you have any of the following variables set before building GCC: LD DEFAULT_LINKER ORIGINAL_LD_FOR_TARGET CONFIG_SITE No: [EMAIL PROTECTED] ~/gcc/out $ echo $LD [EMAIL

[Bug bootstrap/26377] gcc 4.1.0 RC1 failes to bootstrap

2006-02-20 Thread pinskia at gcc dot gnu dot org
--- Comment #10 from pinskia at gcc dot gnu dot org 2006-02-21 02:19 --- (In reply to comment #9) autoconf-2.59 automake-1.9.6 binutils-2.16.1 Maybe thats the reason.. I doubt it. Maybe you have a messed up coreutils. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26377