cross building i386 on amd64

Peter Blok pblok at bsd4all.org
Thu Apr 22 18:15:13 UTC 2021



> On 22 Apr 2021, at 14:20, Eugene Grosbein <eugen at grosbein.net> wrote:
> 
> 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.
I wasn’t sure if any non NFS supported functionality was needed like chflags.

Peter
> 
> 
> _______________________________________________
> freebsd-hackers at freebsd.org <mailto:freebsd-hackers at freebsd.org> mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org <mailto:freebsd-hackers-unsubscribe at freebsd.org>"



More information about the freebsd-hackers mailing list