On Mon, Sep 8, 2014 at 2:52 PM, Thorsten Glaser <t...@mirbsd.de> wrote: > 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.
OK... though if file changes its output significantly from this, it's likely to break libtool. Actually, I guess libtool does: check the output of file first for "32-bit" or "64-bit", then in the 32-bit case check additionally for "x86-64" to determine whether to use -m elf32_x86_64 or -m elf_i386. >>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... Doesn't seem to work if $CC is "gcc -mx32" on an amd64 machine. > I believe my simple compile-time test is the best option. Probably so. -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
