Date: Thu, 22 Apr 2021 19:20:50 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Peter Blok <pblok@bsd4all.org>, freebsd-hackers@freebsd.org Subject: Re: cross building i386 on amd64 Message-ID: <31999507-b590-edcc-a4ff-b0a18105bcfd@grosbein.net> In-Reply-To: <376DADB2-A7A9-4519-888C-BCD8A32B62B3@bsd4all.org> References: <376DADB2-A7A9-4519-888C-BCD8A32B62B3@bsd4all.org>
next in thread | previous in thread | raw e-mail | index | archive | help
17.04.2021 0:22, Peter Blok wrote: > Hi, > > I’m cross building 12-STABLE i386 on a 12-STABLE amd64 system. Sources are refreshed every day. > > Build runs fine and put everything in the right directory. For the target i386 system it is in /usr/obj/i386TARGET. > > Next I NFS mount the source /on /usr/src and /usr/obj/i386TARGET on /usr/obj on the target machine > > When I run make installworld it will use install from /usr/obj/usr/src/i386.i386/tmp/legacy/usr/bin because it is the first install it finds in the PATH set by installworld. This tanks because install is compiled for amd64. > > I understand why the legacy path is compiled for amd64. This is needed to build a distribution. > > So is this is bug or is the way I distribute the objects not supported? It was never supported. But, you will be fine doing it othe way: running "make installworld" using same system you used to run "make buildworld". NFS-export i386 system to build host and run both build and install there.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?31999507-b590-edcc-a4ff-b0a18105bcfd>