MPIR already provides that.
On Jan 13, 7:14 pm, "Dr. David Kirkby"
wrote:
> Bill Hart wrote:
> > For the OpenSolaris setup, could you print the contents of config.log
> > so we can see what went wrong. The usual problem is it can't find a
> > working C compiler for config.sub, but config.log will
Bill Hart wrote:
For the OpenSolaris setup, could you print the contents of config.log
so we can see what went wrong. The usual problem is it can't find a
working C compiler for config.sub, but config.log will tell us what
actually happened (hopefully). It's a long file
Bill.
Can you copy
For the OpenSolaris setup, could you print the contents of config.log
so we can see what went wrong. The usual problem is it can't find a
working C compiler for config.sub, but config.log will tell us what
actually happened (hopefully). It's a long file
Bill.
On Jan 13, 3:45 pm, Jaap Spies w
Gonzalo Tornaria wrote:
On Wed, Jan 13, 2010 at 12:06 PM, Jaap Spies wrote:
Gonzalo Tornaria wrote:
On Wed, Jan 13, 2010 at 11:43 AM, Jaap Spieswrote:
gcc version 4.4.2 20091222 (Red Hat 4.4.2-20) (GCC)
checking build system type... x
On Wed, Jan 13, 2010 at 12:06 PM, Jaap Spies wrote:
> Gonzalo Tornaria wrote:
>>
>> On Wed, Jan 13, 2010 at 11:43 AM, Jaap Spies wrote:
>>>
>>> gcc version 4.4.2 20091222 (Red Hat 4.4.2-20) (GCC)
>>>
>>> checking build system type... x86_64-unk
Gonzalo Tornaria wrote:
On Wed, Jan 13, 2010 at 11:43 AM, Jaap Spies wrote:
gcc version 4.4.2 20091222 (Red Hat 4.4.2-20) (GCC)
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
Sti
On Wed, Jan 13, 2010 at 11:43 AM, Jaap Spies wrote:
> gcc version 4.4.2 20091222 (Red Hat 4.4.2-20) (GCC)
>
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
Still misdetected, it s
Bill Hart wrote:
Ah, I see in a later trac update you have the same problem in Fedora.
But surely there you have cat /proc/cpuinfo. What information does it
give you? We might be able to tackle the problem from there.
I had the wrong Fedora running.
On Fedora 12 64 bit in Virtualbox:
gcc ver
On Wed, Jan 13, 2010 at 9:18 AM, Bill Hart wrote:
> Ah, I see in a later trac update you have the same problem in Fedora.
> But surely there you have cat /proc/cpuinfo. What information does it
> give you? We might be able to tackle the problem from there.
>> > This is in VirtualBox, so virtual p
Ah, I see in a later trac update you have the same problem in Fedora.
But surely there you have cat /proc/cpuinfo. What information does it
give you? We might be able to tackle the problem from there.
Bill.
On Jan 13, 11:14 am, Bill Hart wrote:
> To be honest, I really don't know. You are going
To be honest, I really don't know. You are going to have to ask a
Virtual Box/Open Solaris expert on this. Maybe Open Solaris doesn't
play nice with Virtual Box on your particular hardware.
Either way, if it lies to MPIR about what the processor is, there
isn't a whole lot we can do.
Of course yo
Bill Hart wrote:
MPIR should detect all known intel and amd CPU's (MPIR 1.3 will also
detect via and atom's), but for some reason it doesn't detect yours.
To perform the detection it asks the CPU what it is, using the CPUID
instruction.
2 possiblities:
1) The CPUID instruction is returning the
brandon.bar...@gmail.com wrote:
psrinfo -v seems to be one option, though I think /proc/cpuinfo seems
to be better in linux.
I gave the output of prsinfo below, but it shows nothing more useful than the
fact there are 8 virtual processors running at 3325 MHz. (It's a quad core Xeon,
with two
psrinfo -v seems to be one option, though I think /proc/cpuinfo seems
to be better in linux.
On Jan 12, 11:08 pm, "Dr. David Kirkby"
wrote:
> Bill Hart wrote:
> > MPIR should detect all known intel and amd CPU's (MPIR 1.3 will also
> > detect via and atom's), but for some reason it doesn't detec
Bill Hart wrote:
MPIR should detect all known intel and amd CPU's (MPIR 1.3 will also
detect via and atom's), but for some reason it doesn't detect yours.
To perform the detection it asks the CPU what it is, using the CPUID
instruction.
2 possiblities:
1) The CPUID instruction is returning the
MPIR should detect all known intel and amd CPU's (MPIR 1.3 will also
detect via and atom's), but for some reason it doesn't detect yours.
To perform the detection it asks the CPU what it is, using the CPUID
instruction.
2 possiblities:
1) The CPUID instruction is returning the wrong thing
2) It
Dr. David Kirkby wrote:
Jaap Spies wrote:
Shall I open a trac ticket?
Jaap
I believe you should open a ticket for this.
This is http://trac.sagemath.org/sage_trac/ticket/7910
Jaap
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this grou
Bill Hart wrote:
There aren't any 64 bit 486's. It's misdetecting your CPU.
Bill.
What can I do about that?
Jaap
On Jan 12, 3:31 pm, Jaap Spies wrote:
In Open Solaris in my VirtualBox running under Fedora 12 64 bit on an Intel i7
860:
Finished extraction
***
There aren't any 64 bit 486's. It's misdetecting your CPU.
Bill.
On Jan 12, 3:31 pm, Jaap Spies wrote:
> In Open Solaris in my VirtualBox running under Fedora 12 64 bit on an Intel
> i7 860:
>
> Finished extraction
>
> Host system
> uname -a:
Jaap Spies wrote:
Dr. David Kirkby wrote:
Jaap Spies wrote:
In Open Solaris in my VirtualBox running under Fedora 12 64 bit on an
Intel i7 860:
[...]
In contrast Jaap is running some other operating system (Linux of some
sort ??), and using VirtualBox to install Open Solaris. I doubt that
Dr. David Kirkby wrote:
Jaap Spies wrote:
In Open Solaris in my VirtualBox running under Fedora 12 64 bit on an
Intel i7 860:
[...]
In contrast Jaap is running some other operating system (Linux of some
sort ??), and using VirtualBox to install Open Solaris. I doubt that
makes any differen
21 matches
Mail list logo
