Date: Sun, 20 Nov 2005 22:21:30 +0200 From: Ruslan Ermilov <ru@FreeBSD.org> To: Eirik ?verby <ltning@anduin.net> Cc: Brandon Fosdick <bfoz@bfoz.net>, stable@FreeBSD.org, Joseph Koshy <joseph.koshy@gmail.com> Subject: Re: Centralized building Message-ID: <20051120202130.GH20188@ip.net.ua> In-Reply-To: <F624F829-AC1F-4049-96E2-A9F8D39103A8@anduin.net> References: <EAD12EE3-2CB4-40D4-90AC-B2337455036C@anduin.net> <437F6E41.2040504@bfoz.net> <84dead720511191043u26808efcn54987c99407500e0@mail.gmail.com> <B4BD74C1-61EF-4F55-B6F1-3CADA6352E10@anduin.net> <F624F829-AC1F-4049-96E2-A9F8D39103A8@anduin.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--gTtJ75FAzB1T2CN6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 20, 2005 at 10:14:37AM +0100, Eirik ?verby wrote: >=20 > On Nov 20, 2005, at 09:50 , Eirik ?verby wrote: >=20 > > > >On Nov 19, 2005, at 19:43 , Joseph Koshy wrote: > > > >>>AFAICT cross-compiling amd64 on a i386 machine isn't supported > >>>yet. I ran into a similar problem when I upgraded an i386 > >>>machine to amd64. I thought I could just set CPUTYPE=3Dathlon-64 > >>>and buildworld would do the right thing. Apparently not. > >> > >>Bootstrapping a single machine is supported: > >> > >># make buildworld TARGET_ARCH=3Dnew-arch > >> > >>plus a few other steps. (See build(7)). > >> > >>There have been a couple of postings on the mailing lists > >>on this topic in the recent past. I've taken a stab at > >>describing how to cross-bootstrap too: > >> > >>http://edoofus.blogspot.com/2005/10/cross-building-freebsd.html > >> > >>The OP wanted to do a 'buildworld TARGET_ARCH=3Dfoo' on one > >>machine and then an 'installworld' on a different set of > >>machines. > > > >Yes, and he still wonders if this is supposed to be doable or not. > >I think the culprit is (partly) the fact that every architecture is =20 > >built into its own subdirectory in /usr/obj, EXCEPT the =20 > >architecture the build is running on. The same goes for the install =20 > >part, and if the build and install architectures differ, it cannot =20 > >ever work. Setting MAKEOBJDIRPREFIX on the target host makes the =20 > >install start, but it fails after a couple of minutes with the "dd: =20 > >not found" error. > >(I do notice that there is a /usr/obj/usr directory created also =20 > >when cross-building; I'm assuming this contains the build bootstrap =20 > >tools). >=20 > Follow-up. If I enter src/sys and do a "make install", the dd step =20 > works perfectly - however it stops later when trying to install =20 > cdboot. I am assuming this is due to missing options or wrong target =20 > for make, but - from all I can tell - shows a weakness in the build/=20 > install system. Or maybe not... >=20 > Anyone?? >=20 We don't support build host !=3D install host, in a strict sense. But as Joseph pointed out, we do support NFS installs to different architectures. The build host !=3D install host is supported only if a number of conditions are met, most noticeable are that they should be running the same OS version and the same (or compatible) CPU, and of course the same set of options (/etc/make.conf, etc.) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --gTtJ75FAzB1T2CN6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDgNrKqRfpzJluFF4RAibyAKCLPZSjDxunYJTdGanprbh/Rig+uQCeKEu+ mgGDRJIA+g6emjWM5VerPgo= =KA3v -----END PGP SIGNATURE----- --gTtJ75FAzB1T2CN6--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051120202130.GH20188>