From owner-freebsd-arch Tue Nov 7 3:41:19 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id C575537B4CF for ; Tue, 7 Nov 2000 03:41:15 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id WAA01397; Tue, 7 Nov 2000 22:31:15 +1100 Date: Tue, 7 Nov 2000 22:31:25 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Marcel Moolenaar Cc: arch@FreeBSD.ORG Subject: Re: source upgrading: bootstrap library In-Reply-To: <3A05DA28.DE3EE486@cup.hp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Nov 2000, Marcel Moolenaar wrote: > There are multiple ways to solve (avoid) this. One way is is handling > each case seperately, as is currently done for gcc. We build a FreeBSD > specific library for gcc that contains functions we need to be backward > compatible (see /usr/src/gnu/usr.bin/cc/cc_fbsd). We have a similar > problem with libiberty and just recently with perl. > > Another approach is to build a bootstrap library as part of the > bootstrap phase and have it contain any and all functions or > compatibility shims we need to be able to upgrade. All bootstrap, build > and cross- tools are to be linked against this library (in such a way > that existing functions are used). > > I tend to favor the latter and plan to implement it. Let me know if you > have any objections, alternatives, additions or questions. I think I prefer to handle each case separately, at least at first. There is also a problem with header files. E.g., the current mtree can't be compiled under FreeBSD-2.1.5, because the members of struct timespec were didn't have the braindamaged standard spelling in 2.1.5. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message