Back before the 7.0 Release I used to install cross builds by NFS-mounting /usr/src and /usr/obj of the build machine on the target machine and running: # cd /usr/src # env MAKEOBJDIRPREFIX=/usr/obj/<stuff> make installkernel KERNCONF=<kernconf> ... This doesn't work any more because all the installation tools are built for the architecture of the build system. The alternative to mount the whole fstab structure of the target machine into the build server and installing with DESTDIR works, but feels pretty clumsy in comparison. Is there any way to change that behaviour (most of the stuff that ends up having the wrong architecture is in tmp/legacy, but there's more).
On 2009-Apr-25 17:51:49 +0200, Dominic Fandrey <kamikaze@bsdforen.de> wrote:>Back before the 7.0 Release I used to install cross builds by >NFS-mounting /usr/src and /usr/obj of the build machine on the >target machine and running: > ># cd /usr/src ># env MAKEOBJDIRPREFIX=/usr/obj/<stuff> make installkernel KERNCONF=<kernconf> >...This has only ever worked if the target machine architecture was a superset of the build machine architecture.>This doesn't work any more because all the installation tools >are built for the architecture of the build system.buildworld has always built the build/install infrastucture to suit the build machine architecture.>The alternative to mount the whole fstab structure of the >target machine into the build server and installing with DESTDIR >works, but feels pretty clumsy in comparison.This is the supported way to install onto a different architecture target. -- Peter Jeremy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090428/9ac1b372/attachment.pgp