http://build-failures.rhaalovely.net/amd64/2018-10-25/security/xca.log
security/xca breaks because it uses "cc" to link C++ code. It also
uses "cc" to compile C++ code, but the compiler switches to C++
mode. The link command does not.
xca's build framework uses the CC variable to hold the name of the
compiler. configure correctly sets this to CC=c++.
Enter qt5.port.mk:
MAKE_FLAGS += ${_MODQT5_SETUP}
...
# useful?
_MODQT5_SETUP += CC=${CC} CXX=${CXX}
This forces CC=cc into the build and breaks it.
Do we really need this forceful override in all ports that use Qt5?
There is no equivalent in qt4.port.mk.
We can work around it in the xca port, but working around a workaround
in the ports infrastructure feels silly.
--
Christian "naddy" Weisgerber na...@mips.inka.de
