Backport the change to ensure what we install is stripped (i.e., debug
info is removed) from lang/gcc7. See revision 454177 for background. [1]
Shorten the distinct .if statements for architecture-specific settings,
to use .elif instead.
Reported by: Ports QA Framework, miwi, sobomax [1]
Discussed with: tijl, miwi [1]
Differential Revision: https://reviews.freebsd.org/D10357 [1]
Remove special code handling armv6 (which for GCC 6 and 5-based
ports is necessary for aarch64, armv6 and armv7, but that we never
had for aarch64 or armv7 here).
Consulted with: andreast
Add a conflict with the lang/gcc7 port like we've had it in
lang/gcc5-devel (for lang/gcc5) for a fair while and now also
lang/gcc6-devel (for lang/gcc6).
(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
Remove headers being created by GCC's fixincludes machinery from the
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.
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
pre-release mode (and changed it's version number from 7.0.0 to 7.0.1
accordingly).
Remove gcc7-devel/files/patch-libc++ again, which dim@ and me managed
to get in upstream quickly.
Similar to bug 212465 and bug 216266, lang/gcc7-devel doesn't compile
with libc++ 4.0.0, due to clashes between the redefined abort macro and
standard C++ headers.
Upstream seems to have realized this issue, and are now using system.h
to pull in C++ standard headers, when INCLUDE_xxx is defined, where xxx
is ALGORITHM, VECTOR, and so on.
In this case only gcov.c needs to be fixed.
Approved by: gerald (maintainer)
PR: 216303
MFH: 2017Q1
