On Jan 5, 11:03 am, "William Stein" wrote:
> On Mon, Jan 5, 2009 at 10:46 AM, mabshoff wrote:
> > Yes, that trick was my first idea.
>
> Wait a minute. Just for the record I just tested my OpenSuse 32-bit
> build of sage with libreadline.so* deleted, and Python, Gap, and PARI
> all *do* ge
On Mon, Jan 5, 2009 at 11:03 AM, William Stein wrote:
> On Mon, Jan 5, 2009 at 10:46 AM, mabshoff wrote:
>>
>>
>>
>> On Jan 4, 10:58 pm, "William Stein" wrote:
>>> On Sun, Jan 4, 2009 at 10:52 PM, mabshoff wrote:
>>
>>
>>
>>> >> I.e., for Sage we build only the static readline. Can't Python,
On Mon, Jan 5, 2009 at 10:46 AM, mabshoff wrote:
>
>
>
> On Jan 4, 10:58 pm, "William Stein" wrote:
>> On Sun, Jan 4, 2009 at 10:52 PM, mabshoff wrote:
>
>
>
>> >> I.e., for Sage we build only the static readline. Can't Python, Gap,
>> >> PARI, etc. just link in a static readline?
>>
>> > Wel
On Mon, Jan 5, 2009 at 10:46 AM, mabshoff wrote:
>
>
>
> On Jan 4, 10:58 pm, "William Stein" wrote:
>> On Sun, Jan 4, 2009 at 10:52 PM, mabshoff wrote:
>
>
>
>> >> I.e., for Sage we build only the static readline. Can't Python, Gap,
>> >> PARI, etc. just link in a static readline?
>>
>> > Wel
On Jan 5, 10:46 am, mabshoff wrote:
> On Jan 4, 10:58 pm, "William Stein" wrote:
> > Well, my question is first: does this work?
>
> I would prefer to solve it another way, but it would work.
Oops, right after pressing "send" I realized why this might be a bad
idea: Installing readline-dev
On Jan 4, 10:58 pm, "William Stein" wrote:
> On Sun, Jan 4, 2009 at 10:52 PM, mabshoff wrote:
> >> I.e., for Sage we build only the static readline. Can't Python, Gap,
> >> PARI, etc. just link in a static readline?
>
> > Well, I tried that and I ended up with a Python without readline
> >
On Sun, Jan 4, 2009 at 10:52 PM, mabshoff wrote:
>
>
>
> On Jan 4, 10:39 pm, "William Stein" wrote:
>> On Sun, Jan 4, 2009 at 9:24 PM, mabshoff wrote:
>
>
>
>> What about if we just don't install a shared readline at all? That
>> seems way safer to me than overwriting it with the system readl
On Jan 4, 10:39 pm, "William Stein" wrote:
> On Sun, Jan 4, 2009 at 9:24 PM, mabshoff wrote:
> What about if we just don't install a shared readline at all? That
> seems way safer to me than overwriting it with the system readline.
> In the spkg-install for readline, if the OS is OpenSuse,
On Sun, Jan 4, 2009 at 9:24 PM, mabshoff wrote:
>
>
>
> On Jan 4, 9:15 pm, "William Stein" wrote:
>> On Sun, Jan 4, 2009 at 9:01 PM, William Stein wrote:
>
>
>
>> OK, I found a temporary workaround. See the patch at #4934.
>
> Ok, I will take a look.
>
>> It would also be very nice if we coul
On Jan 4, 9:15 pm, "William Stein" wrote:
> On Sun, Jan 4, 2009 at 9:01 PM, William Stein wrote:
> OK, I found a temporary workaround. See the patch at #4934.
Ok, I will take a look.
> It would also be very nice if we could also fix the openSUSE build
> bug, since I think you said you kn
On Sun, Jan 4, 2009 at 9:17 PM, mabshoff wrote:
> Cool. The dirty fix is to disable that doctest for now. If I ran the
That is very dirty indeed. I think I prefer at least the hack I've
posted to the ticket, which is to make the variable public.
> last doctest by itself it passed, running the
On Jan 4, 9:01 pm, "William Stein" wrote:
> On Fri, Jan 2, 2009 at 11:32 PM, mabshoff wrote:
> Your ticket #4934 segfault:
>
> http://trac.sagemath.org/sage_trac/ticket/4934
>
> which you were just seeing on cicero is popping up for me on several test
> os's on several compilers.
O
On Sun, Jan 4, 2009 at 9:01 PM, William Stein wrote:
> On Fri, Jan 2, 2009 at 11:32 PM, mabshoff wrote:
>>
>> Hello folks,
>>
>> Sage 3.2.3.final is out, 3.2.3.rc0 was never announced on the list.
>> Well, technically the following happened: the first final had some
>> issues, so it was renamed
On Fri, Jan 2, 2009 at 11:32 PM, mabshoff wrote:
>
> Hello folks,
>
> Sage 3.2.3.final is out, 3.2.3.rc0 was never announced on the list.
> Well, technically the following happened: the first final had some
> issues, so it was renamed rc0 and a new final was spun with a number
> of fixes.
>
> Mos
On Sun, Jan 4, 2009 at 6:35 PM, mabshoff wrote:
>
>
>
> On Jan 4, 6:21 pm, "William Stein" wrote:
>> On Sun, Jan 4, 2009 at 5:38 PM, Justin C. Walker wrote:
>
> Hi,
>
>
>
>> I built on a CentOS 64-bit system with 1GB RAM, and a test in arith.py
>> fails due to swapping leading to a timeout. T
On Jan 4, 6:21 pm, "William Stein" wrote:
> On Sun, Jan 4, 2009 at 5:38 PM, Justin C. Walker wrote:
Hi,
> I built on a CentOS 64-bit system with 1GB RAM, and a test in arith.py
> fails due to swapping leading to a timeout. The test in question is a
> *massive* performance regression, I th
On Sun, Jan 4, 2009 at 5:38 PM, Justin C. Walker wrote:
>
>
> On Jan 2, 2009, at 23:32 , mabshoff wrote:
>
>>
>> Hello folks,
>>
>> Sage 3.2.3.final is out, 3.2.3.rc0 was never announced on the list.
>> Well, technically the following happened: the first final had some
>> issues, so it was rename
On Jan 2, 2009, at 23:32 , mabshoff wrote:
>
> Hello folks,
>
> Sage 3.2.3.final is out, 3.2.3.rc0 was never announced on the list.
> Well, technically the following happened: the first final had some
> issues, so it was renamed rc0 and a new final was spun with a number
> of fixes.
>
> Most of
All tests passed on my 10.4 ppc (g4) mac laptop, except for
calculus.py timing out as usual.
-M. Hampton
On Jan 3, 1:32 am, mabshoff wrote:
> Hello folks,
>
> Sage 3.2.3.final is out, 3.2.3.rc0 was never announced on the list.
> Well, technically the following happened: the first final had some
2009/1/3 John Cremona :
> Built fine and all tests pass on my 32-bit ubuntu laptop. In
And also on a 64-bit Suse
Linux version 2.6.18.8-0.3-default (ge...@buildhost) (gcc version
4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP Tue Apr 17 08:42:35
UTC 2007
John
> particular, Atlas built fine a
On 3 Jan., 17:56, mabshoff wrote:
> On Jan 3, 5:47 am, "Georg S. Weber"
> wrote:
>
> Hi,
>
> > Hi, I've got a crash report, which might be a blocker for 3.2.3:
>
> Nope, this is not an issue with 3.2.3, but 3.2.2. And this was done on
> purpose to catch exactly this issue since it has slipped
Built fine and all tests pass on my 32-bit ubuntu laptop. In
particular, Atlas built fine and quickly for the first time ever on
this machine (at least, once I realized that setting SAGE_ATLAS_LIB to
the empty string was not the same as unsetting it).
John
2009/1/3 mabshoff :
>
>
>
> On Jan 3,
On Jan 3, 6:14 am, Jaap Spies wrote:
> On Fedora 9, 32 bits:
> --
> All tests passed!
>
> Jaap
Thanks Jaap, this is pretty much what was expected.
Cheers,
Michael
--~--~-~--~~~---~--~~
To
On Jan 3, 5:47 am, "Georg S. Weber"
wrote:
Hi,
> Hi, I've got a crash report, which might be a blocker for 3.2.3:
Nope, this is not an issue with 3.2.3, but 3.2.2. And this was done on
purpose to catch exactly this issue since it has slipped by us in
releases twice already.
> In the course
mabshoff wrote:
> Hello folks,
>
> Sage 3.2.3.final is out, 3.2.3.rc0 was never announced on the list.
[...]
>
> You can download the sources from
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.3/
>
> or upgrade to this release via
>
> ./sage -upgrade
> http://sage.
Hi, I've got a crash report, which might be a blocker for 3.2.3:
In the course of building and installing 3.2.3.final, an empty file "/
Users/georgweber/.sage/init.sage" was created (I remember having seen
the corresponding output line).
Now trying to start (the older version) Sage 3.2.2, IPytho
Hi,
sorry for the Off-Topic "BTW" question, I moved it to the correct
thread.
Cheers,
gsw
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
On 3 Jan., 08:32, mabshoff wrote:
> Hello folks,
>
> Sage 3.2.3.final is out, 3.2.3.rc0 was never announced on the list.
Hi Michael,
I had found, downloaded, build and (long-)tested the 3.2.3.rc0 when it
was still named "final".
Already rock-stable on MacBook Intel Core2Duo with Mac OS X 10.4
28 matches
Mail list logo
