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
/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
?
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
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
am doing the same under AIX, but I can't seem to get
rid of this. I am still using sage -br to incrementally add packages.
Thanks!
- Sameer
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group
should I
proceed?
Thanks,
- 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
fault.
0x100d3854d932 in ?? ()
(gdb) where
#0 0x100d3854d932 in ?? ()
#1 0x100d47e8 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)
How should I proceed?
Thanks!
- Sameer
On Mar 8, 1:00 pm, William Stein [EMAIL PROTECTED] wrote:
On Sat
dcost.o
-rw-r--r-- 1 sameer utk 2196 2008-03-06 18:37 dcost.o
scipy-20071020-0.6.p3/src file dcost.o
dcost.o: ELF 32-bit MSB relocatable, PowerPC or cisco 4500, version 1
(SYSV), not stripped
So, what command invokes this compilation that gives the error? If I
just try the spkg-install command
this.
Thanks for your help!
- Sameer
On Mar 4, 10:20 pm, Michael.Abshoff [EMAIL PROTECTED]
wrote:
Sameer wrote:
Hi,
When I try to compile Sage 2.10.2 under ppc64 Linux using gcc,
I see that some files are
compiled in 32 bits and some others in 64 bits. Have you noticed
-2.10.2/local/bin/sage-sage: line 212:
13965 Segmentation fault sage-ipython -c $SAGE_STARTUP_COMMAND;
$@
build/sage-2.10.2
Thanks,
- Sameer
On Mar 5, 2:42 pm, William Stein [EMAIL PROTECTED] wrote:
On Wed, Mar 5, 2008 at 1:45 PM, Sameer [EMAIL PROTECTED] wrote:
Hi Michael
10 matches
Mail list logo
