-
-
Notifications
You must be signed in to change notification settings - Fork 553
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
spkg-configure.m4 for boost and boost_cropped #29100
Comments
Dependencies: #29053 |
Changed branch from u/dimpase/packages/boostconfig.m4 to u/dimpase/packages/boostconfig |
This comment has been minimized.
This comment has been minimized.
Reviewer: Isuru Fernando |
comment:6
Works for me on Gentoo but it's a little scary to have the check for boost implicitly be the check for boost_cropped. It would be nice if the new macro result was cached -- then we could just repeat the check -- but I don't think it is. Maybe check |
comment:7
No distro I tried allowed for I guess it is a historical artefact that Sage has these two packages |
comment:8
Replying to @dimpase:
Sage needs |
comment:9
I don't know how I don't know a modern Linux distro that supplies such a "cropped" thing. |
comment:10
According to I'm almost positive the cropped version is a pure Sage invention, to cut down on size and to speed up building. |
comment:11
I think I see what happened. The sage library doesn't need boost at all, the boost spkg is optional. But the spkg-configure.m4 for boost causes it to be installed whenever a system copy is not present. Instead, I think we should leave boost alone (why is it an optional package to begin with?). The spkg-configure.m4 for boost_cropped should look for a full version of boost, like it does now. And then if someone decides to install the optional boost spkg... who cares what happens. |
comment:12
Replying to @orlitzky:
I don't understand what I am supposed to reproduce. I think an optional package only gets installed if its installation is explicitly triggered by |
comment:13
we have a number of optional and experimental packages with spkg-configure.m4 already, and nothing like this was ever reported. |
comment:14
Ok, I'm going to put it back to positive review then. I'm not willing to delete boost at the moment to see what happens. The check for boost_cropped now looks even more correct to me, since that's the standard package. My comment about boost's spkg-configure.m4 no longer applies, it isn't standard and doesn't need to be detected. |
comment:15
Sorry, false alarm: I tested with some other packages. If I uninstall the optional gp2c, for example...
That sure looks like gp2c will be installed from the spkg. That message combined with John's comment made me think for a minute that a full copy of boost was being installed in addition to (or in lieu of) boost_cropped. |
comment:16
#28788 addresses improving the printing of this message. |
comment:17
Yikes, that ax_boost_base.m4 is scary. I hope I never have to debug anything in it. But if it works it works, and I imagine (?) it's well tested. |
Changed branch from u/dimpase/packages/boostconfig to |
we use a macro from autoconf archive to test the version
Depends on #29053
CC: @mkoeppe @isuruf @embray @orlitzky
Component: build: configure
Author: Dima Pasechnik
Branch/Commit:
6f04521
Reviewer: Isuru Fernando
Issue created by migration from https://trac.sagemath.org/ticket/29100
The text was updated successfully, but these errors were encountered: