[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
Is there a chance that there will be executables that run on my work machine with the next release? No, 3.4.2 won't have the fix, but 4.0 will in roughly two weeks. Looking forward to it. Or should I start compiling right now and maybe move to some SVN kind of thing? I don't know what you mean? You can upgrade from sage release to sage release, but there is no such thing as all the sources in some repo. Various bits and pieces of Sage are under version control. Was already wondering why I didn't find any information about a central version control system. What do you mean by upgrade? Just delete and download new binary? Ok, you left out what I truly cared about, i.e. the output from disassemble $pc+32,$pc-32 I was already pretty sure that MPIR/GMP was the issue here. In Sage 4.0 we will build MPIR for generic P4 CPUs so that the problem you ran into won't happen again. Cheers, Michael Hopefully not.. But in any case here is the output of gdb Cheers, Ivan --- i...@ivan-laptop:~$ ./sage -gdb -- | Sage Version 3.4.1, Release Date: 2009-04-21 | | Type notebook() for the GUI, and license() for information.| -- /home/ivan/aps/sage-3.4.1-linux-Ubuntu_8.10-sse2-i686-Linux/local/bin/ sage-ipython GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/ gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu... [Thread debugging using libthread_db enabled] Python 2.5.2 (r252:60911, Apr 24 2009, 04:52:24) [GCC 4.3.2] on linux2 Type help, copyright, credits or license for more information. [New Thread 0xb7e578d0 (LWP 4647)] Program received signal SIGILL, Illegal instruction. [Switching to Thread 0xb7e578d0 (LWP 4647)] 0xb7969542 in __gmpz_set_str () from /home/ivan/aps/sage-3.4.1-linux-Ubuntu_8.10-sse2-i686-Linux/ local/lib/libgmp.so.3 Current language: auto; currently asm (gdb) disassemble $pc+32,$pc-32 Dump of assembler code for function __gmpz_set_str: 0xb7969350 __gmpz_set_str+0: push %ebp 0xb7969351 __gmpz_set_str+1: mov%esp,%ebp 0xb7969353 __gmpz_set_str+3: push %edi 0xb7969354 __gmpz_set_str+4: push %esi 0xb7969355 __gmpz_set_str+5: push %ebx 0xb7969356 __gmpz_set_str+6: call 0xb796935b __gmpz_set_str+11 0xb796935b __gmpz_set_str+11: pop%ebx 0xb796935c __gmpz_set_str+12: add$0x31c99,%ebx 0xb7969362 __gmpz_set_str+18: sub$0x4c,%esp 0xb7969365 __gmpz_set_str+21: mov%gs:0x14,%edx 0xb796936c __gmpz_set_str+28: mov%edx,-0x10(%ebp) 0xb796936f __gmpz_set_str+31: xor%edx,%edx 0xb7969371 __gmpz_set_str+33: mov0x8(%ebp),%eax 0xb7969374 __gmpz_set_str+36: mov0xc(%ebp),%edi 0xb7969377 __gmpz_set_str+39: mov%eax,-0x34(%ebp) 0xb796937a __gmpz_set_str+42: cmpl $0x24,0x10(%ebp) 0xb796937e __gmpz_set_str+46: jg 0xb7969420 __gmpz_set_str+208 0xb7969384 __gmpz_set_str+52: mov-0x54(%ebx),%eax 0xb796938a __gmpz_set_str+58: mov%eax,-0x28(%ebp) 0xb796938d __gmpz_set_str+61: call 0xb79510a4 __ctype_b_...@plt 0xb7969392 __gmpz_set_str+66: mov%eax,-0x24(%ebp) 0xb7969395 __gmpz_set_str+69: mov(%eax),%ecx ---Type return to continue, or q return to quit--- 0xb7969397 __gmpz_set_str+71: mov%esi,%esi 0xb7969399 __gmpz_set_str+73: lea0x0(%edi,%eiz,1),%edi 0xb79693a0 __gmpz_set_str+80: movzbl (%edi),%esi 0xb79693a3 __gmpz_set_str+83: inc%edi 0xb79693a4 __gmpz_set_str+84: testb $0x20,0x1(%ecx,%esi,2) 0xb79693a9 __gmpz_set_str+89: jne0xb79693a0 __gmpz_set_str+80 0xb79693ab __gmpz_set_str+91: movl $0x0,-0x2c(%ebp) 0xb79693b2 __gmpz_set_str+98: cmp$0x2d,%esi 0xb79693b5 __gmpz_set_str+101:je 0xb7969488 __gmpz_set_str +312 0xb79693bb __gmpz_set_str+107:mov0x10(%ebp),%edx 0xb79693be __gmpz_set_str+110:mov$0xa,%eax 0xb79693c3 __gmpz_set_str+115:test %edx,%edx 0xb79693c5 __gmpz_set_str+117:mov-0x28(%ebp),%edx 0xb79693c8 __gmpz_set_str+120:cmovne 0x10(%ebp),%eax 0xb79693cc __gmpz_set_str+124:movzbl (%edx,%esi,1),%edx 0xb79693d0 __gmpz_set_str+128:cmp%edx,%eax 0xb79693d2 __gmpz_set_str+130:jle0xb7969426 __gmpz_set_str +214 0xb79693d4 __gmpz_set_str+132:mov0x10(%ebp),%eax 0xb79693d7 __gmpz_set_str+135:test %eax,%eax 0xb79693d9 __gmpz_set_str+137:jne0xb796944c __gmpz_set_str +252 0xb79693db __gmpz_set_str+139:movl $0xa,0x10(%ebp) 0xb79693e2 __gmpz_set_str+146:cmp$0x30,%esi 0xb79693e5 __gmpz_set_str+149:jne0xb796944c __gmpz_set_str +252 ---Type return to continue, or q return to quit--- 0xb79693e7 __gmpz_set_str+151:movzbl (%edi),%esi
[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
Is there a chance that there will be executables that run on my work machine with the next release? Or should I start compiling right now and maybe move to some SVN kind of thing? For completeness sake: i...@ivan-laptop:~/aps/sage-3.4.1-linux-Ubuntu_8.10-sse2-i686-Linux$ ./ sage -gdb -- | Sage Version 3.4.1, Release Date: 2009-04-21 | | Type notebook() for the GUI, and license() for information.| -- /home/ivan/aps/sage-3.4.1-linux-Ubuntu_8.10-sse2-i686-Linux/local/bin/ sage-ipython GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/ gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu... [Thread debugging using libthread_db enabled] Python 2.5.2 (r252:60911, Apr 24 2009, 04:52:24) [GCC 4.3.2] on linux2 Type help, copyright, credits or license for more information. [New Thread 0xb7dd28d0 (LWP 9733)] Program received signal SIGILL, Illegal instruction. [Switching to Thread 0xb7dd28d0 (LWP 9733)] 0xb78e4542 in __gmpz_set_str () from /home/ivan/aps/sage-3.4.1-linux-Ubuntu_8.10-sse2-i686-Linux/ local/lib/libgmp.so.3 Current language: auto; currently asm (gdb) i...@ivan-laptop:~/aps/sage-3.4.1-linux-Ubuntu_8.10-sse2-i686-Linux$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 12 model name : AMD Athlon(tm) 64 Processor 3400+ stepping: 0 cpu MHz : 2400.000 cache size : 512 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow up bogomips: 4823.56 clflush size: 64 power management: ts fid vid ttp --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
On May 4, 10:11 am, Iwan Lappo-Danilewski ivanjazz...@gmail.com wrote: Is there a chance that there will be executables that run on my work machine with the next release? No, 3.4.2 won't have the fix, but 4.0 will in roughly two weeks. Or should I start compiling right now and maybe move to some SVN kind of thing? I don't know what you mean? You can upgrade from sage release to sage release, but there is no such thing as all the sources in some repo. Various bits and pieces of Sage are under version control. SNIP Program received signal SIGILL, Illegal instruction. [Switching to Thread 0xb7dd28d0 (LWP 9733)] 0xb78e4542 in __gmpz_set_str () from /home/ivan/aps/sage-3.4.1-linux-Ubuntu_8.10-sse2-i686-Linux/ local/lib/libgmp.so.3 Current language: auto; currently asm (gdb) Ok, you left out what I truly cared about, i.e. the output from disassemble $pc+32,$pc-32 I was already pretty sure that MPIR/GMP was the issue here. In Sage 4.0 we will build MPIR for generic P4 CPUs so that the problem you ran into won't happen again. Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
Most likely you're right William.. It seems to be a compiler/processor issue, since I have a very similar configuration on my home machine where it runs perfectly. What is the output of cat /proc/cpuinfo on your computer? Here's the one of the machine where it runs perfectly on ubuntu (just for comparison).. I'll post the one from work (AMD64) and the gdb output on monday sage [4]: !cat /proc/ cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz stepping: 6 cpu MHz : 800.000 cache size : 3072 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm ida tpr_shadow vnmi flexpriority bogomips: 4788.08 clflush size: 64 power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz stepping: 6 cpu MHz : 800.000 cache size : 3072 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm ida tpr_shadow vnmi flexpriority bogomips: 4787.71 clflush size: 64 power management: --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
1. Was this the type of CPU that this binary was supposed to work for (having sse2 and not 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? 3. Can I compile Sage using a vmware player or do I need to upgrade vmware to compile Sage? 4. Can start from the failed installation of sage-vmware-sse2-3.4.1 and do a native compile? 5. Can I do sudo apt-get install of the software components I need 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. 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 --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
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 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 -~--~~~~--~~--~--~---
[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
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? 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 - --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
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 -~--~~~~--~~--~--~---
[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
Have to report a similar problem on ubuntu 9.04.. While version 3.2.3 is running as fine as the sagemath ubuntu package (3.0.5) the newest version won't start telling me ~/aps/sage-3.4.1-linux-Ubuntu_8.10-sse2-i686-Linux$ ./sage -- | Sage Version 3.4.1, Release Date: 2009-04-21 | | Type notebook() for the GUI, and license() for information.| -- ../aps/sage-3.4.1-linux-Ubuntu_8.10-sse2-i686-Linux/local/bin/sage- sage: line 198: 20057 Illegal instruction sage-ipython $@ -i Iwan --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
On Thu, Apr 30, 2009 at 10:43 AM, Iwan Lappo-Danilewski ivanjazz...@gmail.com wrote: Have to report a similar problem on ubuntu 9.04.. While version 3.2.3 is running as fine as the sagemath ubuntu package (3.0.5) the newest version won't start telling me What is the output of cat /proc/cpuinfo on your computer? ~/aps/sage-3.4.1-linux-Ubuntu_8.10-sse2-i686-Linux$ ./sage -- | Sage Version 3.4.1, Release Date: 2009-04-21 | | Type notebook() for the GUI, and license() for information. | -- ../aps/sage-3.4.1-linux-Ubuntu_8.10-sse2-i686-Linux/local/bin/sage- sage: line 198: 20057 Illegal instruction sage-ipython $@ -i Iwan -- 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 -~--~~~~--~~--~--~---
[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
On Apr 30, 10:53 am, William Stein wst...@gmail.com wrote: On Thu, Apr 30, 2009 at 10:43 AM, Iwan Lappo-Danilewski ivanjazz...@gmail.com wrote: Have to report a similar problem on ubuntu 9.04.. While version 3.2.3 is running as fine as the sagemath ubuntu package (3.0.5) the newest version won't start telling me What is the output of cat /proc/cpuinfo on your computer? Well, I am not sure if gdb is installed in the VMWare image (it ought to be trivially installable into a real Linux install), but the following would be helpful to determine which instruction causes the problem. Start sage via gdb, i.e. ./sage -gdb Tell it to run, i.e. press r. Then it crashes. Punch in bt disass $pc-32 $pc+32 and post the output :) Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
William, Thanks I was able to compile sage 3.4.1 on my XP machine starting from sage-vmware-sse2-3.4.1, which had failed work from the binary, by following your directions. For people that might know even less about linux than me the steps I took were: At the login type: login The Passward is: sage then type: sudo su 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 Thanks Mike On Apr 30, 2:34 pm, mabshoff michael.absh...@mathematik.uni- dortmund.de wrote: On Apr 30, 10:53 am, William Stein wst...@gmail.com wrote: On Thu, Apr 30, 2009 at 10:43 AM, Iwan Lappo-Danilewski ivanjazz...@gmail.com wrote: Have to report a similar problem on ubuntu 9.04.. While version 3.2.3 is running as fine as the sagemath ubuntu package (3.0.5) the newest version won't start telling me What is the output of cat /proc/cpuinfo on your computer? Well, I am not sure if gdb is installed in the VMWare image (it ought to be trivially installable into a real Linux install), but the following would be helpful to determine which instruction causes the problem. Start sage via gdb, i.e. ./sage -gdb Tell it to run, i.e. press r. Then it crashes. Punch in bt disass $pc-32 $pc+32 and post the output :) Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
I typed needed to type: Login Sage su sage and I got: Authentication failure Sorry The above resposes were to login and passward. By the way I also check the MD5 and it was correct. Thanks Mike On Apr 27, 10:27 am, William Stein wst...@gmail.com wrote: On Mon, Apr 27, 2009 at 10:25 AM, madison.mich...@gmail.com wrote: On starting sage-vmware-sse2-3.4.1 I get the text menus in vmware. However, on starting either Sage or Notebook it starts and then returns me to the text menus again. When running Sage from the text menu I don't get any error messages before it fails. My vmware sage worked fine for sage 3.2.3. I am using: sage-vmware-sse2-3.4.1 binary Intel Celeron M 1.5 GHz, 1 GB Ram Microsoft Windows XP Professional 5.1.2600, Service Pack 3 VMWARE 2.5.1 build-126130 Previously I could not get sate 3.4 to work on my windows machine. What happens when you type: login: admin $ su - sage ? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
Sorry I forgot to type sudo I got: /usr/local/sage/local/bin/sage-sage: line 198: 3586 Illegal instruction sage-ipython $@ -i Mike Madison On Apr 27, 10:27 am, William Stein wst...@gmail.com wrote: On Mon, Apr 27, 2009 at 10:25 AM, madison.mich...@gmail.com wrote: On starting sage-vmware-sse2-3.4.1 I get the text menus in vmware. However, on starting either Sage or Notebook it starts and then returns me to the text menus again. When running Sage from the text menu I don't get any error messages before it fails. My vmware sage worked fine for sage 3.2.3. I am using: sage-vmware-sse2-3.4.1 binary Intel Celeron M 1.5 GHz, 1 GB Ram Microsoft Windows XP Professional 5.1.2600, Service Pack 3 VMWARE 2.5.1 build-126130 Previously I could not get sate 3.4 to work on my windows machine. What happens when you type: login: admin $ su - sage ? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
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 --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-support] Re: Failure running sage-vmware-sse2-3.4.1
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 --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
