[Bug c/31105] New: build broken (trunk rev 122742)

[Bug c/31105] New: build broken (trunk rev 122742)

[mtrudel at gmx dot ch]

/home/Marco/Desktop/compile-lin-lin/gcc-build/./prev-gcc/xgcc
-B/home/Marco/Desktop/compile-lin-lin/gcc-build/./prev-gcc/
-B/home/Marco/Desktop/compile-lin-lin/gcc-XYZXYZ-lin/i686-pc-linux-gnu/bin/ -c 
 -O2 -g -fomit-frame-pointer -DIN_GCC   -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long
-Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition
-Wmissing-format-attribute -Werror    -DHAVE_CONFIG_H -I. -I.
-I/usr/local/src/gcc/gcc -I/usr/local/src/gcc/gcc/.
-I/usr/local/src/gcc/gcc/../include -I/usr/local/src/gcc/gcc/../libcpp/include
-I/home/Marco/Desktop/compile-lin-lin/gmp-out/include
-I/home/Marco/Desktop/compile-lin-lin/mpfr-out/include
-I/usr/local/src/gcc/gcc/../libdecnumber -I../libdecnumber   
/usr/local/src/gcc/gcc/recog.c -o recog.o
cc1: warnings being treated as errors
/usr/local/src/gcc/gcc/recog.c: In function 'decode_asm_operands':
/usr/local/src/gcc/gcc/recog.c:1558: error: ISO C90 forbids mixed declarations
and code
/usr/local/src/gcc/gcc/recog.c:1600: error: ISO C90 forbids mixed declarations
and code
make[3]: *** [recog.o] Error 1
make[3]: Leaving directory `/home/Marco/Desktop/compile-lin-lin/gcc-build/gcc'

This strongly remembers me to http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30510
Is it possible that some flags trigger the "warnings being treated as errors"
but most developers don't use this? That would explain why people stumble over
it while it seems to work after changes for the developers?!

I configured with:
/usr/local/src/gcc/configure
--prefix=/home/Marco/Desktop/compile-lin-lin/gcc-XYZXYZ-lin
--with-sysroot=/home/Marco/Desktop/compile-lin-lin/gcc-XYZXYZ-lin/sys-root
--build=`/usr/local/src/gcc/config.guess` --host=i686-pc-linux-gnu
--target=i686-pc-linux-gnu --enable-languages=c,c++,java --enable-libgcj
--disable-shared --with-gnu-as --with-gnu-ld --disable-nls --disable-debug
--disable-checking --enable-threads=posix --disable-win32-registry
--enable-java-gc=boehm --enable-java-maintainer-mode
--with-gmp=/home/Marco/Desktop/compile-lin-lin/gmp-out
--with-mpfr=/home/Marco/Desktop/compile-lin-lin/mpfr-out


-- 
           Summary: build broken (trunk rev 122742)
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: mtrudel at gmx dot ch
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31105

[Bug c/31105] build broken (trunk rev 122742)

[rguenth at gcc dot gnu dot org]

------- Comment #1 from rguenth at gcc dot gnu dot org  2007-03-09 13:59 -------
Fixed by http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=122746


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31105

[Bug c/31105] build broken (trunk rev 122742)

[mtrudel at gmx dot ch]

------- Comment #2 from mtrudel at gmx dot ch  2007-03-09 14:12 -------
Thanks. But actually I also tried to start a discussion why such compilation
errors can happen:

This strongly remembers me to http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30510
Is it possible that some flags trigger the "warnings being treated as errors"
but most developers don't use this? That would explain why people stumble over
it while compilation seems to work for the developers?!

Of course I could be completely wrong. But if I'm right, there would be an easy
way to prevent such build breaks...


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31105

[Bug c/31105] build broken (trunk rev 122742)

[pinskia at gcc dot gnu dot org]

------- Comment #3 from pinskia at gcc dot gnu dot org  2007-03-09 17:14 -------
> Of course I could be completely wrong. But if I'm right, there would be an easy
> way to prevent such build breaks...

People make mistakes, this was just one of them.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31105

[Bug middle-end/31105] [4.3 Regression] build broken (trunk rev 122742)

[pinskia at gcc dot gnu dot org]

-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|c                           |middle-end
            Summary|build broken (trunk rev     |[4.3 Regression] build
                   |122742)                     |broken (trunk rev 122742)
   Target Milestone|---                         |4.3.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31105