[sage-support] Re: Porting Sage to AIX
Hi Michael, ParaTools, Inc. has ported SAGE successfully to AIX! We had to rebuild the library and debug it further but now I can say: set path=($PET_HOME/pkgs/sage-3.1.1 $path) sage -- | SAGE Version 3.1.1, Release Date: 2008-08-17 | | Type notebook() for the GUI, and license() for information.| -- sage: import numpy sage: numpy.test() Numpy is installed in /usr/local/PET/pkgs/sage-3.1.1/local/lib/ python2.5/site-packages/numpy Numpy version 1.0.4 Python version 2.5.2 (r252:60911, Oct 18 2008, 03:31:49) [GCC 4.2.1] Found 10/10 tests for numpy.core.defmatrix Found 36/36 tests for numpy.core.ma Found 223/223 tests for numpy.core.multiarray Found 65/65 tests for numpy.core.numeric Found 31/31 tests for numpy.core.numerictypes Found 12/12 tests for numpy.core.records Found 6/6 tests for numpy.core.scalarmath Found 14/14 tests for numpy.core.umath Found 4/4 tests for numpy.ctypeslib Found 5/5 tests for numpy.distutils.misc_util Found 1/1 tests for numpy.fft.fftpack Found 3/3 tests for numpy.fft.helper Found 9/9 tests for numpy.lib.arraysetops Found 46/46 tests for numpy.lib.function_base Found 5/5 tests for numpy.lib.getlimits Found 4/4 tests for numpy.lib.index_tricks Found 3/3 tests for numpy.lib.polynomial Found 49/49 tests for numpy.lib.shape_base Found 15/15 tests for numpy.lib.twodim_base Found 43/43 tests for numpy.lib.type_check Found 1/1 tests for numpy.lib.ufunclike Found 40/40 tests for numpy.linalg Found 2/2 tests for numpy.random Found 0/0 tests for __main__ -- Ran 680 tests in 1.228s OK unittest._TextTestResult run=680 errors=0 failures=0 sage: integrate(tan(x),x) log(sec(x)) sage: a = matrix(ZZ, 10, 4, [randint(0,1) for _ in xrange(40)]); a [0 1 1 0] [1 0 0 0] [0 0 1 1] [0 0 0 0] [1 0 1 1] [1 0 1 1] [1 1 0 1] [1 1 0 0] [0 1 0 1] [0 1 0 0] sage: list(AllExactCovers(a)) [[(0, 0, 1, 1), (1, 0, 0, 0), (0, 1, 0, 0)], [(0, 0, 1, 1), (1, 1, 0, 0)], [(1, 0, 1, 1), (0, 1, 0, 0)], [(1, 0, 1, 1), (0, 1, 0, 0)]] sage: 22+32 54 sage: 3/4+1/6 11/12 sage: Exiting SAGE (CPU time 0m1.86s, Wall time 1m28.08s). Exiting spawned Maxima process. uname -a AIX 3 5 002B912C4C00 The last error was resolved by printing the type of the object that was of type pari.gen. When we rebuilt that library by hand and the dependencies, it worked. I should also add (for the list) that we had to build clisp and gap in 32 bits and change gap.py to use a fixed big number for the file descriptors as the max fileno from getrusage was not working properly in AIX. This change fixed pexpect. Thanks a lot for your help! I look forward to discussing these issues and help with documenting this at the SD 11 with you. - Sameer On Nov 3, 11:37 pm, Sameer [EMAIL PROTECTED] wrote: Michael, An update. I rebuilt liblinboxsage.a by omiting Communicator.o and using a simple g++ -shared -o command that tied in the .o files. I think the crash occured at Communicator.c but I saw a - DDISABLE_COMMUNICATOR. So, I rebuilt the .a file and then it loaded properly until the next crash. The earlier crashes were linked to the first instance of a routine not executing properly due to a shared object that was not built properly. Now I am facing another kind of error where the same routine executes correctly a few times and then crashes at returnsage.rings.rational.Rational(x, base) in rational_field.py. I modified it: (Pdb) c rational_field.py: SSS: after crash myretval = 1 rational_field.py: SSS: before crash, x = 1 base = 0 /usr/local/PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/ rings/rational_field.py(221)__call__() - myretval =sage.rings.rational.Rational(x, base) (Pdb) s Unhandled SIGSEGV: A segmentation fault occured inSAGE. This probably occured because a *compiled* component ofSAGEhas a bug in it (typically accessing invalid memory) or is not properly wrapped with _sig_on, _sig_off. You might want to runSAGEunder gdb with 'sage-gdb' to debug this. But the output suggests
[sage-support] Re: Porting Sage to AIX
On Nov 6, 3:18 pm, Sameer [EMAIL PROTECTED] wrote: Hi Michael, Hi Sameer, ParaTools, Inc. has ported SAGE successfully to AIX! We had to rebuild the library and debug it further but now I can say: set path=($PET_HOME/pkgs/sage-3.1.1 $path) sage -- | SAGE Version 3.1.1, Release Date: 2008-08-17 | | Type notebook() for the GUI, and license() for information. | -- Excellent! sage: import numpy sage: numpy.test() Numpy is installed in /usr/local/PET/pkgs/sage-3.1.1/local/lib/ python2.5/site-packages/numpy Numpy version 1.0.4 Python version 2.5.2 (r252:60911, Oct 18 2008, 03:31:49) [GCC 4.2.1] Found 10/10 tests for numpy.core.defmatrix Found 36/36 tests for numpy.core.ma Found 223/223 tests for numpy.core.multiarray Found 65/65 tests for numpy.core.numeric Found 31/31 tests for numpy.core.numerictypes Found 12/12 tests for numpy.core.records Found 6/6 tests for numpy.core.scalarmath Found 14/14 tests for numpy.core.umath Found 4/4 tests for numpy.ctypeslib Found 5/5 tests for numpy.distutils.misc_util Found 1/1 tests for numpy.fft.fftpack Found 3/3 tests for numpy.fft.helper Found 9/9 tests for numpy.lib.arraysetops Found 46/46 tests for numpy.lib.function_base Found 5/5 tests for numpy.lib.getlimits Found 4/4 tests for numpy.lib.index_tricks Found 3/3 tests for numpy.lib.polynomial Found 49/49 tests for numpy.lib.shape_base Found 15/15 tests for numpy.lib.twodim_base Found 43/43 tests for numpy.lib.type_check Found 1/1 tests for numpy.lib.ufunclike Found 40/40 tests for numpy.linalg Found 2/2 tests for numpy.random Found 0/0 tests for __main__ ... ... ... ... ... ... ... ... ... . -- Ran 680 tests in 1.228s OK unittest._TextTestResult run=680 errors=0 failures=0 sage: integrate(tan(x),x) log(sec(x)) sage: a = matrix(ZZ, 10, 4, [randint(0,1) for _ in xrange(40)]); a [0 1 1 0] [1 0 0 0] [0 0 1 1] [0 0 0 0] [1 0 1 1] [1 0 1 1] [1 1 0 1] [1 1 0 0] [0 1 0 1] [0 1 0 0] sage: list(AllExactCovers(a)) [[(0, 0, 1, 1), (1, 0, 0, 0), (0, 1, 0, 0)], [(0, 0, 1, 1), (1, 1, 0, 0)], [(1, 0, 1, 1), (0, 1, 0, 0)], [(1, 0, 1, 1), (0, 1, 0, 0)]] sage: 22+32 54 sage: 3/4+1/6 11/12 sage: Exiting SAGE (CPU time 0m1.86s, Wall time 1m28.08s). Exiting spawned Maxima process. uname -a AIX 3 5 002B912C4C00 The last error was resolved by printing the type of the object that was of type pari.gen. When we rebuilt that library by hand and the dependencies, it worked. Interesting. I should also add (for the list) that we had to build clisp and gap in 32 bits Ok, that should not be a problem. It would be nice to have GAP work in 64 bit mode, but that can be sorted out later. We will dumb clisp for ecl in the future anyway, so I would not worry too much there. The ecl maintainer does not support AIX yet due to lack of access, but a port should be little work since it practically runs on everything. and change gap.py to use a fixed big number for the file descriptors as the max fileno from getrusage was not working properly in AIX. This change fixed pexpect. Nice. Thanks a lot for your help! I look forward to discussing these issues and help with documenting this at the SD 11 with you. Cool. Hopefully William will get access to that AIX cluster soon so that we can start merging back fixes sooner than that. It would be very helpful if you could post patches and notes to the Wiki page. The output from make check would also be helpful. It might happen that it hangs at some point in which case a CTRL-C or a manual kill of the current doctest would get you past that. I would be *very* interested in how that works out. One bug you certainly have to fix is get_memory_usage() since that one requires support for AIX to be added. There are likely other places where you might run into trouble. Unfortunately getting Sage to build up and start is only half of the battle since making it pass its test suite can be a lot of work. For example the Solaris port has been building more or less out of the box for
[sage-support] Re: Porting Sage to AIX
Michael, William, Here is an update on AIX. I found why sage startup was crashing in real_mpfi.so. I rebuilt libmpfi.so and recompiled real_mpfi.pyx and complex_double.pyx. The illegal instruction error was due to an error in building libmpfi.so caused by arguments given by libtool. By testing with the supplied testcases I was able to narrow it down. Also, for the list, I edited sage/rings/polynomial/ mult_polynomial_libsingular.pyx and replaced the arguments to dlopen call to handle = dlopen(lib, 65536+4); It was using 256+1 earlier (RTLD_GLOBAL | RTLD_LAZY). These values are defined differently in AIX's dlfcn.h as shown above. Now I am running into another error: /usr/local/PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/matrix/matrix_space.py(38)module() - import matrix_modn_dense (Pdb) s --Call-- /usr/local/PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/libs/linbox/__init__.py(1)module() (Pdb) s /usr/local/PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/libs/linbox/__init__.py(1)module() (Pdb) s --Return-- /usr/local/PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/libs/linbox/__init__.py(1)module()-None (Pdb) s /usr/local/PET/src/build/sage-3.1.1/local/bin/sage-sage: line 226: 28756 Illegal instruction (core dumped) sage-ipython $@ -c $SAGE_STARTUP_COMMAND; I checked the __init__.py file and it has 0 bytes: ls -lt /usr/local/ PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/libs/ linbox/__init__.py -rw-r-1 sameer 0 Dec 20 2007 /usr/local/PET/ src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/libs/ linbox/__init__.py Is this normal? I think there may be another library (linbox) that probably needs to be rebuilt, but what I was wondering if this null init.py file is designed to be this way or if it is just an error in my installation. I think the illegal instruction probably points to an incorrectly installed liblinbox.so on which linbox.so is based, but I thought I would check with you. Thanks! - Sameer On Oct 28, 3:19 pm, Sameer [EMAIL PROTECTED] wrote: Michael, William, Thank you so much for the suggestions. I will re-install pexpect and see if it helps. Yes, I am getting closer to the end (~60-70 packages built) but without pexpect/gap it is difficult to get sage to boot up. I will meet and speak to Jose this week and request that you get accounts on their IBM AIX and Linux system. There may be some delay due to the paperwork involved, but it would be great if we can add support for these systems in the sage repository. I have also ported sage to ppc64 Linux at their center. I will keep you posted on the progress on AIX. Thanks! - Sameer On Oct 28, 4:21 am, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Oct 27, 10:42 pm, William Stein [EMAIL PROTECTED] wrote: On Mon, Oct 27, 2008 at 9:15 PM, Sameer [EMAIL PROTECTED] wrote: Hi, I am trying to port sage 3.1.1 to an IBM Power5 AIX system. After I install gap (in 32 bits), I get: So how far did you get building Sage? If GAP is the problem it sounds like you get next to the end. From the error messages above it also seems like it could be a pexpect issue. If GAP by itself starts up cleanly I would assume that the problem is in pexpect. Just out of curiosity, is this a machine you could give some (any?) of the Sage developers accounts on? We would love to officially support AIX. So far, none of us have ever been able to get access to an AIX box. +1 William Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Porting Sage to AIX
On Nov 3, 6:39 pm, Sameer [EMAIL PROTECTED] wrote: Michael, William, Hi Sameer, good that we are back on the list again. Here is an update on AIX. I found why sage startup was crashing in real_mpfi.so. I rebuilt libmpfi.so and recompiled real_mpfi.pyx and complex_double.pyx. The illegal instruction error was due to an error in building libmpfi.so caused by arguments given by libtool. By testing with the supplied testcases I was able to narrow it down. Ok, can you give some details what had to be changed? Also, for the list, I edited sage/rings/polynomial/ mult_polynomial_libsingular.pyx and replaced the arguments to dlopen call to handle = dlopen(lib, 65536+4); It was using 256+1 earlier (RTLD_GLOBAL | RTLD_LAZY). These values are defined differently in AIX's dlfcn.h as shown above. This will be fixed in Sage 3.2 and a patch is at http://trac.sagemath.org/sage_trac/ticket/4427 Now I am running into another error: /usr/local/PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/ matrix/matrix_space.py(38)module() - import matrix_modn_dense (Pdb) s --Call-- /usr/local/PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/ libs/linbox/__init__.py(1)module() (Pdb) s /usr/local/PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/ libs/linbox/__init__.py(1)module() (Pdb) s --Return-- /usr/local/PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/ libs/linbox/__init__.py(1)module()-None (Pdb) s /usr/local/PET/src/build/sage-3.1.1/local/bin/sage-sage: line 226: 28756 Illegal instruction (core dumped) sage-ipython $@ -c $SAGE_STARTUP_COMMAND; Ok, that could be the BLAS or something in LinBox itself. How did you build ATLAS? I checked the __init__.py file and it has 0 bytes: ls -lt /usr/local/ PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/libs/ linbox/__init__.py -rw-r- 1 sameer 0 Dec 20 2007 /usr/local/PET/ src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/libs/ linbox/__init__.py Is this normal? That should be ok, all that is required is that file to exist IRC. I think there may be another library (linbox) that probably needs to be rebuilt, but what I was wondering if this null init.py file is designed to be this way or if it is just an error in my installation. I think the illegal instruction probably points to an incorrectly installed liblinbox.so on which linbox.so is based, but I thought I would check with you. You should get a svn checkout of LinBox and run make check - in Sage we patch the commentator and that breaks make check. Should LinBox pass its make check we can keep on digging. Thanks! - Sameer Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Porting Sage to AIX
Hi Michael, Here is an update on AIX. I found why sage startup was crashing in real_mpfi.so. I rebuilt libmpfi.so and recompiled real_mpfi.pyx and complex_double.pyx. The illegal instruction error was due to an error in building libmpfi.so caused by arguments given by libtool. By testing with the supplied testcases I was able to narrow it down. Ok, can you give some details what had to be changed? I just did a manual: % cd spkg/build; cp -r mpfi* mympfi (the package builds without error and deletes the sources, so it is important to copy it midway while it is building); % cd mympfi; make; % gcc -shared -o libmpfi.so ../src/.libs/*.o -L/usr/local/PET/src/ build/sage-3.1.1/local/lib -lmpfr -lgmp cp libmpfi $SAGE_LOCAL/lib and tested with the tests/test_mpfi to make sure it didn't crash with the illegal instruction. Also, for the list, I edited sage/rings/polynomial/ mult_polynomial_libsingular.pyx and replaced the arguments to dlopen call to handle = dlopen(lib, 65536+4); It was using 256+1 earlier (RTLD_GLOBAL | RTLD_LAZY). These values are defined differently in AIX's dlfcn.h as shown above. This will be fixed in Sage 3.2 and a patch is athttp://trac.sagemath.org/sage_trac/ticket/4427 Now I am running into another error: /usr/local/PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/ matrix/matrix_space.py(38)module() - import matrix_modn_dense (Pdb) s --Call-- /usr/local/PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/ libs/linbox/__init__.py(1)module() (Pdb) s /usr/local/PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/ libs/linbox/__init__.py(1)module() (Pdb) s --Return-- /usr/local/PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/ libs/linbox/__init__.py(1)module()-None (Pdb) s /usr/local/PET/src/build/sage-3.1.1/local/bin/sage-sage: line 226: 28756 Illegal instruction (core dumped) sage-ipython $@ -c $SAGE_STARTUP_COMMAND; Ok, that could be the BLAS or something in LinBox itself. How did you build ATLAS? I checked the __init__.py file and it has 0 bytes: ls -lt /usr/local/ PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/libs/ linbox/__init__.py -rw-r- 1 sameer 0 Dec 20 2007 /usr/local/PET/ src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/libs/ linbox/__init__.py Is this normal? That should be ok, all that is required is that file to exist IRC. I think there may be another library (linbox) that probably needs to be rebuilt, but what I was wondering if this null init.py file is designed to be this way or if it is just an error in my installation. I think the illegal instruction probably points to an incorrectly installed liblinbox.so on which linbox.so is based, but I thought I would check with you. You should get a svn checkout of LinBox and run make check - in Sage we patch the commentator and that breaks make check. Should LinBox pass its make check we can keep on digging. Thanks I will rebuild it! - Sameer --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Porting Sage to AIX
On Nov 3, 7:04 pm, Sameer [EMAIL PROTECTED] wrote: Hi Michael, Here is an update on AIX. I found why sage startup was crashing in real_mpfi.so. I rebuilt libmpfi.so and recompiled real_mpfi.pyx and complex_double.pyx. The illegal instruction error was due to an error in building libmpfi.so caused by arguments given by libtool. By testing with the supplied testcases I was able to narrow it down. Ok, can you give some details what had to be changed? I just did a manual: % cd spkg/build; cp -r mpfi* mympfi (the package builds without error and deletes the sources, so it is important to copy it midway while it is building); Yes. Just run ./sage -sh, then cd into spkg/standard, tar xjf foo.spkg, cd into foo and run ./spkg-install. % cd mympfi; make; % gcc -shared -o libmpfi.so ../src/.libs/*.o -L/usr/local/PET/src/ build/sage-3.1.1/local/lib -lmpfr -lgmp cp libmpfi $SAGE_LOCAL/lib and tested with the tests/test_mpfi to make sure it didn't crash with the illegal instruction. Ok, but why would a static library crash? SNIP Thanks I will rebuild it! - Sameer Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Porting Sage to AIX
Michael, An update. I rebuilt liblinboxsage.a by omiting Communicator.o and using a simple g++ -shared -o command that tied in the .o files. I think the crash occured at Communicator.c but I saw a - DDISABLE_COMMUNICATOR. So, I rebuilt the .a file and then it loaded properly until the next crash. The earlier crashes were linked to the first instance of a routine not executing properly due to a shared object that was not built properly. Now I am facing another kind of error where the same routine executes correctly a few times and then crashes at return sage.rings.rational.Rational(x, base) in rational_field.py. I modified it: (Pdb) c rational_field.py: SSS: after crash myretval = 1 rational_field.py: SSS: before crash, x = 1 base = 0 /usr/local/PET/src/build/sage-3.1.1/local/lib/python2.5/site-packages/sage/rings/rational_field.py(221)__call__() - myretval = sage.rings.rational.Rational(x, base) (Pdb) s Unhandled SIGSEGV: A segmentation fault occured in SAGE. This probably occured because a *compiled* component of SAGE has a bug in it (typically accessing invalid memory) or is not properly wrapped with _sig_on, _sig_off. You might want to run SAGE under gdb with 'sage -gdb' to debug this. But the output suggests that it works properly some times: ./sage args = , sage_startup_cmd = , import sage.misc.misc; print sage.misc.misc.branch_current_hg_notice(sage.misc.misc.branch_current_hg()); from sage.misc.interpreter import preparser; preparser(True);import sage.all_cmdline; sage.all_cmdline._init_cmdline(globals());from sage.all import Integer, RealNumber;import os; os.chdir(/usr/local/ PET/src/build/sage-3.1.1);import sage.misc.interpreter;from sage.misc.interpreter import attached_files;from sage.all_cmdline import *;_=sage.misc.interpreter.load_startup_file(/Dev_users/ sameer/.sage//init.sage) -- | SAGE Version 3.1.1, Release Date: 2008-08-17 | | Type notebook() for the GUI, and license() for information.| -- real_mpfi: after __init__ real_mpfi: after __init__ real_mpfi: after __init__ real_mpfi: after __init__ rational_field.py: SSS: before crash, x = 0 base = 0 rational_field.py: SSS: after crash myretval = 0 rational_field.py: SSS: before crash, x = 1 base = 0 rational_field.py: SSS: after crash myretval = 1 rational_field.py: SSS: before crash, x = 0 base = 0 rational_field.py: SSS: after crash myretval = 0 rational_field.py: SSS: before crash, x = 1 base = 0 rational_field.py: SSS: after crash myretval = 1 real_mpfi: after __init__ qqbar.py: SSS: After self._descr._interval_fast : self._value = 0.? e-21 real_mpfi: after __init__ qqbar.py: SSS: After self._descr._interval_fast : self._value = 1.? real_mpfi: after __init__ qqbar.py: SSS: After self._descr._interval_fast : self._value = 0.? e-21 real_mpfi: after __init__ qqbar.py: SSS: After self._descr._interval_fast : self._value = 1.? real_mpfi: after __init__ qqbar.py: SSS: After self._descr._interval_fast : self._value = 0.? e-21 real_mpfi: after __init__ qqbar.py: SSS: After self._descr._interval_fast : self._value = 1.? real_mpfi: after __init__ qqbar.py: SSS: After self._descr._interval_fast : self._value = 0.? e-21 real_mpfi: after __init__ qqbar.py: SSS: After self._descr._interval_fast : self._value = -1.? real_mpfi: after __init__ rational_field.py: SSS: before crash, x = 0 base = 0 rational_field.py: SSS: after crash myretval = 0 rational_field.py: SSS: before crash, x = 1 base = 0 rational_field.py: SSS: after crash myretval = 1 rational_field.py: SSS: before crash, x = 0 base = 0 rational_field.py: SSS: after crash myretval = 0 rational_field.py: SSS: before crash, x = 1 base = 0 rational_field.py: SSS: after crash myretval = 1 real_mpfi: after __init__ rational_field.py: SSS: before crash, x = 0 base = 0 rational_field.py: SSS: after crash myretval = 0 rational_field.py: SSS: before crash, x = 1 base = 0 rational_field.py: SSS: after crash myretval = 1 rational_field.py: SSS: before crash, x = 1 base = 0 rational_field.py: SSS: after crash myretval = 1 rational_field.py: SSS: before crash, x = 1 base = 0 rational_field.py: SSS: after crash myretval = 1 real_mpfi: after __init__ qqbar.py: SSS: After self._descr._interval_fast : self._value = 0.? e-21 rational_field.py: SSS: before crash, x = -1 base = 0 rational_field.py: SSS: after crash myretval = -1 rational_field.py: SSS: before crash, x = 0 base = 0 rational_field.py: SSS: after crash myretval = 0 rational_field.py: SSS: before crash, x = 1 base = 0 rational_field.py: SSS: after crash myretval = 1 rational_field.py: SSS: before crash, x = 1 base = 0
[sage-support] Re: Porting Sage to AIX
On Oct 27, 10:42 pm, William Stein [EMAIL PROTECTED] wrote: On Mon, Oct 27, 2008 at 9:15 PM, Sameer [EMAIL PROTECTED] wrote: Hi, I am trying to port sage 3.1.1 to an IBM Power5 AIX system. After I install gap (in 32 bits), I get: So how far did you get building Sage? If GAP is the problem it sounds like you get next to the end. From the error messages above it also seems like it could be a pexpect issue. If GAP by itself starts up cleanly I would assume that the problem is in pexpect. Just out of curiosity, is this a machine you could give some (any?) of the Sage developers accounts on? We would love to officially support AIX. So far, none of us have ever been able to get access to an AIX box. +1 William Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Porting Sage to AIX
On Mon, Oct 27, 2008 at 9:15 PM, Sameer [EMAIL PROTECTED] wrote: Hi, I am trying to port sage 3.1.1 to an IBM Power5 AIX system. After I install gap (in 32 bits), I get: Just out of curiosity, is this a machine you could give some (any?) of the Sage developers accounts on? We would love to officially support AIX. So far, none of us have ever been able to get access to an AIX box. William --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
