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: [gentoo-science] [sage-on-gentoo] random SIGABRT errors on amd64
Date: Sun, 30 May 2010 14:22:59 +0200	[thread overview]
Message-ID: <201005301422.59910.cschwan@students.uni-mainz.de> (raw)

Hi,

good news: this bug is now fixed - install polybori-0.6.4-r1 and re-emerge 
sage-4.4.2.

The problem was indeed polybori as suggested by Paulo. The "fix" I have written 
removes polybori's shared objects to enforce static linkage which seems to fix 
the problem. If you want to read more on this bug, read 
http://trac.sagemath.org/sage_trac/ticket/8192 and 
http://trac.sagemath.org/sage_trac/ticket/2822 .

Christopher



             reply	other threads:[~2010-05-30 12:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-30 12:22 Christopher Schwan [this message]
2010-05-30 15:39 ` [gentoo-science] [sage-on-gentoo] random SIGABRT errors on amd64 Christopher Schwan
2010-05-30 22:20   ` François Bissey

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=201005301422.59910.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