From owner-freebsd-current Mon Mar 1 14:11: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 12F9314EA2 for ; Mon, 1 Mar 1999 14:10:59 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA24321; Mon, 1 Mar 1999 14:10:38 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id OAA49598; Mon, 1 Mar 1999 14:10:37 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903012157.QAA24740@y.dyson.net> Date: Mon, 01 Mar 1999 14:10:37 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: "John S. Dyson" Subject: Re: gcc Cc: current@FreeBSD.ORG, obrien@NUXI.com, (Jordan K. Hubbard) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John S. Dyson wrote: > Jordan K. Hubbard said: >> > I can generally build a kernel with EGCS, if I change how the .text and >> > .data are laid out for initialized data. It seems that the initialization >> > code makes assumptions about the order or layout of the initialization >> > data. Once the stuff is made to act more like the version of GCC that >> > FreeBSD uses, the kernel will most often build and work. >> >> It really does appear to be a simple matter of first making egcs "take over" >> the system compiler: >> > Okay, I guess I have been missing something :-). Keep in mind that a whole bunch of stuff connected with kernel initialization has been changed lately. It may be simply that you're dealing with an older vintage kernel. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message