issue with why.2.33 configure's patches #1234
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
opam install why
randomly fails at configuration stage. From the diff between successful and failed runs, it seems that in the latter case, the patches ofconfigure.in
inopam.patch.in
are not present inconfigure
. It's probably due to the fact thatconfigure.Fluorine-version
(applied later) patches both files and depending on the resulting timestamps,autoconf
may considerconfigure
as newer thanconfigure.in
. Removingconfigure
before launchingautoconf
, as in the proposed patch, seems to stabilize the build.