Issue Configure option --with-cxx-main=/usr/bin/clang++ not working #93744

mikecm · June 21, 2022, 9:22am

I believe this was closed inappropriately. Can it be reopened?

vbrozik · June 21, 2022, 9:34am

Why do you require people interested in your message to search for the information? Why do not you post the link?

github.com/python/cpython

Configure option --with-cxx-main=/usr/bin/clang++ not working

opened 11:16AM - 12 Jun 22 UTC

closed 09:20AM - 19 Jun 22 UTC

MaxwellDupre

type-bug

**Configure option --with-cxx-main=/usr/bin/clang++ not working** **My enviro…nment** - CPython versions tested on: Latest 3.12.0.a0 tried on other but CC=/usr/bin/clang not working on those, so pointless to try - Operating system and architecture: fedora 5.17.13-300.fc36.x86_64 Configure options --with-cxx-main=/usr/bin/clang++ CC=/usr/bin/clang runs and gives at end: `configure: creating Modules/Setup.local` `configure: creating Makefile` `configure:` Then: `make` /usr/bin/clang++ -c -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -std=c11 -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -Wstrict-prototypes -Werror=implicit-function-declaration -fvisibility=hidden -I./Include/internal -I. -I./Include -DPy_BUILD_CORE -o Programs/python.o ./Programs/python.c clang-14: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated [-Wdeprecated] error: invalid argument '-std=c11' not allowed with 'C++' make: *** [Makefile:1373: Programs/python.o] Error 1 See [Discuss](https://discuss.python.org/t/compiling-python-with-clang/16323/4) report Tried configure with --with-cxx-main=/usr/bin/g++ CC=/usr/bin/gcc then `make` cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ cc1plus: warning: command-line option ‘-std=c11’ is valid for C/ObjC but not for C++ Shows source files being compiled and linked and actually builds python executable, so this **works**.

You should also add some explanation why do you think “this was closed inappropriately”.

tiran · June 21, 2022, 9:47am

I can reproduce the problem and have reopened the issue.

Your tone seems a bit harsh to me. We value a welcoming and friendly communication style. The ticket contains sufficient information and a simple reproducer. There was no need to provide more information.

vbrozik · June 21, 2022, 10:02am

I am sorry if my message sounded harsh. It certainly was not meant unfriendly. I will try to phrase similar messages differently next time.

Maybe in workflows of some people the issue number alone is OK but other people are not even sure if it is a CPython issue number. URL is probably the most accessible way to point to an issue.