Hi there, Unfortunately this still did not help.
I repeat my original question: Q: The binary (e.g. /usr/bin/bzip2) obviously "knows" what it requires. How do I find out what this is? Neither ldd, ld.so or the like seem to give me this information. BR Alex On Sonntag, 3. März 2024, 18:45:16 CET Alexander Puchmayr wrote: > Am Sonntag, 3. März 2024, 14:32:41 CET schrieb Andreas K. Huettel: > > > I set CFLAGS="-O2 -pipe march=x86-64-v2" on the buildhost and performed > > > a > > > emerge -ev @world, re-creating all packages in binary form. > > > > > > My expectation was that these packages would work on the target > > > platform, > > > but they don't. Error message "CPU ISA level is lower than required". > > > > Quiz question: did you rebuild your toolchain *before* or *after* bzip2? > > > > Suspicion without proof, the startup code embedded by gcc and glibc may > > well be affected by the microarchitecture level. As may be libraries > > statically linked in... > > > > The safer way would be to run emerge -ev world, and afterwards build the > > packages with a second emerge -ev world ... > > Indeed, that seems to be the problem. I remember, my first try was with -v3 > (as my buildhost supported this), and, after discovering the "surprise" on > the target machine, started the emerge -ev @world. Likely, glibc was not > the first package, so there are an unknown number of packets that have the > problem. > > I started to recompile the "usual suspects", like bzip2 and xz, which made > it a bit better, but still the emerge -uavDNk @world did not succeed. > > Now I'm doing again a emerge -ev @world on my buildhost again, so tomorrow > it should be solved. > > Thanks for the hint > Alex
