Re: HEADS UP: cvs repository surgery
>Date: Fri, 09 Nov 2001 15:23:12 -0800 >From: Peter Wemm <[EMAIL PROTECTED]> >This is certainly unrelated.. gdb (and gdb.291) was not touched. >Secondly, I only did src/contrib/gcc, not gcc.295.. The -current compiler >is unchanged at this stage. If this started happening on 4.x then I'd >be worried since 4.x is using src/contrib/gcc. Well, after an email exchange with David O'Brien, I "cloned" the -CURRENT slice in question (copied slice 4 to slice 3, and adjusted fstab), blew away /usr/src on slice 3, did a "cvs co" from the same repository, re-applied some local patches I've been testing, re-booted from slice 3, started the buildworld & friends over, and it worked like a charm. Somewhat emboldened (albeit rather puzzled) by that, I re-booted back to slice 4 (where I had been doing the -CURRENT festivities), re-did the buildworld & friends... and it (also) worked like a charm: freebeast[1] uname -a FreeBSD freebeast.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #40: Fri Nov 9 20:00:56 PST 2001 [EMAIL PROTECTED]:/common/S4/obj/usr/src/sys/FREEBEAST i386 freebeast[2] Sorry about the false alarm. :-( Color me perplexed, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: cvs repository surgery
David Wolfskill wrote: > >Date: Thu, 08 Nov 2001 16:16:25 -0800 > >From: Peter Wemm <[EMAIL PROTECTED]> > > >Some history revisionism has taken place in the src/contrib area as part > >of making way for the next gcc update. > > >Do not be alarmed when you see your next cvsup output (in cvs mode, not > >-checkout mode). > > :-} > > >I am aware of a couple of minor problems, but I dont think they break > >anything But if something (eg: cvs, cvsup, etc) does break, I need to know > >about it. cvs or cvsup doing 'fixups' or reporting checksum errors is > >expected and should only happen once > > >Yes, there are some intentional differences between gcc and gcc.295 etc due > >to some commits being deliberately left out. > > OK; I think the following may qualify as something broken that you > requested notification about: This is certainly unrelated.. gdb (and gdb.291) was not touched. Secondly, I only did src/contrib/gcc, not gcc.295.. The -current compiler is unchanged at this stage. If this started happening on 4.x then I'd be worried since 4.x is using src/contrib/gcc. > >>> stage 4: building everything.. > ... > ===> gnu/usr.bin/binutils/gdb > ... > cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386 - I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../l ibbfd/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils /include -Dprint_insn_i386=print_insn_i386_att -I/usr/src/gnu/usr.bin/binut ils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binuti ls/binutils -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutil s/bfd -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb - I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/config - DFREEBSD_ELF -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/obj/usr/src/i386/us r/include/readline -DNO_MMALLOC -I/usr/obj/usr/src/i386/usr/include -c / usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/scm-exp.c > cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386 - I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../l ibbfd/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils /include -Dprint_insn_i386=print_insn_i386_att -I/usr/src/gnu/usr.bin/binut ils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binuti ls/binutils -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutil s/bfd -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb - I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/config - DFREEBSD_ELF -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/obj/usr/src/i386/us r/include/readline -DNO_MMALLOC -I/usr/obj/usr/src/i386/usr/include -c / usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/scm-lang.c > cc: Internal compiler error: program cc1 got fatal signal 11 > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > freebeast[2] > > > The system in question: > freebeast[2] uname -a > FreeBSD freebeast.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #39: Thu Nov 8 07:37:49 PST 2001 [EMAIL PROTECTED]:/common/S4/obj/usr/ src/sys/FREEBEAST i386 > > and recent CVSup history: > freebeast[3] tail /var/log/cvsup-history.log > CVSup begin from cvsup14.freebsd.org at Mon Nov 5 03:47:00 PST 2001 > CVSup ended from cvsup14.freebsd.org at Mon Nov 5 03:53:54 PST 2001 > CVSup begin from cvsup14.freebsd.org at Tue Nov 6 03:47:00 PST 2001 > CVSup ended from cvsup14.freebsd.org at Tue Nov 6 03:53:16 PST 2001 > CVSup begin from cvsup14.freebsd.org at Wed Nov 7 03:47:00 PST 2001 > CVSup ended from cvsup14.freebsd.org at Wed Nov 7 03:53:06 PST 2001 > CVSup begin from cvsup14.freebsd.org at Thu Nov 8 03:47:00 PST 2001 > CVSup ended from cvsup14.freebsd.org at Thu Nov 8 03:53:09 PST 2001 > CVSup begin from cvsup14.freebsd.org at Fri Nov 9 03:47:00 PST 2001 > CVSup ended from cvsup14.freebsd.org at Fri Nov 9 03:55:59 PST 2001 > > (Yes, each of those CVSups also corresponds to successful build & boot of > -CURRENT (and -STABLE: that's updating my own copy of the CVS repository). > I did a quick check of the archives of cvs-all, but didn't see anything > recent hitting gcc there. > > Cheers, > david > -- > David H. Wolfskill[EMAIL PROTECTED] > As a computing professional, I believe it would be unethical for me to > advise, recommend, or support the use (save possibly for personal > amusement) of any product that is or depends on any Microsoft product. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED];
Re: HEADS UP: cvs repository surgery
On Fri, Nov 09, 2001 at 07:39:28AM -0800, David Wolfskill wrote: > >Yes, there are some intentional differences between gcc and gcc.295 etc due > >to some commits being deliberately left out. > > OK; I think the following may qualify as something broken that you > requested notification about: This is *very* strange: > ===> gnu/usr.bin/binutils/gdb > ... > cc -O -pipe -D_GNU_SOURCE -I- -I. >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb Thus this is -current. However, current is still using src/contrib/gcc.295, so you should see zero problems in HEAD. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: cvs repository surgery
>Date: Thu, 08 Nov 2001 16:16:25 -0800 >From: Peter Wemm <[EMAIL PROTECTED]> >Some history revisionism has taken place in the src/contrib area as part >of making way for the next gcc update. >Do not be alarmed when you see your next cvsup output (in cvs mode, not >-checkout mode). :-} >I am aware of a couple of minor problems, but I dont think they break >anything But if something (eg: cvs, cvsup, etc) does break, I need to know >about it. cvs or cvsup doing 'fixups' or reporting checksum errors is >expected and should only happen once >Yes, there are some intentional differences between gcc and gcc.295 etc due >to some commits being deliberately left out. OK; I think the following may qualify as something broken that you requested notification about: >>> stage 4: building everything.. ... ===> gnu/usr.bin/binutils/gdb ... cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include -Dprint_insn_i386=print_insn_i386_att -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/binutils -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/bfd -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/config -DFREEBSD_ELF -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/obj/usr/src/i386/usr/include/readline -DNO_MMALLOC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/scm-exp.c cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include -Dprint_insn_i386=print_insn_i386_att -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/binutils -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/bfd -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/config -DFREEBSD_ELF -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/obj/usr/src/i386/usr/include/readline -DNO_MMALLOC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/scm-lang.c cc: Internal compiler error: program cc1 got fatal signal 11 *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error freebeast[2] The system in question: freebeast[2] uname -a FreeBSD freebeast.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #39: Thu Nov 8 07:37:49 PST 2001 [EMAIL PROTECTED]:/common/S4/obj/usr/src/sys/FREEBEAST i386 and recent CVSup history: freebeast[3] tail /var/log/cvsup-history.log CVSup begin from cvsup14.freebsd.org at Mon Nov 5 03:47:00 PST 2001 CVSup ended from cvsup14.freebsd.org at Mon Nov 5 03:53:54 PST 2001 CVSup begin from cvsup14.freebsd.org at Tue Nov 6 03:47:00 PST 2001 CVSup ended from cvsup14.freebsd.org at Tue Nov 6 03:53:16 PST 2001 CVSup begin from cvsup14.freebsd.org at Wed Nov 7 03:47:00 PST 2001 CVSup ended from cvsup14.freebsd.org at Wed Nov 7 03:53:06 PST 2001 CVSup begin from cvsup14.freebsd.org at Thu Nov 8 03:47:00 PST 2001 CVSup ended from cvsup14.freebsd.org at Thu Nov 8 03:53:09 PST 2001 CVSup begin from cvsup14.freebsd.org at Fri Nov 9 03:47:00 PST 2001 CVSup ended from cvsup14.freebsd.org at Fri Nov 9 03:55:59 PST 2001 (Yes, each of those CVSups also corresponds to successful build & boot of -CURRENT (and -STABLE: that's updating my own copy of the CVS repository). I did a quick check of the archives of cvs-all, but didn't see anything recent hitting gcc there. Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP: cvs repository surgery
Some history revisionism has taken place in the src/contrib area as part of making way for the next gcc update. Do not be alarmed when you see your next cvsup output (in cvs mode, not -checkout mode). I am aware of a couple of minor problems, but I dont think they break anything But if something (eg: cvs, cvsup, etc) does break, I need to know about it. cvs or cvsup doing 'fixups' or reporting checksum errors is expected and should only happen once. ie: it should be recovered from automaticaly and NOT happen next time. I only want to know if: - something is corrupted - cvs or cvsup or some other tool crash or report persistant errors - source is corrupted, particularly in RELENG_4. Yes, there are some intentional differences between gcc and gcc.295 etc due to some commits being deliberately left out. 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
