devel/*{-xtoolchain,}-gcc: Retire the old GCC external toolchain ports.

These have been supplanted by the devel/freebsd-gcc6 port which uses
separate flavors for each target architecture and bundles the
CROSS_TOOLCHAIN makefile.

Feedback from:	jrm
Reviewed by:	lwhsu, bapt
Differential Revision:	https://reviews.freebsd.org/D30765

One more small cleanup, forgotten yesterday.
Reported by:	lwhsu

Remove # $FreeBSD$ from Makefiles.

These ports now build on aarch64.

Approved by:	portmgr (tier-2 blanket)
Obtained from:	lonesome.com TRYBROKEN run

These ports now build on powerpc64.

Approved by:	portmgr (tier-2 blanket)

Simplify some of the logic for external GCC toolchain packages.

- Always define BU_PREFIX as GCC_TARGET if needed.  This was already
  effectively true, but BU_PREFIX was just being set to the same value
  in the case that GCC_TARGET wasn't defined.  This is simpler and
  avoids duplicating some logic.
- Simplify amd64-gcc by not defining GCC_TARGET and BU_PREFIX in that
  port but instead replacing "amd64" with "x86_64" in the
  devel/powerpc64-gcc Makefile.  This matches what base/gcc does.
- Remove FREEBSD_EXTENSION now that it is no longer needed.

Approved by:	zeising
Differential Revision:	https://reviews.freebsd.org/D18349

Cleanup packing lists for xtoolchain gcc packages.

- Add missing entries for gcov-dump and the gcov-tool manpage to the
  various xtoolchain gcc ports.
- Add gcov-dump to the post-install loops that handle optional renaming
  of tools and manpages.

Reviewed by:	kan
Differential Revision:	https://reviews.freebsd.org/D16465

Drop builtin float.h for amd64-gcc.

GCC's builtin <float.h> header is not compatible with
sys/x86/include/float.h.  Drop the builtin header for now.  If at
some point GCC's notion of floating point constants for i386 can
converge with sys/x86/include/float.h this can be restored.

Reviewed by:	bapt
Differential Revision:	https://reviews.freebsd.org/D16073

Catch up with changed binutils prefix some more

The amd64-gcc needs same treatment as amd64-binutils,
we need to override BUTARGET in order to account for
amd64 vs x86-64 mismatch.

Submitted by: lwhsu

Fix --sysroot for cross-toolchain GCC packages

By default, GCC assumes that a cross compiler should not have any valid
initial include or library paths aside from /usr/local/lib/gcc/<mumble>/.
This means that one cannot use --sysroot to point to a system root for
another architecture and have GCC automatically look for headers in
${sysroot}/usr/include, etc.  Currently we workaround this in FreeBSD's
build system with explicit -isystem, -B, and -L directives.  However,
this is cumbersome compared to clang (where a bare --sysroot DTRT)
especially when using the compiler to build other software (such as test
programs, etc.).

One can override GCC's assumption and force it to assume that it should
honor --sysroot by setting the '--with-sysroot' option to force GCC to
assume a specific system root.  By setting this to '/', this means that

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

Try to bring some consistency to ports that have x86-specific pieces.

 - in general, if we think that the code is not architecture-specific,
   and instead just enables x86 assembler by default, those should
   use BROKEN rather than IGNORE.  This will allow them to be attempted
   with TRYBROKEN.
 - spell i386 as x86.
 - spell asm as assembler.
 - pet portlint.

These changes should have no effect on tier-1 builds.

Approved by:	portmgr (tier-2 blanket)

Make the error results more correct, per recent logs.

Approved by:	portmgr (tier-2 blanket)

For ports that are marked BROKEN on armv6, and also fail to build on
armv7, mark them so.

This is part two of a multipart commit to bring armv7 ports to parity
with armv6.

Approved by:	portmgr (tier-2 blanket)
Obtained from:	lonesome.com -exp run

Make sure <arch-gcc> come with consistent content

Expand hackery in post-install target to
make sure that we always end up with same set of
$GCC_TARGET-prefixed files no matter if port is
built for cross target or for native target to be
used as external toolchain.

Take over the maintainership.

Reviewed by:	emaste, imp, bapt
Approved by:	bapt
Differential Revision:	https://reviews.freebsd.org/D10537

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

While here, pet portlint.

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

Mark the gcc crosscompiler ports as broken on various tier-2 archs.

Unfortunately neither the maintainer or I have time at the moment
to chase down all of these failures.  The "fails to package" ones
ought to be fairly easy to fix.

Discussed with:		maintainer

Yet another plist fix

Reported by:	cognet
Pointyhat to:	bapt

Fix plist

Reported by:	cognet

Make amd64-gcc respect the 'unknown' second component of the triplets
as other cross toolchain gcc ports

Update cross toolchain gcc to 6.2.0
Remove the powerpc64 patch which has been upstreamed

many ports: mark broken on powerpc64

Update cross gcc to 5.3.0
While here:
- fix packaging on amd64
- fix building with utf8 locales en recent head by enforcing the locale to be C

Resurrect amd64 xtoolchain needed for build FreeBSD with gcc as an external
toolchain

amd64 cross toolchain was somewhere broken and not really useful, let's focus
on gcc cross toolchain for arches not supporting clang for now

Fix packaging

Reported by:	pkg-fallout

Add an external toolchain suitable for amd64 target