some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
${LOCALBASE}/mkspecs (ugh)
This port should really be merged with qca-qt5 and qt4/qt5 should be a
FLAVOR of it.. or at least this port should use the qt4 MODULE :)
- Merge security/{qca-ossl,qca-gnupg,qca2} into qca
to solve the update process (hint from sthen@ thanks)
- Disable SSL2 and SSL3 by default!
- Many useful tweaks and advice from landry@. Many thanks!
This patch includes the last BUILD_PACKAGES:M* block tweak
from landry@
OK sthen@
* renaming libqca to libqca2 for the qca2 port
* removed conflict line from qca2 PLIST
* bumped qca2
* updated conflict line in qca PLIST
* bumped qca2
* updated WANTLIB of qca-ossl and bumped
* hooked qca2 up to the build in the ports/security/Makefile
OK shadchin@, espie@
