Re: -current upgrade path broken?
On Thu, Aug 01, 2002 at 09:51:25AM -0700, David O'Brien wrote: On Thu, Aug 01, 2002 at 03:16:35PM +0300, Ruslan Ermilov wrote: I have stumbled to this too, and thought I'm getting crazy. After some hours of investigation, I have found that O'Brien did some repo-surgery there, removed some revisions, and later replaced them with the new stuff (well, new stuff took the same revisions), and now some of your checked out sources (revisions) do not match what's in your CVS repository. Since you did not provde details I don't know exactly what you are talking about or when this repo surgery was to have taken place. But yes, Peter did back out some revs several months ago. Huh?! Read the first posting in this thread. I suggest that you do forced commits to contrib/gcc/config/i386/*.h (probably other arches too) that were surgered. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg41617/pgp0.pgp Description: PGP signature
Re: -current upgrade path broken?
On Fri, Aug 02, 2002 at 11:09:23AM +0300, Ruslan Ermilov wrote: Huh?! Read the first posting in this thread. I suggest that you do forced commits to contrib/gcc/config/i386/*.h (probably other arches too) that were surgered. I already did 2 forced committs. See some of Peter's email on the topic of why the forced commits wont always fix the problem. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current upgrade path broken?
On Fri, Aug 02, 2002 at 04:21:25AM -0700, David O'Brien wrote: On Fri, Aug 02, 2002 at 11:09:23AM +0300, Ruslan Ermilov wrote: Huh?! Read the first posting in this thread. I suggest that you do forced commits to contrib/gcc/config/i386/*.h (probably other arches too) that were surgered. I already did 2 forced committs. See some of Peter's email on the topic of why the forced commits wont always fix the problem. Would you be so kind to tell me the Message-ID's and/or Subject:'s of his emails? Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg41623/pgp0.pgp Description: PGP signature
-current upgrade path broken?
Should one be able to do a source upgrade from an old -current (March 10) to the latest? I have been trying, but it breaks in the cross tools section in gnu/usr.bin/cc/cc_int. mkdep fails. There are a lot of warnings that looks like this: # /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/unix.h:70: warning: `TARGET_DEFAULT' redefined /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/i386.h:400: warning: this is the location of the previous definition /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/unix.h:83: warning: `FUNCTION_VALUE_REGNO_P' redefined /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/i386.h:1654: warning: this is the location of the previous definition ## I don't think they cause the failure, but there are so many of them that they are hiding the real stuff. I think what is breaking mkdep is this: # /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/varasm.c:598: macro `SELECT_SECTION' used with too many (3) args /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/varasm.c:3400: macro `SELECT_SECTION' used with too many (3) args /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/varasm.c:4006: macro `SELECT_RTX_SECTION' used with too many (3) args ... mkdep: compile failed *** Error code 1 Stop in /home/src/gnu/usr.bin/cc/cc_int. *** Error code 1 Stop in /home/src/gnu/usr.bin/cc. *** Error code 1 Stop in /home/src. *** Error code 1 Stop in /home/src. *** Error code 1 Stop in /home/src. # John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current upgrade path broken?
I have stumbled to this too, and thought I'm getting crazy. After some hours of investigation, I have found that O'Brien did some repo-surgery there, removed some revisions, and later replaced them with the new stuff (well, new stuff took the same revisions), and now some of your checked out sources (revisions) do not match what's in your CVS repository. rm -rf /usr/src/contrib/gcc and /usr/src/gnu/usr.bin/cc, check them out again, and try again. It worked for me now. I hope that people will learn the lessons from this, and won't be doing such scary things in the future. Peter had some work-arounds to avoid problems like this, were these forced commits over the affected files, I don't remember? On Thu, Aug 01, 2002 at 12:47:38PM +0200, John Hay wrote: Should one be able to do a source upgrade from an old -current (March 10) to the latest? I have been trying, but it breaks in the cross tools section in gnu/usr.bin/cc/cc_int. mkdep fails. There are a lot of warnings that looks like this: # /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/unix.h:70: warning: `TARGET_DEFAULT' redefined /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/i386.h:400: warning: this is the location of the previous definition /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/unix.h:83: warning: `FUNCTION_VALUE_REGNO_P' redefined /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/i386.h:1654: warning: this is the location of the previous definition ## I don't think they cause the failure, but there are so many of them that they are hiding the real stuff. I think what is breaking mkdep is this: # /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/varasm.c:598: macro `SELECT_SECTION' used with too many (3) args /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/varasm.c:3400: macro `SELECT_SECTION' used with too many (3) args /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/varasm.c:4006: macro `SELECT_RTX_SECTION' used with too many (3) args ... mkdep: compile failed *** Error code 1 Stop in /home/src/gnu/usr.bin/cc/cc_int. *** Error code 1 Stop in /home/src/gnu/usr.bin/cc. *** Error code 1 Stop in /home/src. *** Error code 1 Stop in /home/src. *** Error code 1 Stop in /home/src. # John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg41570/pgp0.pgp Description: PGP signature
Re: -current upgrade path broken?
Yup, you are right, thanks. I remember about the problem, but did not remember the symptoms of it, so didn't put two and two together. :-( I have stumbled to this too, and thought I'm getting crazy. After some hours of investigation, I have found that O'Brien did some repo-surgery there, removed some revisions, and later replaced them with the new stuff (well, new stuff took the same revisions), and now some of your checked out sources (revisions) do not match what's in your CVS repository. rm -rf /usr/src/contrib/gcc and /usr/src/gnu/usr.bin/cc, check them out again, and try again. It worked for me now. I hope that people will learn the lessons from this, and won't be doing such scary things in the future. Peter had some work-arounds to avoid problems like this, were these forced commits over the affected files, I don't remember? ... I don't think they cause the failure, but there are so many of them that they are hiding the real stuff. I think what is breaking mkdep is this: # /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/varasm.c:598: macro `SELECT_SECTION' used with too many (3) args /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/varasm.c:3400: macro `SELECT_SECTION' used with too many (3) args /home/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/varasm.c:4006: macro `SELECT_RTX_SECTION' used with too many (3) args ... mkdep: compile failed ... John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current upgrade path broken?
On Thu, Aug 01, 2002 at 03:16:35PM +0300, Ruslan Ermilov wrote: I have stumbled to this too, and thought I'm getting crazy. After some hours of investigation, I have found that O'Brien did some repo-surgery there, removed some revisions, and later replaced them with the new stuff (well, new stuff took the same revisions), and now some of your checked out sources (revisions) do not match what's in your CVS repository. Since you did not provde details I don't know exactly what you are talking about or when this repo surgery was to have taken place. But yes, Peter did back out some revs several months ago. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
