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-4.3.5-r1 && sage-core
Date: Sun, 18 Apr 2010 11:02:42 +0200	[thread overview]
Message-ID: <201004181102.42844.cschwan@students.uni-mainz.de> (raw)

Hi Steve,

thanks for reporting - I just pushed my latest changes which should fix the 
problem. Re-emerging sage-base should create the needed directories; sage-core 
contains your proposed patch.

Christopher

On Sunday 18 April 2010 07:32:05 Steven Trogdon wrote:
> Christopher,
> 
> The follow probably only applies to amd64. Sage will not install with the
> subject ebuilds. The
> "sage -c" during postinstall fails because the files
> 
> 	/opt/sage/local/lib/sage-flag.txt
> 	/opt/sage/local/lib/sage-current-location.txt
> 
> cannot be written since /opt/sage/local/lib doesn't exit. I suppose the
> files are needed. One can create the symlink lib -> lib64 if lib is needed
> or whatever. Even if this is fixed "sage -c" fails because the amd64-hack
> patch does't take. The spkg-install is bypassed with the sage-core ebuild.
> I tried a variety of things to get Sage to install and adding
> 
> 	append-flags -fno-strict-aliasing
> 
> to the sage-core ebuild works here. I'm not sure of the impact on ~x86 or
> ~pcc.
> 
> Steve



             reply	other threads:[~2010-04-18 10:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-18  9:02 Christopher Schwan [this message]
2010-04-18 19:10 ` [gentoo-science] sage-4.3.5-r1 && sage-core Steven Trogdon
2010-04-18 20:28   ` Christopher Schwan
2010-04-19  3:18     ` François Bissey
2010-04-19  8:52       ` Christopher Schwan
2010-04-19  9:13         ` François Bissey
2010-04-19 10:36           ` François Bissey
2010-04-19 11:04             ` Christopher Schwan
  -- strict thread matches above, loose matches on Subject: below --
2010-04-18  5:32 Steven Trogdon
2010-04-18  7:46 ` François Bissey
2010-04-18  7:51 ` François Bissey
2010-04-18  7:58 ` François Bissey
2010-04-18  8:04 ` 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=201004181102.42844.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