From owner-freebsd-arch Sat Oct 16 4:13:28 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 73DE414E82 for ; Sat, 16 Oct 1999 04:13:25 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id NAA21379 for ; Sat, 16 Oct 1999 13:13:09 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id NAA57125 for freebsd-arch@freebsd.org; Sat, 16 Oct 1999 13:13:08 +0200 (MET DST) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id D23CE14E82 for ; Sat, 16 Oct 1999 04:12:31 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.3/8.9.1) id VAA81111; Sat, 16 Oct 1999 21:14:49 +1000 (EST) (envelope-from jb) Date: Sat, 16 Oct 1999 21:14:49 +1000 From: John Birrell To: Marcel Moolenaar Cc: arch@freebsd.org Subject: Re: make world issues Message-ID: <19991016211449.H67481@freebsd1.cimlogic.com.au> References: <380716A4.20961526@scc.nl>, <19991016074606.C67481@freebsd1.cimlogic.com.au> <38085861.1A16B95C@scc.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <38085861.1A16B95C@scc.nl>; from Marcel Moolenaar on Sat, Oct 16, 1999 at 12:50:09PM +0200 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 16, 1999 at 12:50:09PM +0200, Marcel Moolenaar wrote: > John Birrell wrote: > > > > I don't think that cross-compilation helps solve the bootstrap/upgrade > > problem caused by the signal changes. > > I think it does. Please explain to me why you think cross-compilation > doesn't solve bootstrapping/upgrading. Because when cross-compiling, you don't execute anything that you build for the target system. By contrast, for the host build, you need to update things in bootstrap order and then progessively execute the updated things in order to complete the build. If you make a change (like the signal changes) that isn't backward compatible, then you can't bootstrap properly because you can't execute what you build. You shouldn't blame the build process for it's inability to handle the lack of backward compatibility in your code. We shouldn't allow changes to libc that won't work with older kernels. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ john.birrell@opendirectory.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message