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.
Otherwise this test will generate a stack overflow, silently disabling libffi
support.
Found with -fstack-protector-strong, fixed by martynas@, thanks! Bumping
REVISION because there are already packages with strong stack protection
enabled out there.
Disable threads as it seems to trigger funky bugs. Enable it on all
archs but sparc64 as it's broken there.
Testing on arm/mips64el by kili, sparc64/ppc by me.
all secondary compilers were relocated to separate projects so we need a
rakudo port to get the perl6 binary back.
this update also addresses the recent bulk fallout noticed by naddy@
testing by sthen@ and ajacoutot@, thanks!
Parrot is a virtual machine designed with the needs of dynamically typed
languages (such as Perl and Python) in mind, and should be able to run
programs written in these languages more efficiently than VMs developed
with static languages in mind (JVM, .NET).
ok jasper@, steven@
