On Tue, Sep 5, 2017 at 10:43 PM, Grant wrote:
>> Now I'm running into "trap invalid opcode" errors on the older
>> systems. Can I disable some of the newer CPU instruction sets on the
>> master laptop when compiling to hopefully generate binaries that will
>> work on the older sys
> Now I'm running into "trap invalid opcode" errors on the older
> systems. Can I disable some of the newer CPU instruction sets on the
> master laptop when compiling to hopefully generate binaries that will
> work on the older systems?
Yes. You need to find out CPU_FL
On Tue, Sep 5, 2017 at 10:28 PM, Grant wrote:
Now I'm running into "trap invalid opcode" errors on the older
systems. Can I disable some of the newer CPU instruction sets on the
master laptop when compiling to hopefully generate binaries that will
work on the older systems?
>>
>>> Now I'm running into "trap invalid opcode" errors on the older
>>> systems. Can I disable some of the newer CPU instruction sets on the
>>> master laptop when compiling to hopefully generate binaries that will
>>> work on the older systems?
>>
>> Yes. You need to find out CPU_FLAGS_X86 and
>> Now I'm running into "trap invalid opcode" errors on the older
>> systems. Can I disable some of the newer CPU instruction sets on the
>> master laptop when compiling to hopefully generate binaries that will
>> work on the older systems?
>
> Yes. You need to find out CPU_FLAGS_X86 and "-marc
On Mon, Sep 04, 2017 at 12:39:02PM -0700, Grant wrote
>
> Now I'm running into "trap invalid opcode" errors on the older
> systems. Can I disable some of the newer CPU instruction sets on the
> master laptop when compiling to hopefully generate binaries that will
> work on the older systems?
Y
I have a network of very nearly identical Dell XPS 13 laptops that I
manage with a script. The master pushes the contents of its
filesystem to the others so I only have to manage one system. It's
worked really well over several years. I just got a new Dell XPS 13
to serve as the master and there
7 matches
Mail list logo