Remove expired ports:

2020-02-29 lang/gcc6: Unsupported by upstream. Use GCC 9 or newer instead.
2020-02-28 www/pycarddav: Deprecated by upstream, please migrate to
deskutils/py-khard
2020-03-02 x11/xpra: Old, uses EOLed python27
2020-03-02 x11-wm/ccsm: Old, uses EOLed python27
2020-03-02 x11-toolkits/py-gtkglext: Old, uses EOLed python27
2020-03-02 deskutils/syncthing-gtk: Old, uses EOLed python27
2020-03-02 x11-wm/compiz-fusion: Old, uses EOLed python27
2020-03-02 x11/run_scaled: Old, uses EOLed python27

This port (lang/gcc6) has been marked deprecated since r485607 (2018-11-22).

Now that its last consumer in the tree is gone, mark it for actual removal
with an expiration date end of February 2019, some eight weeks from now.

Now that GCC 9 is the canonical version in the Ports Collection,
recommend that (instead of GCC 9) in the deprecation notes of ports
for old versions of GCC.

lang/gcc*: Hide pkg-message during upgrades

PR:		239419
Approved by:	gerald (maintainer)

Recommend the use of GCC 8 (instead of GCC 7 until now) to replace
these older versions of GCC - GCC 4.8, GCC 5, and GCC 6 - which have
been end-of-lifed upstream many moons ago.  GCC 8 has been the default
version of GCC in the Ports Collection for a while and as such proven
itself, plus of all versions it is most likely to be present/used.

No functional change, just updated advice to our users.

Simplify the creation of the multilib-related sub-directory tree on
powerpc64 and avoid leaving an empty directory behind on the way.

PR:		235964, 231804
Discussed with:	Piotr Kubaj <pkubaj@anongoth.pl>

Backport r488673 | andreast | 2018-12-29 from lang/gcc7:

  Fix build of GCC on powerpc64.

  While building GCC itself we have to use the built GCC libraries to
  configure additional parts of GCC and not the libraires from the host.

  Install the built 32-bit libraries. This was not done up to now.

And no longer required GCC 5 to build on powerpc64, making this port a
natural choice of a "base" for newer members of the lang/gcc* family.

PR:		235964, 231804
Submitted by:	Piotr Kubaj <pkubaj@anongoth.pl>

Fix an incorrect sed regular expression used in libjava by adding a local
patch files/patch-libjava-classpath-scripts-check_jni_methods.sh.in.
Escapes of ordinary characters will be disallowed by regex(3) in the
future. [1]

While here already, factor out a proper USES block in the Makefile. [2]

PR:		233443 [1]
Submitted by:	kevans [1]
Reported by:	portlint [2]

On powerpcspe configure GCC --with-cpu=8548 instead of --with-cpu=8540,
which caused the build to fail after the update to binutils 2.31 and was
factually incorrect anyways (since the oldest we support is 8548).

PR:		235393
Reported by:	jhibbits

Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 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, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.

PR:		231590

Remove a conflict with gcc6-devel which does not exist any longer.

Deprecate this port since GCC 6 has been end-of-lifed upstream and
lang/gcc7 and lang/gcc8 are available as official releases.  Do not
mark for expiration yet, though.

Install texinfo files (GNU info) into ${PREFIX}/share/info

After a discussion on the mailing list on moving manpages to
${PREFIX}/share/man for consistency with base where it is
installed in usr/share/man, it appeared the same should happen
to GNU info files which were installed under share in base and
not in ports.

Now texinfo is not in base on any of the supported version of FreeBSD
it is possible to proceed to this move and it is easier to do than
the manpage change.

Other benefit than consistency are less patching: all build tools but
cmake are expecting info files to be under share/info and cmake (patched here)
was having an exception for BSD so the patch makes FreeBSD case less
specific for them

Bump revision of all impacted ports

PR:		232907
exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D17816

Update to the GCC 6.4.0 upstream release which carries a number of
fixes and closes the GCC 6 release  branch.

files/patch-armv7-support and files/patch-freebsd-unwind.h made it
upstream in between GCC 6.4 and GCC 6.5, so remove them.

After an include, PLIST_SUB must be appended to, not overwritten.

If it is overwritten, many values will be clobbered, and
pain will ensue.

PR:		230864
Submitted by:	mat
exp-runs by:	antoine

Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.

This includes ports
 - featuring USE_GCC=yes or USE_GCC=any,
 - featuring USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and those
 - with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
   c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.

PR:		222542

Improve the explanation on why on powerpc64 we require USE_GCC=5 and
not one of the more common/flexbile options such as USE_GCC=yes.

Reported by:	linimon

Backport r469768 from lang/gcc7:

Simplify MASTER_SITES, taking advantage of the default for GCC releases
provided by MASTER_SITES_ABBREVS.

Reported by:	portlint

