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.
upstream patch provided by ruby-core for ruby 2.4.
No CVE numbers, but this fixes the following vulnerabilities:
* Fix a DNS request hijacking vulnerability.
* Fix an ANSI escape sequence vulnerability.
* Fix a DOS vulernerability in the query command.
* Fix a vulnerability in the gem installer that allowed a malicious
gem to overwrite arbitrary files.
pollution diff is in.
lang/squeak/vm does not build but it's due to the recent audio changes
games/xbattle: also fixes some conflicting implicit decl
print/hplip: also fixes some conflicting implicit decl
Stop overriding the internal jnr-posix implementation, as the patches
in our copy have been merged upstream. This also means we can drop the
zip/unzip BDEPs.
OK jasper@
Work around upstream regression causing rake/rdoc/ri to not work by
copying the real executables over the rubygems shims.
Fix the #! lines on the executables.
The old ant based tests no longer work, and the new maven tests
require downloading tons of packages at runtime, so punt and mark
NO_TEST=Yes and stop downloading the -src tarball.
system that downloads 190+ .jar files at build time. Switch to using
the binary distribution, since there is no point compiling java source
code to java bytecode when we can use the precompiled java bytecode.
Use our custom jnr-posix distfile with 64-bit time_t support by
directly patching jruby.jar.
Add jruby-launcher gem as a separate distfile, but since we only need
the binary, compile it manually and don't install the gem.
Still keep the src distfile for the tests, because the binary distfile
doesn't include them.
Add patch to work around rubygems regression with .files in the root
of the gem not getting installed (already accepted upstream).
without any modifications to PATH. To run an ruby program that is
installed in jruby's bin directory (which no longer needs to be in the
PATH), use jruby -S program.
The spec task requires network access via git, which is not allowed.
Since git isn't needed anymore for regress, remove it from
REGRESS_DEPENDS. The spec task is just commented out in case somone
wants to run it manually.
Set JAVA_HOME and PATH and disable forking so java doesn't crash when
running the test and spec tasks. Don't install the jruby-launcher gem
when running the test and spec tasks, as it fails.
Regress depend on git when running the specs, as it needs to download
current rubyspecs for the spec task.
Delete the jruby-complete.jar file and just use the jruby.jar file
when running the specs, as otherwise you get additional test failures
and warnings.
Switch to SUBST_CMD while here now that has been fixed. Also, bump
the memory limits by 50M as 384M doesn't seem to be enough in all
cases.
