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

2019-11-26 Thread Ruslan Garipov
On 11/26/2019 12:09 AM, Miroslav Lachman wrote: > 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

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

2019-11-25 Thread Miroslav Lachman
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.

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

2019-11-25 Thread Ruslan Garipov
On 11/25/2019 10:30 PM, Miroslav Lachman wrote: > Ruslan Garipov wrote on 2019/11/25 15:06: >> Hello. >> >> I want to build kernel and world (of FreeBSD 13.0-CURRENT) on a fast >> virtual machine for other ones (all the virtual machines are hosted on >> VMware EXSi hypervisors, which have different

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

2019-11-25 Thread Miroslav Lachman
Ruslan Garipov wrote on 2019/11/25 15:06: Hello. I want to build kernel and world (of FreeBSD 13.0-CURRENT) on a fast virtual machine for other ones (all the virtual machines are hosted on VMware EXSi hypervisors, which have different physical CPUs). After `make -j16 buildworld` has finished su

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

2019-11-25 Thread Ruslan Garipov
Hello. I want to build kernel and world (of FreeBSD 13.0-CURRENT) on a fast virtual machine for other ones (all the virtual machines are hosted on VMware EXSi hypervisors, which have different physical CPUs). After `make -j16 buildworld` has finished successfully on the build machine, I get there