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.
account) and add a dumb build fix with --std=c++03 on clang arches.
upstream has much newer branches (e.g. 1.9.1 released yesterday, 2.0.0
released a few months ago) but too much churn for a quick fix, and at
least they'll now be on the portroach radar.
in ports. So add a BUILD_DEPENDS on devel/cryptopp:patch and symlink it
into the build so we get all the patches of our ports version. Also drops
the BUILD_DEPENDS on archivers/unzip.
Bump REVISION.
Still does not fix the build error on i386 though...
Suggested by and ok sthen@
connected, this was introduced with the xcb fix and would result in
the server eating 100% cpu while waiting for clients
bump PKGNAME
ok dim@ (maintainer)
caused multi-second pauses for each event rendering it useless,
due to queueing in xcb buffers not triggering X file descriptor
changes.
Patch from http://bugs.gentoo.org/show_bug.cgi?id=257794
OK & hint in the right direction from maintainer dim@ :)
