On Monday, 14 December 2020 12:55:33 GMT n952162 wrote: > On 12/14/20 11:17 AM, Wols Lists wrote: > > On 14/12/20 08:51, Dale wrote: > >> If you are able, maybe you can compile the bigger packages on a faster > >> system? If it is a option, it may help. > > > > If I have multiple similar machines, I create a shared a shared local > > repository. Then I run emerge with the settings (can't remember what > > they are) "use binary if it's there, create binary". > > > > That way, especially the big ones, only get built on one machine. > > > > Cheers, > > Wol > > Oh man! That would be wonderful. How similar do they need to be? All > my x86 machines are currently AMD, I think, but probably from different > generations.
It depends on the different instruction sets between the CPUs. You could try compiling one package as a test with the existing $COMMON_FLAGS on the fast host and emerge '--buildpkg y', or '--buildpkgonly', then emerge it as a binary on the slow host with '--usepkgonly y'. If the binary package does not emerge/run on the slow host, then you can try again, but use COMMON_FLAGS="-march" instead of "-march=native" to compile it on the fast host. The same binary package could then be installed on all slow hosts.
signature.asc
Description: This is a digitally signed message part.
