Right, but if you also change the host to x86_64 it will never run config.guess, so it has no idea what CPUID returns. Then you should be able to select ABI=64 (or in fact that should be automatic).
Bill. 2009/2/5 mabshoff <michael.absh...@mathematik.uni-dortmund.de>: > > > > On Feb 5, 12:20 pm, Bill Hart <goodwillh...@googlemail.com> wrote: >> I don't understand why you don't get ABI=64 when you select >> -host=x86_64-blah. It *should* give you ABI = 64. If not there is some >> other problem here. > > Well, with gmp 4.2.1 on William's Xeon OSX box doing "ABI=64 ./ > configure" stopped dead in its tracks because gmp did not consider the > CPU in question capable of 64 bits. To get a 64 bit gmp 4.2.1 on that > box you had to set CFLAGS to include '-m64' and select the generic C > code. The same is likely to apply here since the AMD K6 is not 64 bits > and the abilist only has 32. I do not have access to the box is > question, so I cannot test any of this. > >> Perhaps I mean -build=x86_64-blah. > > Well, as mentioned in the last email it looks like a bug in kvm and/or > qemu to me. I checked and at least kvm on x86-64 requires > virtualization instructions that are only in somewhat recent AMD and > Intel CPUs, so selecting an AMD K6 as virtual CPU seems like a strange > choice. > >> Bill. > > Cheers, > > Michael > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
