Switching ports-gcc from gcc4.9 to gcc8 causes a PLIST change in all
dependent ports. E.g.:
--- /usr/ports/plist/amd64/libcerf-1.11
+++ /usr/ports/plist/amd64/libcerf-1.11-new
@@ -5,7 +5,7 @@
@arch amd64
+DESC
@sha eJKgQhCdr8i1gVOn1LSaMv4pNozHOTosL7nNrpe6GJU=
-@depend lang/gcc/4.9,-libs:gcc-libs->=4.9,<4.10:gcc-libs-4.9.4p19
+@depend lang/gcc/8,-libs:gcc-libs->=8,<9:gcc-libs-8.3.0p0
@wantlib c++.2.1
@wantlib c++abi.0.1
@wantlib c.95.0
That affects a considerable number of ports.
Espie thinks that bumping _SYSTEM_VERSION across all architectures
is too big a hammer and that we need to handle this arch by arch:
aarch64
Already uses gcc8, no change.
amd64, arm, i386
These are the other clang archs. They only use gcc4 for a limited
number of ports. The affected ports should receive an explicit
REVISION bump. All ports that have a LIB_DEPENDS or RUN_DEPENDS
on lang/gcc/4.9* are affected. This list might be slightly
different for each of the three archs.
all remaining archs
These have so many ports that depend on ports-gcc that bumping
them all would be too much work. Instead bump _SYSTEM_VERSION-$arch.
Is that an accurate summary of what needs to be done?
Index: arch-defines.mk
===================================================================
RCS file: /cvs/ports/infrastructure/mk/arch-defines.mk,v
retrieving revision 1.62
diff -u -p -r1.62 arch-defines.mk
--- arch-defines.mk 26 Apr 2019 16:10:06 -0000 1.62
+++ arch-defines.mk 27 Apr 2019 14:48:09 -0000
@@ -78,7 +78,7 @@ _SYSTEM_VERSION-aarch64 = 3
_SYSTEM_VERSION-amd64 = 4
_SYSTEM_VERSION-arm = 3
_SYSTEM_VERSION-i386 = 2
-_SYSTEM_VERSION-${MACHINE_ARCH} ?= 0
+_SYSTEM_VERSION-${MACHINE_ARCH} ?= 1
_SYSTEM_VERSION-${ARCH} ?= 0
# @version = ${_SYSTEM_VERSION} + ${_SYSTEM_VERSION-${MACHINE_ARCH}}
--
Christian "naddy" Weisgerber na...@mips.inka.de
