Re: [gentoo-user] Re: Lowest common denominator compile

[Alan McKinnon <alan.mckinnon@gmail.com>]

On 04/09/2017 22:16, Grant wrote:
>> 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 have been some changes that were
>> difficult to integrate with the network (high-res screen, /dev/sda
>> replaced with /dev/nvme0n0) but those problems are fixed thanks to you
>> guys.
>>
>> 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?  If so, could anyone point me in the right
>> direction?  I don't want to use distcc please.
>>
>> CHOST="x86_64-pc-linux-gnu"
>> CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer"
> 
> 
> Switching to -mtune=native seems to work.  Time for an emerge -e world.

Also time for ansible. Why you managing a fleet of machines with a
script that won't actually differentiate properly between machines? It
will sorts mostly do it right, except when you forget something.

This is exactly the use-case ansible was designed for: declarative,
idempotent, predictable management of a fleet of machines that may or
may not be around when you feel like updating something (so it catches
up later), and needs only sshd and python to do it's magic :-)

Never mind that ansible was written with servers in mind; in terms of
management where you do $STUFF_THAT_NEEDS_MANAGING, there is no
difference between servers and laptops. A computer is still just a computer.

</me also laments the lack of poudriere on Gentoo. But that's for
another time>

-- 
Alan McKinnon
alan.mckinnon@gmail.com