On the way, rework the architecture-specific special settings, sorting
and using .elif instead of distinct .if sequences.
Add a workaround for armv7. [1]
Tested by: andreast [1]
This addresses a real-world issue around threading and unwinding that
andreast@ has fixed upstream and backported to the GCC 6 release branch
(cf. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82635 ).
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
installation / packaging to avoid breakage when FreeBSD's headers are
changing afterwards. Several fellow committers have strongly indicated
that our headers do not need the kind of adjustments that GCC performs.
Bump PORTREVISION since unfortunately this appears relevant with the
pending release of FreeBSD 11.1.
No longer default to building GCJ/libgcj on any platform, that is,
option JAVA no longer is the default anywhere. lang/gcc6 retains
this for the time being as does lang/gcc5.
And indent JAVA_USES aligned with other entries.
specific USE_GCC=5 to be future proof when GCC 6 becomes the default
(since USE_GCC=yes would then pull in lang/gcc6 which we obviously
cannot require to build gcc6 itself nor gcc6-devel). This also helps
users who play with GCC_DEFAULT in Mk/bsd.default-versions.mk.
Reported by: jhibbits
Discussed with: andreast
There are two cases:
- The upstream versionning is compatible with our versionning, or using
DISTVERSION's magic leads to a compatible PORTVERSION, use
DISTVERSION. If it is possible to use DISTVERSIONPREFIX and
DISTVERSIONSUFFIX to make it compatible, use them.
- The upstream versionning is not compatible with our versionning, and
DISTVERSION's magic does not lead to a correct PORTVERSION, then set
PORTVERSION to the equivalent of our versionning, and set DISTNAME.
It is possible to use a third variable where you store upstream's
version and use it to compute PORTVERSION and/or DISTNAME, like the
dns/bind9* ports do.
Sponsored by: Absolight
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
