Opened 2 years ago
Last modified 11 months ago
#29498 new enhancement
Do not check for system packages of disabled optional packages
| Reported by: | mkoeppe | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | sage-wishlist |
| Component: | build: configure | Keywords: | configure, optional packages |
| Cc: | mjo, dimpase, slelievre | Merged in: | |
| Authors: | Reviewers: | ||
| Report Upstream: | N/A | Work issues: | |
| Branch: | Commit: | ||
| Dependencies: | Stopgaps: |
Status badges
Description (last modified by )
Related: is there some way to detect if --enable-gp2c was passed? We shouldn't have to run this code at all, by default.
Unfortunately, although (after a recent change) the SAGE_SPKG_ENABLE calls are emitted in m4/sage_spkg_configures.m4 before the SAGE_SPKG_CONFIGURE_* calls, the shell code that sets the "enable" variables still ends up after the shell code from the SAGE_SPKG_CONFIGURE_* (because of autoconf reordering magic).
We would have to move the SAGE_SPKG_ENABLE calls even earlier, i.e., before the m4_sincludes of the spkg-configure.m4.
Related:
Change History (7)
comment:1 Changed 2 years ago by
- Milestone changed from sage-9.1 to sage-9.2
comment:2 Changed 2 years ago by
- Description modified (diff)
comment:3 Changed 21 months ago by
- Milestone changed from sage-9.2 to sage-9.3
comment:4 Changed 18 months ago by
- Cc slelievre added
- Description modified (diff)
- Keywords configure optional packages added
comment:5 Changed 18 months ago by
- Description modified (diff)
comment:6 Changed 16 months ago by
- Milestone changed from sage-9.3 to sage-9.4
Setting new milestone based on a cursory review of ticket status, priority, and last modification date.
comment:7 Changed 11 months ago by
- Milestone changed from sage-9.4 to sage-wishlist
Note: See
TracTickets for help on using
tickets.
pushing these forward to 9.2