- there was never a lang/python3/3.6 (@pkgpath marker for this is present in
current 3.6 plists), python3/3.x was only used for 3.2, so remove these.
- they should probably have originally used "@pkgpath lang/python/3.5" to
trigger updates from 3.5 when 3.5 was removed, but no point adding those
to 3.6 now that 3.7 is the default version. so add @pkgpath lang/python/3.5
markers in 3.7 PLISTs, fixing the upgrade path if old versions were present
(there was previously nothing to trigger 3.5 being removed/updated so
stray packages would be left around).
problem reported by Laurie Tratt
Do the same thing we do with the flang driver and force linking with the
static libraries instead.
Reported off-list by j <AT> bitminer <DOT> ca -- thanks!
like the rest of the ports tree. This also allows removing a bunch of
manual setting of PATH="${PORTPATH}" HOME="${PORTHOME}" done in various
ports etc. This also makes sure CFLAGS is passed through (not everything
honours it but it does improve at least some ports).
Remove NO_CCACHE from www/honk that was added because the above problem
resulted in ccache variables not being passed through correctly breaking
the cc calls in this.
ok kmos@
"ld: error: XX: has non-ABS relocation R_386_GOTOFF against symbol 'XX'"
is seen on other ports (telephony/asterisk, math/py-scipy) when built
with gcc 8 and znotext does not help there, so is unlikely to help here
either.
* switch gcc4 module to gcc/8
* register the gcc/8 subpackages as updates for their gcc/4.9 counterparts
* sync the gcc version in devel/llvm
* add a quirk entry that gcj is obsolete
* unhook 4.9 from the build
Preparatory work by many.
ok sthen@
generate metadata/hash on libraries.
remove -doc subpackage too, as it has different files depending the
arch.
with that, we should be able to have rustc on more archs.
OK sthen@
While here, remove some comments in Makefile.inc about flang being
integrated into LLVM. That's no longer happening; the new f18 compiler is
scheduled to be integrated into LLVM instead.
MODPY_TEST_ARGS was not enough to get the tests to run using
MODPY_PYTEST, geo/py-proj.
This adds MODPY_TEST_DIR, which defaults to WRKSRC as is normal, to
allow overriding the subdirectory that tests run in. This isn't
specific to MODPY_PYTEST, it will work for PY_SETUPTOOLS tests also.
OK landry@ sthen@
