Date: Sun, 20 Nov 2005 10:14:37 +0100 From: =?ISO-8859-1?Q?Eirik_=D8verby?= <ltning@anduin.net> To: =?ISO-8859-1?Q?Eirik_=D8verby?= <ltning@anduin.net> Cc: Brandon Fosdick <bfoz@bfoz.net>, stable@freebsd.org, Joseph Koshy <joseph.koshy@gmail.com> Subject: Re: Centralized building Message-ID: <F624F829-AC1F-4049-96E2-A9F8D39103A8@anduin.net> In-Reply-To: <B4BD74C1-61EF-4F55-B6F1-3CADA6352E10@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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 20, 2005, at 09:50 , Eirik =D8verby wrote: > > 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). 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... Anyone?? /Eirik > > > >> >> -- >> FreeBSD Volunteer, http://people.freebsd.org/~jkoshy >> >> > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-=20 > unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F624F829-AC1F-4049-96E2-A9F8D39103A8>