Avoid passing a "\n" argument to configure
#122
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.
(This is mainly to get feedback from the CI, I am not claiming this is a proper fix.)
When configuring at toplevel with
--enable-middle-end=flambda2
, the file withthe options for stage 0 (namely
configure_opts_stage0
) contains a "\n" stringwhich is then passed to
configure
. This leads (at least on macOS) to a failureof the configure call. If there are leftovers from a previous successful build, stage 0
will "inherit" the configuration, leading to an inconsistent state (e.g. the
Config
module will report it is an flambda2 build, even though the subtree does not even
contain the sources for flambda2).