Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In MPFR, don't delete old libraries #12548

Closed
jdemeyer opened this issue Feb 20, 2012 · 10 comments
Closed

In MPFR, don't delete old libraries #12548

jdemeyer opened this issue Feb 20, 2012 · 10 comments

Comments

@jdemeyer
Copy link

libmpfr (and libmpfr and libmpc, #12515) are run-time dependencies of gcc (#12369). These therefore become build-time dependencies of Sage. When these libraries are deleted during installation of mpfr, gcc stops working, causing build failures in parallel builds.

Since there is no clear reason why the old libraries should be deleted, we simply don't delete them. The mpir spkg-install already doesn't delete libraries and mpc will be fixed in #12515.

spkg: http://boxen.math.washington.edu/home/jdemeyer/spkg/mpfr-2.4.2.p2.spkg

CC: @jpflori

Component: packages: standard

Author: Jeroen Demeyer

Reviewer: John Palmieri

Merged: sage-5.0.beta6

Issue created by migration from https://trac.sagemath.org/ticket/12548

@jdemeyer

This comment has been minimized.

@jdemeyer
Copy link
Author

Author: Jeroen Demeyer

@jdemeyer
Copy link
Author

Diff for the mpfr spkg, for review only

@jdemeyer
Copy link
Author

comment:2

Attachment: mpfr-2.4.2.p2.diff.gz

@jdemeyer

This comment has been minimized.

@jdemeyer jdemeyer changed the title In MPIR and MPFR, don't delete old libraries In MPFR, don't delete old libraries Feb 20, 2012
@jhpalmieri
Copy link
Member

comment:4

Looks good to me. Why even delete the headers?

@jhpalmieri
Copy link
Member

Reviewer: John Palmieri

@jpflori
Copy link

jpflori commented Feb 24, 2012

comment:5

Isn't the point of deleting the old librairies to not have tons of old librairies inside lib/ if Sage keeps on getting updated?

You might argue that it's not a big deal, because Sage is already so big, but...

And wasn't #12366 sufficient for building gcc?

@jdemeyer
Copy link
Author

comment:7

Replying to @jpflori:

Isn't the point of deleting the old librairies to not have tons of old librairies inside lib/ if Sage keeps on getting updated?

Probably. But this wouldn't work here, as deleting the old mpir/mpfr/mpc libraries would mean that gcc stops working. There are work-arounds, but they would make the build/upgrade process a lot more complicated.

And wasn't #12366 sufficient for building gcc?

For serial builds, #12366 is sufficient. The problem with parallel builds is that there is a cerain time between the deleting of the old mpfr libraries and the installation of the new mpfr libraries. During that time, a gcc in a parallel build wouldn't work anymore.

@jdemeyer
Copy link
Author

Merged: sage-5.0.beta6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants