> > Wesley J Landaker wrote on Sat, Jun 22, 2002 at 04:27:41PM -0600 : > > > > I ran into this same issue on my laptop, which is a i586 -- after > > updating to the latest glibc, I got all sorts of illegal instruction > > errors as above. (A monsterous pain to clean up, I might add, since > > things like "cp" and "ls" aren't statically linked, so won't help in > > fixing glibc problems.) >
After giving it some more thought I consider it to be highly dangerous "feature" that must NEVER BE DONE AUTOMATICALLY. Linking your default libraries to any specific process type makes it impossible to (ex-)change CPU as part of system changeover or to restore backup on different system. What os worse, because use has no idea what happens (s)he has no idea how to fix it. The only case when such CPU-specific library tuning can be done automatically is when you recheck it on every startup ... but here you are trapped. It must be done very early before anything else runs ... but at this point root is usually read-only yet ... -andrej
