-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support compiler names with spaces #801
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In some cases, especially when using autotools, the value of
CC
orCXX
may have spaces in it. For example, in my projectCXX
is detected asg++ -std=c++17
. Should the-std=c++17
part really be inCXXFLAGS
? Absolutely, but autotools isn't going to make that easy. Other examples arempicc -cc=clang
(MPICH) or if using an absolute path with spaces.configure
doesn't seem to handle this gracefully and just takes the first word, e.g. truncatingg++ -std=c++17
tog++
. The correct value (with spaces) is echoed correctly byselect_tool_w_env
. Rather, the problem seems to be the fact thatselect_tool
expects a space-separated list of binaries to check for, rather than a single possibly whitespace-containing name.The text was updated successfully, but these errors were encountered: