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.
we have a perfectly serviceable distfile, with a perfectly valid licence.
just because it hasn't been touched in years is not a good enough reason
to nuke it. I have some software I haven't touched in years which still
works, and it's not as if this takes a long time in bulks
* share/apps => share/apps.kde3
* share/doc/HTML => share/doc/HTML.kde3
This is a part of KDE3/4 deconflicting work.
Build tested in a bulk by landry@, also sat over a week on ports@.
Run-time tested with some KDE3 apps, including KMail, taxipilot, yakuake...
"do it" landry@
"lib/kde3/foo" where appropirate, but also many missing desktop goo items
added, some PFRAG.shared removed and so on.
input and okay landry@ and ajacoutot@, also okay espie@
