Update llvm-cheri to a new snapshot.

The CHERI LLVM backend can now target both 128-bit and 256-bit (as well
as 64-bit and 512-bit if hardware existed) from a single binary so remove
devel/llvm-cheri128.

Sponsored by:	DARPA, AFRL

Update to a new snapshot and apply the patch for posix_fallocate()
support being remove for ZFS

PR:		223383, 223440
Sponsored by:	DARPA, AFRL

Update to a new snapshot.

Add CROSS_TOOLCHAIN files (currently requiring in-tree binutils).

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

Make ninja opt-out in cmake.mk

Using ninja instead of make (1) can lead to significant speed ups while
building.
Therefore switch from having the ninja generator opt-in to having it opt-out.

Previously cmake-ports that wanted to use ninja could set
    CMAKE_NINJA=yes
now, ports that do not work with ninja can set
    cmake:<existing args>,noninja
Note, that needing this should be an exception and most often points to a broken
cmake of the port.

The ports using cmake were modified
* removed USES=gmake, if ninja is used
* removed MAKE_ARGS, if ninja is used
* added the cmake-argument noninja if necessary

PR:		219629
PR:		213331
Exp-run by:	antoine
Reviewed by:	rakuco
Differential Revision:	https://reviews.freebsd.org/D10748

Fix build when LOCALBASE is not /usr/local.

Reviewed by:	brooks
Sponsored by:	Dell EMC Isilon
Differential Revision:	https://reviews.freebsd.org/D10859

- Fix Shebangs

Remove the misspelled ONLY_FOR_ARCH definitions, which referred to an
arch we no longer support in any case.

Approved by:	portmgr (tier-2 blanket), "just fix it"

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

Fix build with gcc 4.9

PR:		196712

${RM} already has -f.

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

Update to a fresh snapshot.

Convert tab after WWW: in pkg-descrs to single space as per PHB

Approved by:	portmgr blanket

Upgrade CHERI LLVM and Qemu ports to new snapshots supporting the
upcoming v5 ISA.

Sponsored by:	DARPA, AFRL

Add a version of llvm-cheri for 128-bit CHERI capabilities.

No functional change to devel/llvm-cheri, just plist generalization.

Sponsored by:	DARPA, AFRL

Update to an April 23rd snapshot.

many ports: mark broken on powerpc64

Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g.

With hat:	portmgr
Sponsored by:	Absolight

Update to a March 3rd snapshot.

Update the Makefile.snapshot generate script to fine the date of the most
recent change rather than using today's date.

Update to the latest snapshot.

Upgrade to a new snapshot and switch to a -cheri suffix similar to other
llvm ports.

PR:		206036

Add file missed in previous commit.

Reviewed by:	FreshPorts Sanity Daemon

Update to a new CHERI-LLVM/Clang snapshot.

Remove UNIQUENAME and LATEST_LINK.

UNIQUENAME was never unique, it was only used by USE_LDCONFIG and now,
we won't have conflicts there.

Use PKGBASE instead of LATEST_LINK in PKGLATESTFILE, the *only* consumer
is pkg-devel, and it works just fine without LATEST_LINK as pkg-devel
has the correct PKGNAME anyway.

Now that UNIQUENAME is gone, OPTIONSFILE is too. (it's been called
OPTIONS_FILE now.)

Reviewed by:	antoine, bapt
Exp-run by:	antoine
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D3336

Disable LLDB when the chosen compiler is gcc.

On platforms where the system compiler isn't clang (including 9.x),
USES=compiler:c++11-lib uses gcc48 as the compiler.  Unfortunatly, gcc48
does not provide a sufficently complient c++11 environment to build LLDB
when compiled on 9.x and possiably on other platforms.

Replace lang/clang-cheri with devel/llvm-cheri derived from devel/llvm-devel
and update to the latest versions in git.

Sponsored by:	DARPA, AFRL