Daniel Schepler dixit: >-mx32), and then run file on the test program. If file outputs
No, file(1) is an added dependency, unreliable (can have false positives and negatives) and known to change output from time to time. >Or, less reliably, you could look at the configure triplet, which is >x86_64*linux-gnux32 for x32 builds, and x86_64*linux-gnu for amd64 >builds. $CC -dumpmachine – but only if $CC is a GCC… I believe my simple compile-time test is the best option. bye, //mirabilos -- 13:37⎜«Natureshadow» Deep inside, I hate mirabilos. I mean, he's a good guy. But he's always right! In every fsckin' situation, he's right. Even with his deeply perverted taste in software and borked ambition towards broken OSes - in the end, he's damn right about it :(! […] works in mksh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
