From: Jari_42 <ma3jmf@gmail.com>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] [sage-on-gentoo] Sage-4.5.3 segmentation fault
Date: Fri, 26 Nov 2010 03:32:35 -0800 (PST) [thread overview]
Message-ID: <30308916.post@talk.nabble.com> (raw)
In-Reply-To: <201011110951.37839.cschwan@students.uni-mainz.de>
Hi,
Just to report that I can reproduce this exact error on my amd64 gentoo
install with Sage-4.6-r1 and python-2.6.6-r1.
Thanks,
Jari
On Thursday 11 November 2010 00:00:20 v_2e@ukr.net wrote:
> Hello!
>
> On Thu, 28 Oct 2010 11:08:28 +1300
>
> François Bissey <f.r.bissey@massey.ac.nz> wrote:
> > thanks for the debugging trace Vladimir.
> > It looks like the problem is in pynac, it may be a compatibility
> > problem with python 2.6.6. You have gone in uncharted territories
> > with this version of python. Christopher knows more about pynac
> > than me, he may be able to do something about it.
> >
> > Thanks for the report.
> >
> > Francois
>
> I just wanted to report that Sage-4.6-r1 shows exactly the same
> behaviour with python-2.6.6-r1.
>
> -----
> <v_2e@ukr.net>
--
View this message in context: http://old.nabble.com/-sage-on-gentoo--Sage-4.5.3-segmentation-fault-tp30055784p30308916.html
Sent from the gentoo-science mailing list archive at Nabble.com.
next prev parent reply other threads:[~2010-11-26 11:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 9:32 [gentoo-science] [sage-on-gentoo] Sage-4.5.3 segmentation fault v_2e
2010-10-26 9:38 ` François Bissey
2010-10-26 18:53 ` v_2e
2010-10-26 19:45 ` François Bissey
2010-10-26 20:14 ` v_2e
2010-10-27 8:07 ` Christopher Schwan
2010-10-27 21:34 ` v_2e
2010-10-27 22:08 ` François Bissey
2010-11-10 23:00 ` v_2e
2010-11-11 8:51 ` Christopher Schwan
2010-11-26 11:32 ` Jari_42 [this message]
2010-11-29 10:43 ` Christopher Schwan
2010-12-01 10:14 ` v_2e
2010-12-01 10:29 ` Christopher Schwan
2010-10-26 9:45 ` Christopher Schwan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30308916.post@talk.nabble.com \
--to=ma3jmf@gmail.com \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox