Quoting [email protected]:
Hello!
On Wed, 15 Aug 2012 09:31:12 +1200
[email protected] wrote:
Quoting [email protected]:
> Hello!
> I've noticed that 'lcalc' is available again and tried to emerge
> Sage. This time it failed because of 'dev-python/sympy-0.7.1'. It
> refuses to be built and gives the following error:
>
> . . .
>
Hi Vladimir,
I cannot reproduce that. Which version of sage do you have currently
installed and was any component updated recently (mpmath,mpfr,gmp?).
Well, actually I lost my "/var" partition several days ago, so now I'm
re-emerging everything although I have already got this "everything" on
the "/usr" partition.
So when I run 'emerge sage', it pulls 'dev-python/sympy-0.7.1' as a
dependency. That is why I'm not sure I can understand why the SymPy
build log mentions Sage at all. How can it know about Sage if Sage is
intended to be merged *after* sympy?
I'm trying to emerge Sage 5.2-r2, and I have Sage-5.2 (I don't
remember exactly whether it was '-r2' or '-r1' though) installed on my
system.
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.
Francois
