From owner-freebsd-current Thu Aug 1 6: 0:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA75F37B401; Thu, 1 Aug 2002 06:00:36 -0700 (PDT) Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1E5943E6A; Thu, 1 Aug 2002 06:00:25 -0700 (PDT) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.6/8.11.6) id g71D0EB52936; Thu, 1 Aug 2002 15:00:14 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200208011300.g71D0EB52936@zibbi.icomtek.csir.co.za> Subject: Re: -current upgrade path broken? In-Reply-To: <20020801121635.GB26622@sunbay.com> from Ruslan Ermilov at "Aug 1, 2002 03:16:35 pm" To: ru@FreeBSD.org (Ruslan Ermilov) Date: Thu, 1 Aug 2002 15:00:14 +0200 (SAT) Cc: obrien@FreeBSD.org, peter@FreeBSD.org, current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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 -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message