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
>
> ---
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: 2
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 cra
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
> >
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. B
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
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
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 ac
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 G
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 lo
Hi,
I have tried building gap in both 32 bit and 64 bits. With 32 bits
I had to add a -Os optimize for size option so it would not exceed the
memory limits. With the 64 bit gap, I get:
> /site/PET/src/build/sage-3.1.1/local/bin/gap -b -p -T -o G
> /site/PET/src/build/sage-3.1.1/data//extco
11 matches
Mail list logo
