Re: buildworld on CPU-A, installworld on CPU-B ends up with SIGILL

From: Miroslav Lachman <>
Date: Mon, 25 Nov 2019 20:09:53 +0100
Ruslan Garipov wrote on 2019/11/25 19:26:


>> I didn't tried this with current but I am using it with stable (11.3 at
>> this time). Building on Xeon E3-1240v3 and installing on many different
>> machines. Some of them are 10+ years old AMD Opteron, some Xeon E5649,
>> some 10 years old Intel Pentium.
>> So at least it worked in the past (11.3 amd64). Did you use this
>> workflow in the past / did it work?
> No, unfortunately I didn't.  Always built world/kernel on target host.
>> I remember some issue in the past which was (accidentally?) fixed by
>> running "make buildworld && make builkernel && make installkernel &&
>> make installworld" on the build host (to some different DESTDIR) and
>> then "make installkernel && make installworld" on the target host (build
>> machine is shared via NFS)
> Therefore, this trick somehow "fixes" /usr/obj shared on the build
> machine?  I'll try this later.  Thanks!

Yes, I think so. But I am not a developer nor I know much about how 
build process works.

Miroslav Lachman
Received on Mon Nov 25 2019 - 18:09:57 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:22 UTC