On Feb 5, 1:04 am, Willem Jan Palenstijn <w...@usecode.org> wrote:
> Hi,

Hi,

I talked to wjp about this in #sage-devel, so I have a head start :)

> When building the mpir shipped with sage 3.3.alpha5 (r1555) on a
> kvm/qemu amd64 virtual machine I get a 32-bit libgmp.so.
>
> The two config*.guess scripts report:
> [r...@localhost src]# bash config.guess
> athlon-unknown-linux-gnu
> [r...@localhost src]# bash configfsf.guess
> x86_64-unknown-linux-gnu
>
> cpuinfo:
> processor       : 0
> vendor_id       : AuthenticAMD
> cpu family      : 6
> model           : 2

I tried finding a CPU family 6, model 2 AMD CPU and I am not sure such
a thing exists, certainly not as 64 bit CPU.

> model name      : QEMU Virtual CPU version 0.9.1

That won't be very helpful, either :)

> stepping        : 3
> cpu MHz         : 2411.119
> cache size      : 512 KB
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 2
> wp              : yes
> flags           : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx lm up pni
> bogomips        : 4828.63
> TLB size        : 1024 4K pages
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 40 bits physical, 48 bits virtual
> power management:
>
> See below for the start of config.log. The full config.log is available 
> athttp://www.math.leidenuniv.nl/~wpalenst/sage/kvm_amd64_config.log.
>
> If you need any other information, please let me know.
>
> Kind regards,
> Willem Jan
>
> -----------------

<SNIP>

> abilist=32

This is the culprit since abilist should have 32 64.

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
-~----------~----~----~----~------~----~------~--~---

Reply via email to