Run "/usr/sbin/service ldconfig restart" for USE_LDCONFIG instead of
"ldconfig -m <path>" so the order of ldconfig search directories after
package installation is the same as after a reboot.  The original command
simply appends the path to the list of directories while the ldconfig rc.d
script uses "sort -u".

Bump lang/gcc* which are known to install libraries with exactly the same
name so the library loaded at runtime depends on the order of the search
directories.

PR:		228046
Approved by:	portmgr (antoine)

Filter the -mretpoline command-line option, which is understood by
recent versions of clang (and used in the context of the Spectre
security issues), but not GCC (which uses different options for the
same) from CFLAGS and CXXFLAGS.

This avoids the build of this port via bootstrap, which is the default
and leverages both the system compiler (clang in most cases) plus a just
built version GCC, to fail due to the latter not knowing -mretpoline.

PR:		228205
Submitted by:	rozhuk.im@gmail.com

Update mpfr to 4.0.1 release and bump PORTVERSION of dependent ports.

math/cloog
 - Update to 0.19.0
 - Use github
 - Add ac_cv_prog_TEXI2DVI to avoid building docs for now

devel/isl
 - Update to 0.19

- Bump PORTREVISION of all dependencies

Allow gcc compilers to be built on new arch 'powerpcspe'.

Tested for no-harm on amd64.

Submitted by:		jhibbits
Approved by:		portmgr (tier-2 blanket)
Differential Revision:	D13126

Bump PORTREVISIONs of all users of math/mpc that we just updated to
version 1.1.0 (via revision 464079).

Rework the architecture-specific special settings, sorting snippets and
using .elif instead of distinct .if sequences, similar to most of the
other lang/gcc* ports by now. (This being the default port we usually
let changes settle elsewhere first.)

Backport revision 454177 from lang/gcc7 now also to lang/gcc6, the
current default GCC port:

Make sure what we install is stripped (i.e., debug info is removed).

The straightforward way is setting INSTALL_TARGET to install-strip,
which is supported by the upstream GCC build machinery.

Unfortunately this fails when running as regular user (non-root)
since strip requires write permission to the files in question,
and we install binaries as r-xr-xr-x by default.  To work around
that we need to set BINMODE to allow for write access by the user,
something that's common on GNU/Linux (which is why this probably
has not been noticed there).  This is not necessary when running
as root.

Add a patch that we pulled into gcc6-devel via upstream a few days ago
that addresses a real-world issue around threading and unwinding as
files/patch-freebsd-unwind.h .

This will become obsolete with the next release of GCC 6, GCC 6.5.

Bump PORTREVISION since this is a functional change.

On the way fix up the format for files/patch-armv7-support . [1]

Reported by:	portlint [1]

Add support for armv7-*-freebsd*.
This patch is already upstreamed and can be dropped once a new GCC 6.x is
released.

PR:	221905
Submitted by:	mmel@
Approved by:	gerald@ (maintainer)

Add a conflict with the lang/gcc6-devel port as we've had it in lang/gcc5
(for lang/gcc5-devel) for a fair while.  This mirrors what we did for the
lang/gcc5-devel port earlier this week.

Also make Python a build-only dependency when building Java
(via JAVA_USES=python:build) which makes the installed port/package
quite a bit more lightweight.

Bump PORTREVISION for those two changes.

Do not quote constant strings compared with ${ARCH}. [1]  Remove
some commented (and thus disabled) logic around this on the way.

This brings the active lang/gcc* release-based ports in sync with
their respective lang/gcc*-devel twins.

PR:		221905 [1]
Submitted by:	linimon [1]

