I use the binpkg feature to quickly update an Athlon64 system with
packages compiled on an Athlon64 X2 system. march=athlon64 on both
systems, I avoided using the new gcc 4.3.2 march=native option to
maintain compatibility. The Athlon64 apparently runs fine, but yesterday
I discovered that mplayer aborts with 'illegal instruction', spitting
out a warning that possibly the package was compiled for a different
machine, which is true!

Anybody has ideas why it is happening? On last update I switched from
gcc-4.2.1 to gcc-4.3.2, but since the system seemed stable and running
fine till now I did not do the recommended emerge -e world. Maybe some
mplayer dependency is still referencing the old gcc libraries?

raffaele

Reply via email to