Remove an outdated suggestion from the ./configure documentation
#26112
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
The documentation was worded in such a way that it suggested `./configure --prefix=~/` was valid, but we removed support for specifying paths that aren't absolute last year, to more closely match the behavior of `autoconf`. Remove the suggestion to use `~/` so that future readers don't encounter that error message (or at least don't encounter it on our suggestion). ---- Signed-off-by: Lydia Duncan <lydia-duncan@users.noreply.github.com>
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.
Resolves #26107
The documentation was worded in such a way that it suggested
./configure --prefix=~/was valid, but we removed support for specifying paths that aren't absolute last year, to more closely match the behavior ofautoconf. Remove the suggestion to use~/so that future readers don't encounter that error message (or at least don't encounter it on our suggestion).Double checked the built documentation