------- Comment #3 from kargl at gcc dot gnu dot org 2009-04-30 16:35 ------- (In reply to comment #2) > (In reply to comment #1) > > Change Severity to normal. Fortran bugs are never major. > > > > AFAIK, there will be no further releases from the gcc-4.1.x branch, > > so it is highly unlikely that this bug will be fixed. gcc-4.4.0 > > was released a week or so ago. Try using it. You'll find that > > gfortran in 4.4.0 is much, much, much, better than the compiler in > > 4.1.2 (a two year old piece of software). > > > > Thanks for the quick replay. > > Unfortunately, I have just tried with gcc-4.4.0 and it gives a similar error. > Now I used: > /home2/gdb/local/src/gcc-4.4.0/configure --prefix=/home2/gdb/local/gcc-4.4.0 > --enable-languages=c,fortran --with-as=/home2/gdb/local/binutils-2.18/bin/as > --with-ld=/home2/gdb/local/binutils-2.18/bin/ld > > I copied gmp-4.2.4 and and mpfr-2.4.1 within the source, so as to build > everything together. Also tried with other versions of gmp, mpfr and binutils > getting always the same error. >
If 4.4.0 doesn't build on your i686-pc-linux-gnu system, then something is definitely broken but it's not gfortran. Do you have an older version of MPFR or GMP installed in /usr/local? This can sometimes cause problems. What happens if you use the system's ld and as? -- kargl at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39971