Re-run configure+make after installing an SPKG with sage -i

[embray]

This is an idea for fixing #27373.

As explained in comment#73 on that ticket, after installing a new package it is really necessary to re-run configure after installing a new package, whether it was an optional package that was not previously installed, or a standard package that was not previously installed (due to a configure-time check determining that it was not needed).

This is to ensure that files generated by configure reflect the new system configuration, in terms of what SPKGs are installed.

Further, it is advisable to re-run make all-build in case the sage -i installed packages whose dependents need to be rebuilt.

This also needs to ensure that if an SPKG is installed for some standard package, that we account for that when re-running configure: It must not try again to check the system for that dependency, and just reflect that the SPKG is installed. For example, from #27373, if Sage is first built using GMP/MPIR from the system, then we run sage -i mpir, the system configuration must be updated to reflect that we are now using the mpir SPKG instead of GMP/MPIR from the system. It's also necessary to rebuilt any of its dependent packages.

Depends on #27641

CC: @dimpase

Component: build

Author: Erik Bray

Branch/Commit: public/build/ticket-27642 @ e168732

Reviewer: Dima Pasechnik

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

[embray]

comment:1

This branch mostly fixes the bug in #27373 for me.

As noted in the commit message this does not yet preserve arguments previously passed to configure. I think we can fix that by running ./config.status --config but I need to test that a bit more.

---

Last 10 new commits:

687cdf0	Replace various --with-gmp=$SAGE_LOCAL flags in spkg-installs with a
6de961d	Reworked this a bit more
f76d6d5	fix typo
5f90ff7	added a bit more explanation
3dee97c	correct logic for SAGE_GMP_PREFIX etc
0308142	add the AX_ABSOLUTE_HEADER macro
eea0685	iml in particular is very picky about being given an absolute path to the
6f29e86	Add support for unconditional pre- and post-check actions in spkg-configure.m4
a2bab81	Refactor the mpir/spkg-configure.m4 (and to a lesser extent the one for gmp) to use the new pre and post arguments to SAGE_SPKG_CONFIGURE
a29056a	Trac #27642: Initial attempt at fix: re-run `configure` and `make all-build` after

[embray]

Author: Erik Bray

[embray]

Commit: a29056a

[embray]

Branch: u/embray/build/ticket-27642

[dimpase]

comment:2

could you rebase it?

[dimpase]

Changed branch from u/embray/build/ticket-27642 to public/build/ticket-27642

[dimpase]

Changed commit from a29056a to 248c071

[dimpase]

New commits:

191269e	Add support for unconditional pre- and post-check actions in spkg-configure.m4
f9c9a91	Refactor the mpir/spkg-configure.m4 (and to a lesser extent the one for gmp) to use the new pre and post arguments to SAGE_SPKG_CONFIGURE
248c071	Trac #27642: Initial attempt at fix: re-run `configure` and `make all-build` after

[dimpase]

comment:4

Trying this with ./configure leaves gmp not marked as an not to be installed, while mpir is marked as not to be installed. (to be fixed on #27641).

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

191269e	Add support for unconditional pre- and post-check actions in spkg-configure.m4
1c24df1	Refactor the mpir/spkg-configure.m4 (and to a lesser extent the one for gmp) to use the new pre and post arguments to SAGE_SPKG_CONFIGURE
dc8fd7f	Refactor the mpir/spkg-configure.m4 (and to a lesser extent the one for gmp) to use the new pre and post arguments to SAGE_SPKG_CONFIGURE
4bce1a3	Trac #27642: Initial attempt at fix: re-run `configure` and `make all-build` after