Detect gcc even if compiler binary is symlinked #56
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.
Sometimes the compiler identification (the only part that
configure
currently uses to detect the vendor) is derived from the running executable name (argv[0]
):Following the symlinks until an actual binary could be an option, but then we would need to only do this for vendor identification, and use the original symlink for actual compilation. And that's because certain vendors (e.g. Apple, HPE Cray) depend on the symlink being used, and don't allow / won't work properly if the underlying executable is used.
This change sidesteps this whole issue (at least for gcc), by looking for the string "Free Software Foundation", which should be unique among compiler version messages.