It seems to be autotools doing that. It checks that the compiler can at least compile a binary (it worked fine on your machine with the -march=nocona flag). Also the assembler can produce code on any platform, so that is all it checks.
It should either pass -m64 to the compiler when checking ABI=64 (which I assume would fail on your system) or it should do more stringent tests on the OS to check it really is 64 bit. I'm not sure why it doesn't do that. Bill. On 12 July 2010 21:05, Tomasz Melcer <[email protected]> wrote: > On 11 Lip, 20:17, Bill Hart <[email protected]> wrote: >> It detects that your processor is an i7, which is 64 bit, thus it >> tries to build a 64 bit binary. >> >> If you want to force it to build a 32 bit binary, you have to pass >> ABI=32 to configure. > Thank you, it works. > > But... why does MPIR do that? Why isn't it enough to trust compiler? > (I'm just curious) > > Tomasz Melcer > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/mpir-devel?hl=en. > > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
