From: Steven Trogdon <strogdon@d.umn.edu>
To: gentoo-science@lists.gentoo.org
Subject: [gentoo-science] sage-4.3.5-r1 && sage-core
Date: Sun, 18 Apr 2010 00:32:05 -0500 [thread overview]
Message-ID: <1271568736.17226.0@pavilion64> (raw)
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
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
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-04-18 6:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 5:32 Steven Trogdon [this message]
2010-04-18 7:46 ` [gentoo-science] sage-4.3.5-r1 && sage-core 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
-- strict thread matches above, loose matches on Subject: below --
2010-04-18 9:02 Christopher Schwan
2010-04-18 19:10 ` 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
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=1271568736.17226.0@pavilion64 \
--to=strogdon@d.umn.edu \
--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