From owner-freebsd-stable Sat Feb 6 04:47:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA07495 for freebsd-stable-outgoing; Sat, 6 Feb 1999 04:47:05 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from neptune.psn.net (neptune.psn.net [207.211.58.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA07487 for ; Sat, 6 Feb 1999 04:47:04 -0800 (PST) (envelope-from chemtechweb@psn.net) Received: from 1-41.phx.psn.net ([209.63.50.169] helo=psn.net) by neptune.psn.net with esmtp (PSN Internet Service 2.10 #1) for freebsd-stable@freebsd.org id 10978Z-0000X1-00; Sat, 6 Feb 1999 05:47:03 -0700 Message-ID: <36BC3A20.8ADA79AF@psn.net> Date: Sat, 06 Feb 1999 05:48:32 -0700 From: Emmanuel Gravel Reply-To: chemtechweb@psn.net Organization: Orbit Communications X-Mailer: Mozilla 4.08 [en] (Win98; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: make world fail after cvsup Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just tried to upgrade from 2.2.7 release (from CD's) to 3.0 stable by cvsupping the whole source tree. I had to restart cvsup multiple times because of connection failures, but I don't know if this had anything to do with my problem (first cvsup for me). Once I had completed the download (message of success by cvsup) I cd /usr/src and make world. Messages went by really fast (I have a PII 450 with 128 MB ram) but I know I saw many messages of "file not found". But that's not the major problem. Here's the final error message when rebuilding the bootstrap binaries: /usr/src/lib/csu/1386-elf/crtbegin.c:30 attributes not supported for this target /usr/src/lib/csu/1386-elf/crtbegin.c:31 attributes not supported for this target then it gives a few assembler messages and error 1 stop. Full output from make available on demand, but it's much too big to be included here. Mind you, I'm writing this message from a Win98 machine (I don't dare halt the FreeBSD machine until the problem is solved). Anyone have any hints to what could have gone wrong? Better yet, how to fix this? Thanks, Manu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message