Don Lewis wrote:
> It appears that the problem is that cvsup10 is sick.  It doesn't have a
> complete set of the gcc updates.  I was only getting rev 1.2 of
> emit-rtl.c, but rev 1.3 was committed 36 hours ago.  I got the correct
> version of that file plus a bunch of other stuff when I switched to
> cvsup13.

Argh.  Out of disk space.  Fixing now.

> 
> On  3 Sep, Don Lewis wrote:
> > On  1 Sep, Alexander Kabaev wrote:
> >> GCC 3.2.1-pre is now in the tree. Please let me know if you see any
> >> problems recompiling your world/kernel.
> > 
> > I haven't seen any other reports of this problem.  I'm upgrading from
> > a September 1st version of -current.
> > 
> > cc -O -pipe -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/usr/src/i386/usr\"
     -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc1/../cc_tools -I/usr/src/
    gnu/usr.bin/cc/cc1/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc1/../../../../co
    ntrib/gcc -I/usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/config -I. 
       -D__FBSDID=__RCSID -c /usr/src/contrib/gcc/c-decl.c
> > cc -O -pipe -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/usr/src/i386/usr\"
     -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc1/../cc_tools -I/usr/src/
    gnu/usr.bin/cc/cc1/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc1/../../../../co
    ntrib/gcc -I/usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/config -I. 
       -D__FBSDID=__RCSID  -static -o cc1 main.o c-parse+%DIKED.o c-lang.o c-de
    cl.o /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc1/../cc_int/libcc_int.a
> > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc1/../cc_int/libcc_int.a(i386
    .o): In function `ix86_expand_int_movcc':
> > i386.o(.text+0x7bf5): undefined reference to `gen_int_mode'
> > *** Error code 1
> > 
> > Stop in /usr/src/gnu/usr.bin/cc/cc1.
> > *** Error code 1
> 
> 

Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to