public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christopher Schwan <cschwan@students.uni-mainz.de>
To: <gentoo-science@lists.gentoo.org>
Subject: Re: [gentoo-science] [sage-on-gentoo] Sage-4.5.3 segmentation fault
Date: Wed, 1 Dec 2010 11:29:32 +0100	[thread overview]
Message-ID: <201012011129.32923.cschwan@students.uni-mainz.de> (raw)
In-Reply-To: <20101201121429.035c4b94.v_2e@ukr.net>

Hi,

On Wednesday 01 December 2010 11:14:29 v_2e@ukr.net wrote:
>   Hello!
>   I have migrated to Python-2.7.1 yesterday (by the way, I had to
> rename my
> '/var/lib/layman/sage-on-gentoo/dev-lang/python/python-2.7.ebuild'
> file to
> '/var/lib/layman/sage-on-gentoo/dev-lang/python/python-2.7.1.ebuild'
> since there is Python-2.7.1 in the main Portage tree already.)

Thanks for that info - I removed the 2.7 from our overlay because it isnt 
supported (not tested).

>   And Sage shows the same behaviour as before. The same segmentation
> fault.

Thats is as expected since Sage selects python to be 2.6.

> 
> 
> -----
>  <v_2e@ukr.net>



  reply	other threads:[~2010-12-01 10:30 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
2010-11-29 10:43                     ` Christopher Schwan
2010-12-01 10:14                       ` v_2e
2010-12-01 10:29                         ` Christopher Schwan [this message]
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=201012011129.32923.cschwan@students.uni-mainz.de \
    --to=cschwan@students.uni-mainz.de \
    --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