From owner-freebsd-current Fri Aug 10 11:54:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id A2B8537B405; Fri, 10 Aug 2001 11:54:27 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id LAA07696; Fri, 10 Aug 2001 11:54:25 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010810202300.A80439@sunbay.com> Date: Fri, 10 Aug 2001 11:54:27 -0700 (PDT) From: John Baldwin To: Ruslan Ermilov Subject: Re: Cross builds and upgrade path from 4.x are broken in usr.bin Cc: current@FreeBSD.org, Warner Losh , Bruce Evans , Mark Peek Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 10-Aug-01 Ruslan Ermilov wrote: > On Fri, Aug 10, 2001 at 10:04:01AM -0700, Mark Peek wrote: >> At 7:14 PM +0300 8/10/01, Ruslan Ermilov wrote: >> >On Fri, Aug 10, 2001 at 08:38:21AM -0700, Mark Peek wrote: >> > > At 5:37 PM +0300 8/10/01, Ruslan Ermilov wrote: >> > > I'm not sure I understand what you mean by "cross-platform" >> >> installworld. Do you mean "build on a HOST platform and install on >> >> TARGET", or "build on a HOST, install on HOST but using a TARGET >> >> disk"? >> >> >> >I meant the latter here. >> >> Has this ever worked? >> Is it really a goal of the project to have it work? >> > Yes. Imagine that you are rolling an Alpha release on an i386 box. You don't do that. Cross releases need much more work before that is feasible. As Mark mentions, there are many thigns that would need to be fixed. Also, the release process would be hacked, and you still wouldn't have a true "clean room" release since you can't build a "clean room" to run a fresh world in. >> Your solution does not work. You're creating binary files in HOST >> format during the build phase and expecting things such as alignment >> and endianness to be the same as the TARGET format. Unless the tools >> are built to output for either the appropriate architecture or in a >> portable, binary format, you will have problems reading the file on >> the TARGET platform. It probably works for you since you're doing a >> 4.X->5.0 upgrade on the same platform. >> > What? ``file -C'' produces different output on Alpha and on i386? > Are you sure? (Haven't checked myself.) sparc64 is big endian. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message