citnames: allow pre/postfixes to cc & c++ compiler calls #602
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 pull request modifies the regex for recognized GCC compiler calls to allow pre/postfixes to
cc
andc++
in the same manner as already implemented e.g. forgcc
(though explicitly excludingcc1
, which otherwise would also be matched). This matches e.g. the previously missingx86_64-pc-linux-gnu-cc
andx86_64-pc-linux-gnu-c++
compiler calls that are present on my system (Gentoo, sys-devel/gcc-13.2.1_p20240210).More specifically, I've encountered the issue of such compiler call being unrecognized when applying Bear to the compilation of Neomutt and using the
.configure
command as used by portage for the Neomutt ebuild (to align with target build process), which then employsx86_64-pc-linux-gnu-cc
as compiler call. While this is simply a symlink tox86_64-pc-linux-gnu-gcc
(which is recognized by Bear) and the alternative solution would of course be to modify the employed.configure
command so thatmake
uses a "different" (but actually identical) compiler call, it would make sense to me if Bear simply recognizes such compiler calls as well (not having used Bear before, it took me a bit to figure out why the generatedcompile_commands.json
was almost empty).