> Hi,
>
> I encountered the following when making a fresh install of sage (~136
> packages) within a 32bit chroot. Emerge of sage terminated because of the
> following line
>
> dosym $(which gp) "${SAGE_LOCAL}"/bin/sage_pari || die
>
> in the sage-scripts ebuild. In emerging sage, sage-scripts gets pulled in
> before pari and thus the failure. I suppose it would be awkward to have
> sage-scripts depend on pari when only a symlink is created? This can be
> replicated if one has a working sage by removing pari and sage-scripts and
> either updating world or re-emerging sage-core. Here, sage-scripts gets
> pulled in before pari and the update/emerge fails.
>
Hi Steve,
I have just added a svn snapshot of pari in the overlay but not all
dependencies have been adjusted for the right slot.
How did that go? Did you get pari 2.3 or 2.4 installed?
I would imagine that if you had only pari 2.4 things failed to compile as
I have slotted it so you have to request it explicitly which happens nowhere
at the moment.
Francois
