running build_ext building '_sass' extension creating build/temp.linux-x86_64-cpython-310 clang -Wno-unused-result -Wsign-compare -DNDEBUG -pipe -march=native -fno-diagnostics-color -O2 -Werror=implicit-function-declaration -Werror=implicit-int -fPIC -DPy_LIMITED_API -I/usr/include/python3.10 -c _sass.c -o build/temp.linux-x86_64-cpython-310/_sass.o -fPIC -std=gnu++0x -Wall -Wno-parentheses -Werror=switch error: invalid argument '-std=gnu++0x' not allowed with 'C' error: command '/var/tmp/portage/dev-python/libsass-python-0.22.0/temp/clang-wrappers/clang' failed with exit code 1 * ERROR: dev-python/libsass-python-0.22.0::gentoo failed (compile phase): ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma-j4-20221114-100928 ------------------------------------------------------------------- GNUMAKEFLAGS="$GNUMAKEFLAGS --jobserver-style=pipe" GNUMAKEFLAGS="$GNUMAKEFLAGS --shuffle" CC=clang CXX=clang++ gcc-config -l: [1] x86_64-pc-linux-gnu-12 * clang/llvm (if any): clang version 15.0.4 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/15/bin Configuration file: /etc/clang/clang.cfg /usr/lib/llvm/15 15.0.4 Python 3.10.8 Available Ruby profiles: (none found) Available Rust versions: [1] rust-bin-1.65.0 * The Glorious Glasgow Haskell Compilation System, version 9.0.2 php cli (if any): HEAD of ::gentoo commit b8e2249d082e7e8a2de0486f2530ae7648594dbf Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Mon Nov 14 20:46:54 2022 +0000 2022-11-14 20:46:54 UTC emerge -qpvO dev-python/libsass-python [ebuild N ] dev-python/libsass-python-0.22.0 USE="-test" PYTHON_TARGETS="python3_10 -python3_8 -python3_9 -python3_11"
Created attachment 832709 [details] emerge-info.txt
Created attachment 832711 [details] dev-python:libsass-python-0.22.0:20221114-220613.log
Created attachment 832713 [details] emerge-history.txt
Created attachment 832715 [details] environment
Created attachment 832717 [details] etc.clang.tar.bz2
Created attachment 832719 [details] etc.portage.tar.bz2
Created attachment 832721 [details] temp.tar.bz2
Sorry about that. I've looked at the bug linked in [1] and not at the build log linked on our bug, and assumed it was fixed upstream. Andrew, could you report the bug upstream? I can't because upstream banned me for no reason (I mean, I've asked and he literally told me he doesn't know why i'm banned but he won't undo it). [1] https://bugs.gentoo.org/730244#c2
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d102abe028aad19d4f3fb10b627b7005b2e117c9 commit d102abe028aad19d4f3fb10b627b7005b2e117c9 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2022-11-15 05:50:19 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2022-11-15 05:57:49 +0000 dev-python/libsass-python: Remove insane CC opts again Bug: https://bugs.gentoo.org/881339 Signed-off-by: Michał Górny <mgorny@gentoo.org> .../{libsass-python-0.22.0.ebuild => libsass-python-0.22.0-r1.ebuild} | 3 +++ 1 file changed, 3 insertions(+)
(In reply to Michał Górny from comment #8) > Sorry about that. I've looked at the bug linked in [1] and not at the build > log linked on our bug, and assumed it was fixed upstream. > > Andrew, could you report the bug upstream? I can't because upstream banned > me for no reason (I mean, I've asked and he literally told me he doesn't > know why i'm banned but he won't undo it). > > [1] https://bugs.gentoo.org/730244#c2 They don't really seem interested in fixing the problem: "Gentoo is elevating the warning to an error, that's on them"
We're definitely not. It's Clang that's bailing out. Note that in this case, it's not *just* saying "unknown argument, treating as an error" (which Clang can do), it's actually saying "-std is valid for C but I have no idea what value you just told me to use" (because C++ happens to have a -std too). So it's not, in this case, an unknown option, but garbage passed into an argument which happens to be valid in C. But it's always invalid to pass CXXFLAGS to a C compiler anyway. For example, -Werror=odr is completely valid for C++, and means nothing for C. So, even if we were, it'd be something to fix (if minor).
