From: Francois Bissey <fbissey@slingshot.co.nz>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] [sage-on-gentoo] cannot build Sage because of Sympy-0.7.1
Date: Wed, 15 Aug 2012 22:36:35 +1200 [thread overview]
Message-ID: <2462308.VzLfuT9oqk@vrooom-vrooom> (raw)
In-Reply-To: <20120815133251.68abde50e87e93534b15a888@ukr.net>
On Wed, 15 Aug 2012 13:32:51 v_2e@ukr.net wrote:
> Hello!
>
> On Wed, 15 Aug 2012 13:32:46 +1200
>
> fbissey@slingshot.co.nz wrote:
> > ...
> >
> > Actually mpmath and sympy autodetect sage at run-time. If it is
> > present they will use it. There is a variable to set off that
> > behavior in mpmath but it the mechanism is currently broken. I talked
> > to both upstream about it and hopefully
> > something will be done about it eventually.
> >
> > Technically sympy is a run time dependency of sage so you can emerge
> > it afterwards. Two solutions: skip it and come back to it later when
> > sage has been
> > merged again and hopefully whatever is currently broken (and it is
> > broken) will
> > be fixed. The other solution is to unmerge sage and emerge sympy then
> > start the
> > merge process of sage again.
>
> I tried different things including:
>
> emerge -va --nodep sage # success
> emerge -vCa sage # success
> emerge -1va sympy # success
> emerge -va sage # success
> emerge -1va sympy # fails with the same error as before
>
>
hum...... what does
printenv | grep SAGE
return?
Francois
next prev parent reply other threads:[~2012-08-15 12:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 17:49 [gentoo-science] [sage-on-gentoo] cannot build Sage because of Sympy-0.7.1 v_2e
2012-08-14 21:31 ` fbissey
2012-08-14 23:02 ` v_2e
2012-08-15 1:32 ` fbissey
2012-08-15 10:32 ` v_2e
2012-08-15 10:36 ` Francois Bissey [this message]
2012-08-15 11:35 ` v_2e
2012-08-15 22:03 ` fbissey
2012-08-16 8:05 ` v_2e
2012-08-16 9:28 ` Francois Bissey
2012-08-16 15:10 ` v_2e
2012-08-16 21:32 ` fbissey
2012-08-17 9:20 ` v_2e
2012-08-17 9:28 ` Francois Bissey
2012-08-17 10:29 ` v_2e
2012-08-17 10:39 ` Francois 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=2462308.VzLfuT9oqk@vrooom-vrooom \
--to=fbissey@slingshot.co.nz \
--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