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: Fri, 17 Aug 2012 22:39:24 +1200 [thread overview]
Message-ID: <2323265.iCCqBSj8HU@vrooom-vrooom> (raw)
In-Reply-To: <20120817132914.4925ced9651cbafa8ac3fa8b@ukr.net>
On Fri, 17 Aug 2012 13:29:14 v_2e@ukr.net wrote:
> On Fri, 17 Aug 2012 21:28:09 +1200
>
> Francois Bissey <fbissey@slingshot.co.nz> wrote:
> > Best solution: rebuild mpmath without the gmp useflag and remove gmpy.
> > Rebuilding is not enough as the flag only insure that gmpy is
> > installed. mpmath autodetect gmpy's presence all by itself if it is
> > present - gmp flag or not.
>
> I did as you suggested and now I can 'import mpmath' and 'import
> sympy' in the Python2 shell without any errors.
> Maybe it is worth masking this 'gmp' USE-flag if Sage is being
> emerged? Or is it impossible?
>
gmpy is the real culprit. You can have it independently of the useflag.
We can put something in the package.use we provide in the overlay.
We could ship a package.mask file as well.
I am setting MPMATH_NOGMPY in sage-env in sage-5.3 so there
won't be problems from sage.
Francois
prev parent reply other threads:[~2012-08-17 12:08 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
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 [this message]
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=2323265.iCCqBSj8HU@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