It means the compiler for -m686 shouldn't have assumed cmov was available
> > So you have a buggy rpm program. Get the rpm program fixed so it correctly
> > stops you from doing that.
> Maybe, ok. But why should such a mistake prevent me from workin with the
> system when it could be easily catched? Ok, the emulation code may not
It can be easily caught. Thats what rpm is for. If it let you install that
package on a box that can run it without using --force type options its
> be easy, I dunno, but the infrastructure for emulation of instructions
> is already there (FPU emulation). To say its the admins fault is easy
FPU emulation should probably have been in glibc via a fault handler
but thats a historical story.
> but the costs of automatically catching such errors are little in
> respect of the benefit you get. A running system is always better than
> a unusable one even if it was the admins fault.
Then while you are it you can make the kernel magically recover from rm -rf /
or rm * in /lib...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/