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
m4/nut_report_feature.m4: try to report configure invocation args #1709
m4/nut_report_feature.m4: try to report configure invocation args #1709
Conversation
…h debug enabled Related-to: networkupstools#1789
…nable-inplace-runtime mode is used
d3d42b4
to
285e006
Compare
Installed a build of this PR, so
Then re-ran just
This is a bit messy regarding For now it is deterministic and (maybe a bit too) visible about what gets applied, and just works :) On a similar note, configure values that are guessed but not specified in CLI options explicitly (e.g. python version above), may be guessed differently in a later run. Arguably feature, not a bug. Similarly for environment variables that can impact a build:
...in the former case, they are not part of CONFIG_FLAGS saved and reported.
|
With later additions, CONFIG_FLAGS with tokens that include spaces (maybe Windows paths, etc) should be handled better, e.g.:
|
…ckticks, all doublequoted outside => use $(...)
…etworkupstools#1826, networkupstools#1709] - bump libs version-info
…etworkupstools#1826, networkupstools#1709] - bump libs version-info
…ccording to older binaries found (if not provided otherwise) [networkupstools#1826, networkupstools#1709]
...and use them for
--enable-inplace-runtime
configurations in particular, to facilitate rebuilds over existing deployments.