On Jan 14, 6:17 pm, "Luis Finotti" <[EMAIL PROTECTED]> wrote:
> Dear Michael,
>
> On Jan 14, 2008 11:58 AM, mabshoff
>
> <[EMAIL PROTECTED]> wrote:
>
> (...)
>
> > > But, so far, I haven't had any problems while running my old stuff...
>
> > The doctest that fails communicates with another Sage instance. I have
> > seen this fail on occasion with systems with low memory. Since your
> > gcc is tuned for "i486-linux-gnu" could you enlighten us how much
> > memory your system has available? Maybe "i486-linux-gnu" is the
> > default gcc build target on Debian - I no longer have access to a 32
> > bit Debian box.
Hi Luis,
> It has 1Gb... Is that already considered "low memory"?
I wouldn't think so, the problem happened with 256 MB or so. What
might be an issue is something else (i.e. the tp_new issue), which
seems to be finally fixed upstream in python. Please report if the
problem persists in the the next release. Unless I can come up with a
reproducible test case on my end I am reluctant to open a ticket. If
anybody else can reproduce this please speak up.
> :-) As I
> said, so far it hasn't given me any trouble, although I use Sage at
> home less than at work. About gcc, I don't know much about it at all.
> I just did "apt-get install gcc" or something like that...
ok, somebody else might know this hopefully.
> Thanks!
>
> Luis
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
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://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---
