Date: Tue, 7 Nov 2000 22:31:25 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Marcel Moolenaar <marcel@cup.hp.com> Cc: arch@FreeBSD.ORG Subject: Re: source upgrading: bootstrap library Message-ID: <Pine.BSF.4.21.0011072223001.3041-100000@besplex.bde.org> In-Reply-To: <3A05DA28.DE3EE486@cup.hp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0011072223001.3041-100000>