4.4: Sync configure and test setup with bash-5.2 #35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jansorg
force-pushed
the
jansorg/4.4/unit-test-setup
branch
from
13c3743 to
74bc114
Compare
jansorg
force-pushed
the
jansorg/4.4/unit-test-setup
branch
from
74bc114 to
2c61c56
Compare
jansorg
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 sync the unit test setup with the bash 5.2 branch to make the output nicer and easier to read.
I've also synced some more of the configure changes and also updated ltmain.sh to the version generated on my local machine (i.e. based on the current autotools(?) stack). But I don't know much about the autotools anymore...
There was a static path in
test-cmd-info-variables.sh, which is now fixed to make the tests pass.I don't know why tests were not failing before this PR, but apparently the unit tests were not executed.