From owner-freebsd-current Mon Dec 2 1: 4:33 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D482237B401 for ; Mon, 2 Dec 2002 01:04:31 -0800 (PST) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00B7B43EB2 for ; Mon, 2 Dec 2002 01:04:22 -0800 (PST) (envelope-from ru@whale.sunbay.crimea.ua) Received: from whale.sunbay.crimea.ua (ru@localhost [127.0.0.1]) by whale.sunbay.crimea.ua (8.12.6/8.12.6/Sunbay) with ESMTP id gB293htV088374 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 2 Dec 2002 11:03:43 +0200 (EET) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.12.6/8.12.6/Submit) id gB293hwr088369; Mon, 2 Dec 2002 11:03:43 +0200 (EET) Date: Mon, 2 Dec 2002 11:03:43 +0200 From: Ruslan Ermilov To: "M. Warner Losh" Cc: current@FreeBSD.org Subject: Re: [REPORT] Upgrade from 4.0-RELEASE to 5.0-CURRENT Message-ID: <20021202090343.GB86324@sunbay.com> References: <3DEA2774.DCE1CACD@newsguy.com> <20021201.111129.35672010.imp@bsdimp.com> <20021202081715.GA83484@sunbay.com> <20021202.014458.85416045.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BwCQnh7xodEAoBMC" Content-Disposition: inline In-Reply-To: <20021202.014458.85416045.imp@bsdimp.com> User-Agent: Mutt/1.5.1i 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 --BwCQnh7xodEAoBMC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 02, 2002 at 01:44:58AM -0700, M. Warner Losh wrote: > In message: <20021202081715.GA83484@sunbay.com> > Ruslan Ermilov writes: > : Um, why? I can even cross-build any of our supported arches on the > : 4.0-RELEASE i386 box. This happens almost automatically, as part > : of the cross-arch work tasks. >=20 > I think that there are some build tools that need a complete copy of > the byte swapping macros, just so that cross building a sparc64 > platform would work. It seems to me, and a bunch of others, that > jumping through a lot of hoops to allow cross building of sparc64 on > intel on 4.0-release isn't that interesting. imho. >=20 For the cross-release, yes, the work isn't yet finished (when creating floppies that, last time I checked, didn't even work on sparc64, we need to byteswap the filesystem images -- there is a utility floating around, bswapfs(8), that could be used to do just this, but it was limited to FFS1 (again, last time I checked). Another cross-tool that was needed for this to work was crunchide(1): : revision 1.263 of Makefile.inc1 : date: 2002/04/30 09:34:53; author: ru; state: Exp; lines: +2 -1 : Make crunchide(1) a cross-tool; needed for cross-arch "make release". : Note that a.out is only supported for the non-cross i386 case. For the "regular" cross-build the only tool that needed tweaking was elf2aout(1): : revision 1.282 of Makefile.inc1 : date: 2002/05/20 14:42:48; author: ru; state: Exp; lines: +5 -1 : Bootstrap elf2aout(1) for sparc64; used to build sys/boot/sparc64/boot1. (Of course, both crunchide(1) and elf2aout(1) were "fixed" to support different endianness host/target machines, for this to work.) Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --BwCQnh7xodEAoBMC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE96yHvUkv4P6juNwoRAjlHAJ4pWfOSHRC+hFzZpUlIV2bB+830zwCfe6HH wgkuQgXiHgCrMF5wg2coTUE= =2x88 -----END PGP SIGNATURE----- --BwCQnh7xodEAoBMC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message