On Thu, Apr 30, 2009 at 9:56 AM, <madison.mich...@gmail.com> wrote:
>
> Just to clarify:
>
> Starting from my failed installation of sage-vmware-sse2-3.4.1 can i
> just change to the /usr/local/sage directory and type make to get a
> native compile?
Not exactly. You must
1. Just delete /usr/local/sage, then
cd /usr/local; rm -rf sage
2. download sage-3.4.1.tar by typing
wget http://sagemath.org/src/sage-3.4.1.tar
3. extract it,
tar xvf sage-3.4.1.tar
4. move it to be /usr/local/sage, and
mv sage-3.4.1 sage
5. type make.
cd sage; make
William
>
> Thanks Mike
>
> On Apr 30, 8:45 am, William Stein <wst...@gmail.com> wrote:
>> On Thu, Apr 30, 2009 at 3:50 AM, <madison.mich...@gmail.com> wrote:
>>
>> > 1. Was this the type of CPU that this binary was supposed to work for
>> > (having sse2 and not sse3)?
>>
>> Maybe. But the issue might not be just sse3.
>>
>>
>>
>> > 2. Is Sage migrating to work on only modern duel core CPUs? I have
>> > compiled Sage 3.4 on an older processor Ubuntu linux notebook and it
>> > worked. Is this going away?
>>
>> No. No. You can run Sage on nearly any CPU if you build from source.
>>
>> > 3. Can I compile Sage using a vmware player or do I need to upgrade
>> > vmware to compile Sage?
>>
>> You can compile sage. Just delete /usr/local/sage, then download
>> sage-3.4.1, extract it, move it to be /usr/local/sage, and
>> type make. Wait a few hours. That's precisely how I made the
>> current /usr/local/sage directory.
>>
>>
>>
>> > 4. Can start from the failed installation of sage-vmware-sse2-3.4.1
>> > and do a native compile?
>>
>> Yes.
>>
>>
>>
>> > 5. Can I do "sudo apt-get install" of the software components I need
>> > to compile Sage in vmware?
>>
>> You don't need any extra software components to compile sage in vmware.
>>
>> > It seems some of us using windows XP are locked out of using Sage 3.4,
>> > but we don't understand what the road block is.
>>
>> I don't think Windows XP is relevant. It's your old processor.
>>
>> -- William
>>
>>
>>
>>
>>
>>
>>
>> > Thanks Mike
>>
>> > On Apr 27, 11:37 am, madison.mich...@gmail.com wrote:
>> >> processor : 0
>> >> vendor_id : GenuineIntel
>> >> cpu family : 6
>> >> model : 13
>> >> model name : Intel(R) Celeron(R) M processor 1.50GHz
>> >> stepping : 8
>> >> cpu MHz : 1476.382
>> >> cache size : 1024 KB
>> >> fdiv_bug : no
>> >> hlt_bug : no
>> >> f00f_bug : no
>> >> coma_bug : no
>> >> fpu : yes
>> >> fpu_exception : yes
>> >> cpuid level : 2
>> >> wp : yes
>> >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
>> >> pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss nx up
>> >> bogomips : 3007.50
>>
>> >> Thanks Mike Madison
>>
>> >> On Apr 27, 11:20 am, William Stein <wst...@gmail.com> wrote:
>>
>> >> > On Mon, Apr 27, 2009 at 10:56 AM, <madison.mich...@gmail.com> wrote:
>>
>> >> > > Sorry I forgot to type sudo
>>
>> >> > > I got:
>>
>> >> > > /usr/local/sage/local/bin/sage-sage: line 198: 3586 Illegal
>> >> > > instruction sage-ipython "$@" -i
>>
>> >> > This means you can't run the Sage vmware image on your computer, i.e.,
>> >> > it is was built for a processor that is newer than yours. What does
>> >> > the output of
>>
>> >> > cat /proc/cpuinfo
>>
>> >> > say?
>>
>> >> > William
>>
>> --
>> William Stein
>> Associate Professor of Mathematics
>> University of Washingtonhttp://wstein.org- Hide quoted text -
>>
>> - Show quoted text -
> >
>
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
