Hi, Gabriel Paubert wrote:
Anyway, I think the best of two worlds would be to use getauxval() >when available (most probably any currently supported OS) and fall >back to cpuinfo if not. A configure test I suppose is quite simple.You don't always configure/compile on the machine you run. Especially the people who build distributions.
Wait, sure you have host and target. But you do need to have the library versions you run on - that's how I know cross-compilation. So if you can't check the CPU type you will run on at compile time (trivial, just an example), but you do know if you are compiling against a certain library version. So at buld time you do know if getauxval() will be available or not. Otherwise any program which uses autotools would not be compilabel on a different machine, or am I missing a point?
Riccardo