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.
Qt5 depends on libestdc++ from ports, this has bad interactions with the
PSEUDO_FLAVORS setup (PSEUDO_FLAVORS should not change the content of
built packages). Let's go back to Qt4 as a quick fix. Reported by
nigel@ and input from sthen@, ok Rafael Sadowski (maintainer).
just set CONFIGURE_ARGS on mips64el, don't provide a way to build with
--english-only on other arch (as the only reason for using this seems to
be to work around compiler/toolchain problems). Avoids oddity with
out-of-date reported by fgsch@.
Also make sure the arch check is done after including bsd.port.arch.mk;
ARCH was in my environment when I tested before, sigh... this problem
reported by kili@.
"it's shorter than the previous version, so it's automagically ok" kili@ ;)
building support for other languages). Use it on mips64el by default
as ld(1) has trouble without it. Information from Brian Callahan and
Bryan Irvine.
- while there, prefer http MASTER_SITES
ok landry@
