From owner-freebsd-stable Sat Sep 18 20:53: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from internet.madriver.k12.oh.us (madriver.k12.oh.us [156.63.175.141]) by hub.freebsd.org (Postfix) with SMTP id 09BF914D25 for ; Sat, 18 Sep 1999 20:53:00 -0700 (PDT) (envelope-from MWhite@madriver.k12.oh.us) Received: from Mad_River-Message_Server by internet.madriver.k12.oh.us with Novell_GroupWise; Sat, 18 Sep 1999 23:53:00 -0400 Message-Id: X-Mailer: Novell GroupWise 5.5 Date: Sat, 18 Sep 1999 23:52:34 -0400 From: "Matt White" To: Subject: =?ISO-8859-7?Q?RE:=20Problems=20building=203.3=20=AF=20SOULTION?= Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Blowing away /usr/src worked. (Note: Be sure you backup your kernel = config file before doing this!) After this error I started having gcc dump core quite building the world. = Normally I assume this means hardware, but I suppose not in this case. It = was coreing in the same spot each time. (I don't have an overclocked CPU.) Thanks to those who responded. - Matt >>> "Matt White" 09/18/99 08:32PM >>> I was upgrading from 3.2, as of a few weeks ago. I try to build the world = every few weeks. I blew away /usr/src, and I'm in the middle of supping a whole new copy. = I'll keep the list posted if this works. But yes, this box was a 2.2.5 box that's been upgraded all along. (2.2.5 = -> 2.2.6 -> 2.2.7 -> 3.0 -> 3.1 -> 3.2) - Matt >>> Bryan Talbot 09/18/99 07:02PM >>> Ok, I'll give it a shot. Since neither one of you state what version = of=20 FreeBSD you were running when trying to make the world, I'll assume = it's=20 NOT 3.x. If this is the case then you really need to read the=20 /usr/src/Makefile and look at that nifty "upgrade" target. If you are using 3.x now, I don't know what the problem is ... I = upgraded=20 from 3.2-stable to 3.3-stable last night without a hitch and I know = many=20 others have too. At 03:30 PM 9/18/99 , Will Andrews wrote: >On 18-Sep-99 Matt White wrote: > > cc -static -O -pipe -I. > > -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc - > > I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config=20 > -DFREEBSD_NATIVE > > -D > > DEFAULT_TARGET_VERSION=3D\"2.7.2.3\" > > -DDEFAULT_TARGET_MACHINE=3D\"i386-unknown-freeb > > sd\" -I/usr/obj/src/gnu/usr.bin/cc/cc_tools/../cc_tools > > -I/usr/obj/src/tmp/usr > > /include -static -o bi-arity bi-arity.o bi-parser.o bi-lexer.o=20 > bi-reverse.o > > ./bi-arity < > > /src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/bytecode.def > > > bc-arity.h > > syntax error in input > > *** Error code 33 > > > > Stop. > > *** Error code 1 > >Yes, I get the same problem, but normally I just edit the appropriate = Makefile >to bypass cc_tools, cc1, cc1-obj, and other programs. Unfortunately, no = one >replied when I first reported this problem, so I just went and did that. = I >suspect that now my cc1/cc1-obj/etc. are hopelessly out-of-sync, even = though >they continue to function. > >My suspicion is that somehow, somewhere, cc got borked and i no longer = can >properly compile the bc-arity stuff.. not that I have a clue what it's = for, of >course. Could somebody look into this? (Please.) > >Thanks. > >-- >Will Andrews >GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- >?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ >G++>+++ e->++++ h! r-->+++ y? > > >To Unsubscribe: send mail to majordomo@FreeBSD.org=20 >with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org=20 with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org=20 with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message