oofcanvas @1.0.2: cc1plus: error: unrecognized command line option "-std=c++11"

[ryandesign (Ryan Carsten Schmidt)]

​https://build.macports.org/builders/ports-10.7_x86_64-builder/builds/154269/steps/install-port/logs/stdio

--->  Building oofcanvas
DEBUG: Executing proc-pre-org.macports.build-build-0
DEBUG: Executing org.macports.build (oofcanvas)
DEBUG: Environment: 
CC='/opt/local/bin/clang-mp-15'
CC_PRINT_OPTIONS='YES'
CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_graphics_oofcanvas/oofcanvas/work/.CC_PRINT_OPTIONS'
CFLAGS='-arch x86_64 -isysroot/'
CPATH='/opt/local/include'
CXX='/opt/local/bin/clang++-mp-15'
CXXFLAGS='-arch x86_64 -stdlib=libc++ -isysroot/'

Finding dependencies for C++ files.
cc1plus: error: unrecognized command line option "-std=c++11"
Command failed, no output: g++ -std=c++11 -MM -MG -MT ./oofcanvas/oofcanvasgui/guicanvas.o -Ioofcanvas -Ibuild/temp.macosx-10.7-x86_64-2.7 -Ibuild/temp.macosx-10.7-x86_64-2.7/oofcanvas ./oofcanvas/oofcanvasgui/guicanvas.C
Command failed:  cd "/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_graphics_oofcanvas/oofcanvas/work/oofcanvas-1.0.2" && /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 setup.py --no-user-cfg build --pythonAPI --magick 
Exit code: 1

It's not UsingTheRightCompiler. MacPorts wants it to use clang++-mp-15, but it's using g++ instead.

[snarkhunter (Steve Langer)]

Why would this be cropping up now? Did the default compiler change? oofcanvas uses distutils to choose the compiler, but adds some options manually.

The next version of oofcanvas will use cmake instead of distutils, and will be released within a few days. The new version will not have this particular problem. It will take me a little while to get the portfile updated because I have not much experience with cmake and no experience using cmake in a portfile. In any case I don't think it will be practical to fix this issue now.

-- Steve

[ryandesign (Ryan Carsten Schmidt)]

Thanks, it looks like 1.1.1, using cmake, is using the right compiler and has built successfully everywhere.