Programs/_testembed.o: $(srcdir)/Programs/_testembed.c This issue is unrelated and has been fixed. I'm not sure how g++ landed in LINKCC or MAINCC. $(LINKCC) $(PY_CORE_LDFLAGS) $(LINKFORSHARED) -o Programs/_testembed.o $(BLDLIBRARY) $(LIBS) $(MODLIBS) $(SYSLIBS) Programs/_testembed: Programs/_testembed.o $(LIBRARY) $(LDLIBRARY) $(PY3LIBRARY) > cc1plus: warning: command line option ‘-std=c99’ is valid for C/ObjC but not for C++ > cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ Indeed, there are much gcc-only options in the compilation of ` Programs/_testembed.c`, and g++ complains about them: I think in this case the error is more trivial: simply ` Programs/_testembed.c` is compiled with g++ but it should be compiled with gcc. PS: as a workaround, `-with-cxx-main=gcc-9.2.0` works, but probably it's not optimal.Īuthor: Karthikeyan Singaravelan (xtreak) * I suppose simply ` Programs/_testembed.c` is a C source file and must not be compiled with g++ usr/local/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include/stdatomic.h:40:9: error: ‘_Atomic’ does not name a type Include/internal/pycore_atomic.h:15,įrom.
Gcc-9.2.0 -pthread -c -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -flto -fuse-linker-plugin -ffat-lto-objects -flto-partition=none -g -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-function-declaration -fvisibility=hidden -fprofile-generate -I./Include/internal -I. Programs/_testembed.cĬc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++Ĭc1plus: warning: command line option ‘-std=c99’ is valid for C/ObjC but not for C++ I./Include -DPy_BUILD_CORE -o Programs/_testembed.o. G++-9.2.0 -c -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -flto -fuse-linker-plugin -ffat-lto-objects -flto-partition=none -g -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-function-declaration -fvisibility=hidden -fprofile-generate -I./Include/internal -I. configure -enable-optimizations -with-lto -with-cxx-main=g++-9.2.0 Marco Sulla, cludwig, jkloth, vstinner, xtreakĬreated on 11:37 by Marco Sulla, last changed 19:52 by pablogsal.
> I wonder how many AAA games have been released on Windows using GCC or clang with those enginesĪccording to the (quite possibly stale) official wiki, Source does not support Clang, and only supports GCC for building Linux dedicated servers.Failed to build with -with-cxx-main=g++-9.2.0 It's a reduction sure enough, but I think that's a reasonable set of engines to consider. > if you are reducing the world to just what Unreal, Source and CryEngine officially support I presume (in the absence of any real data of course) that ICC doesn't result in significant performance advantages over MSVC, for games, or it would have been worth these developer's time to support it. > I did not say that everyone was using ICC, rather that desktop and game developers did not share the same opinion regarding ICC and Visual C++ So I'm sure 9.3 will be coming along soon, though not as quickly as with some other distros.įor those interested in more about the store I found the most relevant information here when I last went looking for a way to contribute money to the project (i.e. I'm off topic here so I'll wind this up with a note that the GCC package for Slackware Current is gcc-9.2.0-i586-4.txz. Yes, 15 has been a long time coming but Patrick continues to publish updates and the Slackware Security mailing list is alive and active.
I switched to more mainstream distros at some point based on me using them at various jobs but always liked the idea of Slackware (the most BSD like Linux!).Īnd I'm posting this from a laptop running -current. But I'll admit some bias as I started my life with Linux using Slackware from a CD that came with a book about Linux, I think in 1994, maybe early 1995. It seems to be a long, drawn out affair and I'm trying to come across as neutral here as I'm sure I don't have all the information. Patrick states that after a few years and much review he was basically being ripped off by them and withdrew permission for them to continue.Īlthough helped by many volunteers Slackware is mostly a one man show and Patrick's income from the project was basically drawing down to zero. Basically, as I understand it, the store was not run by Patrick Volkerding but by a third party that agreed to share profits with him from sales of Slackware branded merchandise.
The store thing is a sad state of affairs.