Bump PORTREVISION for ports depending on the canonical version of GCC
(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

Move ONLY_FOR_ARCHS and BROKEN_sparc64 together and up into a block
of their own (per guidance from portlint and the manual).

Remove workaround for PR 219274 that bapt@ had put in place in 2014
from pkg-plist for lang/gcc5 and lang/gcc6 (which won't be updated
too soon otherwise).

PR:		219274

Update to the GCC 6.4.0 upstream release which carries a number of fixes.

This now comes as an xz archive, so update USES=tar accordingly.

Also this now includes
  files/patch-aarch64-support,
  files/patch-libgcc-config-arm-unwind-arm, and
  files/patch-x86-64-fix-m16
which andreast@ and me pushed upstream.

On the other hand we gain bin/gcov-dump6 and man pages for gcov-dump6
and gcov-tool6.

Finally, as with lang/gcc5 and lang/gcc6-devel, remove headers being
created by GCC's fixincludes machinery from the installation / packaging
to avoid breakage when FreeBSD's headers are changing afterwards.

Alphabetize ARCH definitions.

No need to bump PORTREVISION because package does not change.

Reviewed by:	gerald
Approved by:	portmgr (tier-2 blanket)

Adjust WWW URL to refer to https and avoid a trailing slash.

Replace the general USE_GCC=yes when building for powerpc64 by the
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

Forward port files/patch-x86-64-fix-m16 from lang/gcc5.  This has been
in gcc6-devel for a while, but the next GCC 6 release has been taking
longer than expected, so let's put this in temporarily.

PR:		219291

I jumped the gun by marking this broken on powerpc64.  There is
active work ongoing to debug it.

Mark some ports failing on power64.  In cases where the error message
was a stub, provide a real one.

While here, pet portlint.

Approved by:	portmgr (tier-2 blanket)
Reported by:	swills

Make _Unwind_GetIP, _Unwind_GetIPInfo and _Unwind_SetIP available as functions
for arm*-*-freebsd*.
This patch is already pushed upstream to all active gcc branches.
GCC-5, GCC-6, GCC-7 and trunk. The gcc?-devel ports will catch up these bits
with the next update.
Once a new release for gcc6 or gcc5 is done, this patch will be obsolete.

Approved by: gerald@ (maintainer)

- Fix shebang

Approved by:	gerald (maintainer via mail)

Define WCHAR_T for aarch64 on all active gcc (gcc/gcc5 and gcc6) releases.
This define is already in upstream.
The gcc*-devel ports will pickup the commit from upstream.

Submitted by:	kan@
Approved by:	gerald@ (maintainer)

Bump PORTREVISIONs for ports depending on the canonical version of GCC and
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

Backport the bits needed for aarch64-*-freebsd* support from the gcc6-devel
port.
The same applies here as on the lang/gcc5 port, as soon as GCC releases
a new gcc6, these bits go away. Iow, they are already part of the gcc6-devel
branch.

Approved by:	gerald(maintainer)

No longer define CPE_VERSION for ports tracking releases of GCC since
there the default of PORTREVISION is just fine.

Remove traces of armv6hf which no longer exists as an arch. [1]

Sort ONLY_FOR_ARCHS.

Reported by:	andreast [1]

No longer BROKEN on powerpc64 according to andreast@.

The output of tools like awk, date, sort, tr,... depends on the current
locale set by the user.  Add LANG=C and LC_ALL=C at the beginning of
bsd.port.mk and export them so all commands are executed with the C locale.
LC_ALL=C overrides all other LC_* variables.  LANG is used by setlocale(3)
as default value for LC_* variables, so normally it isn't used when LC_ALL
is set, but there's code out there that looks at LANG directly so it's safer
to set it as well.  The only commands not captured by this are !=
assignments before any inclusion of bsd.port.*mk.

Introduce USE_LOCALE=<locale> that adds LANG=<locale> and LC_ALL=<locale> to
CONFIGURE_ENV and MAKE_ENV so upstream build systems can be executed with a
different locale (e.g. USE_LOCALE=en_US.UTF-8).

PR:		215882
Exp-run by:	antoine
Approved by:	portmgr (antoine)

Update to the GCC 6.3 release which brings a number of bugfixes.

Omit the definition of DISTVERSION which is only necessary for ports
tracking snapshots of GCC and simplify the definition of GCC_VERSION
(but keep the latter as a variable to align the gcc6-devel and gcc6 ports).

Remove files/patch-unwind-ia64.h since we have not been supporting ia64
with this release series (ONLY_FOR_ARCHS has not been including ia64).

Replace USE_GCC=4.9+ by USE_GCC=yes, now that lang/gcc and the default
version for GCC in the Ports Collection have moved to GCC 4.9.

${RM} already has -f.

PR:		213570
Submitted by:	mat
Exp-run by:	antoine
Sponsored by:	Absolight

Update to the GCC 6.2 release with a fair number of fixes.

files/patch-armv6-hf-support has been accepted upstream, even
on the GCC 6-branch this release comes from, so remove it.

Backport the following from lang/gcc6-devel:

GCC uses an AWK script to generate source code that helps process
command-line options.  According to POSIX, string comparisons (and
hence sorting) are to be performed based on the locale's collating
order.  Alas GNU AWK only does so in POSIX mode, whereas starting
with FreeBSD 11 we do so by default, running into a bug (or false
assumption) with that script used by GCC.

Setting MAKE_ARGS such that AWK is always invoked in the C locale
works around this bug. [1]

PR:		210122 [1], 211742 [1]
Submitted by:	jkim [1]

Skip armv6hf support and move it into armv6.

Welcome to the GCC 6.1 release, the first release of the GCC 6 series.

The default mode for C++ is now -std=gnu++14 instead of -std=gnu++98.

Type-based alias analysis now disambiguates accesses to different pointers.
This improves precision of the alias oracle by about 20-30% on higher-level
C++ programs. Programs doing invalid type punning of pointer types may now
need -fno-strict-aliasing to work correctly.

Value range propagation now assumes that the this pointer of C++ member
functions is non-null. This eliminates common null pointer checks but also
breaks some non-conforming code-bases (such as Qt-5, Chromium, KDevelop).
As a temporary work-around -fno-delete-null-pointer-checks can be used.
Wrong code can be identified by using -fsanitize=undefined.