Most patch merges inspired from patrick's work on base-clang. Consumer
ports fixed/marked BROKEN as discussed with bcallah@ and rsadowski@.
powerpc tests and PLIST fixes from cwen@, thanks! rust-1.36 tests by
semarie@
It also drops libclazylib.so, but that one isn't used by the ports tree.
There is something fishy with libClazyPlugin.so (renamed from
libClangLazy.so) which is directly used as a shared lib by
bin/clazy-standalone.
ok rsadowski@ (maintainer)
there may be some missing as my unpacked ports source is a little out of date
but this should catch the main things people might run into
the struct was reordered a second time in sysctl.h r1.192 to improve
compatibility but amd64 snapshot packages made it out before that happened
so the bumps are still needed
for some reason password_hash requires libargon2 even though php has
access to the argon2 functions from libsodium. prompted by a mail
from Heiko Zimmermann.
(also note, there is a separate sodium_crypto_pwhash_str function
which was already available and doesn't depend on libargon2)
Changes in thread internals between ruby 2.5 and 2.6 resulted in
ruby processes not waking up when receiving some signals. Fix
this by backporting an upstream patch. Remove three patches to
the tests that skipped tests. Two of these issues were fixed by
this upstream patch, and the other was fixed by the pthread fifo
fdlock fix.
Follow the upstream recommendations for packagers and switch to
multi-packages:
devel/gettext -> devel/gettext,-runtime
devel/gettext-tools -> devel/gettext,-tools
(new) devel/gettext,-textstyle
the command line. This resulted in shared libraries with an .interp section,
confusing plist generation tools.
Discussed with espie@, guenther@ and kettenis@; initial patch from espie@.
ok espie@
Keep using Java 8, but add necessary patches and update jffi and
jruby-launcher dependencies so that Java 11 could be used. The JRuby
team still recommends the use of Java 8 for JRuby, though that will
be changing in the future.
Keep using Java 8, but add necessary patches and update jffi and
jruby-launcher dependencies so that Java 11 could be used. The JRuby
team still recommends the use of Java 8 for JRuby, though that will
be changing in the future.
