From owner-freebsd-current Thu Nov 21 6:29: 9 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 4446F37B401 for ; Thu, 21 Nov 2002 06:29:06 -0800 (PST) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A9B043E3B for ; Thu, 21 Nov 2002 06:29:00 -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 gALESRbS016980 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 21 Nov 2002 16:28:27 +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 gALESQ9g016970; Thu, 21 Nov 2002 16:28:26 +0200 (EET) Date: Thu, 21 Nov 2002 16:28:26 +0200 From: Ruslan Ermilov To: "M. Warner Losh" Cc: current@FreeBSD.org Subject: Re: Cross-Development with NetBSD Message-ID: <20021121142826.GA12467@sunbay.com> References: <20021121151714.U961-100000@squirm.dsto.defence.gov.au> <20021121.001014.56348240.imp@bsdimp.com> <20021121102050.GC81999@sunbay.com> <20021121.062809.64538355.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline In-Reply-To: <20021121.062809.64538355.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 --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 21, 2002 at 06:28:09AM -0700, M. Warner Losh wrote: > In message: <20021121102050.GC81999@sunbay.com> > Ruslan Ermilov writes: > : On Thu, Nov 21, 2002 at 12:10:14AM -0700, M. Warner Losh wrote: > : > In message: <20021121151714.U961-100000@squirm.dsto.defence.gov.au> > : > "Wilkinson,Alex" wri= tes: > : > : Is FreeBSD likely to follow the in footsteps of NetBSD and create a= framework to do crossbuilds ? > : > :=20 > : > : http://ezine.daemonnews.org/200211/xdevnetbsd.html > : >=20 > : > FreeBSD already has cross builds for a while, since before NetBSD's > : > cross build infrastructure. However, NetBSD's infrastructure is a > : > little more extensive because it is possible to do incremental builds > : > and build full releases that work in a cross build evironment. > : >=20 > : What do you mean by "incremental builds and full releases that work ...= "? >=20 > ruslan, >=20 > First and foremost, I ment no disrespect in what I said. You > have made the upgrade path for FreeBSD almost painless for a wide > range of releases (less painful than NetBSD has been at times for me). > You gave FreeBSD the ability to cross build world about a year or a > year and a half ahead of NetBSD's similarly integrated ability. >=20 Sorry if I sounded so, I didn't mean to. :-) > NetBSD builds a directory full of tools that you can later use to > incrementally build, say, 'ls' or 'cat' because one can define > USETOOLS to be 'yes' and have the make automatically pick them up when > rebuilding. There are a few of the details I'm a little unclear on, > but that's the jist of it. >=20 We also can, this just requires a few really tiny tweaks to Makefile.inc1, and I've posted them already some time ago -- basically, for each architect= ure you should build the subset of buildworld targets (WMAKE_TGTS), up to and including _libraries (if you want to build roughly any bit later), and them you can ``make {depend|all} SUBDIR_OVERRIDE=3Dbin/cat'' for each of the desired TARGET_ARCH. > Second, the NetBSD have tested almost all of their platforms in a > cross build release scenario. They know that the binaries that result > from 'make release' build on i386 actually boot on the target > platform. They have build 1.6.x for many of their platforms this > way. So far, the FreeBSD has done all its builds natively. >=20 I know that the Alpha and sparc64 binaries produced on i386 work. I know that cross-compiling i386 on either Alpha or sparc64 is broken (GCC sometimes produces different assembler output than the native compiler). I lack the necessary hardware to actually test/fix the issues with cross-releases. > One of the cool things about the NetBSD approach, btw, is that they > have a src/tools directory. This directory lists all the build tools > for building in one place. I think that this is a little cleaner than > what we have in the Makefile.inc1 right now. On the other hand, it is > a lot more complicated than what we have now, and I'm not sure that > added complexity is worth it. >=20 When you say "build tools", do you mean them in our build-tools sense, or something else? 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 --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE93O2KUkv4P6juNwoRAgCpAJwJJHnstk4HR5crEWOnXIatoSbNBACfR8oU 3DwR9CBnwRK7u4Bqg348t8I= =czxZ -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message