Remove expired port:
2017-09-13 security/clambc: Practically unmaintained, featuring issues elsewhere
solved 6 years ago

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

Mark deprecated with an expiration date of 2017-09-13 since this is
essentially unmaintained upstream (last RC three years ago, features
issues fixed on the clang side six years ago, and fails to build with
modern compilers such GCC 6+ or clang for that matter).

Reset maintainership to give others a chance to pick this up. [1]

Bump PORTREVISION due to the changes above.

Replace USE_GCC=any by USE_GCC=5 to unstall PR 219275.

PR:		219289, 219275
Approved by:	zi (maintainer) [1]

Mark some ports failing on aarch64, and, in a few cases, other tier-2
archs.

While here, pet portlint.

Approved by:	portmgr (tier-2 blanket)

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

Bump PORTREVISIONS for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.8.5 to GCC 4.9.4 (at least under some
circumstances such as versions of FreeBSD or platforms).

In particular that is ports with USE_GCC=yes, USE_GCC=any, or one of
gcc-c++11-lib, openmp, nestedfct, c++11-lib as well as c++14-lang,
c++11-lang, c++0x, c11 requested via USES=compiler.

security/clambc: convert to CONFIGURE_OUTSOURCE

Approved by:	portmgr blanket
Differential Revision:	https://reviews.freebsd.org/D5895

security/clambc is not jobs safe.

This has failed on me at least twice recently.  Here's the last fail:
Assembler messages:
Fatal error: llvm[3]: Compiling Mangler.cpp for Release build
can't create /wrkdirs/security/clambc/work/clamav-bytecode-compiler-
  clambc-0.98.5rc1/obj/lib/Target/ClamBC/Release/version.o: No such file
  or directory

MASTER_SITES cleanup.

- Replace ${MASTER_SITE_FOO} with FOO.
- Merge MASTER_SITE_SUBDIR into MASTER_SITES when possible. (This means 99.9%
  of the time.)
- Remove occurrences of MASTER_SITE_LOCAL when no subdirectory was present and
  no hint of what it should be was present.
- Fix some logic.
- And generally, make things more simple and easy to understand.

While there, add magic values to the FESTIVAL, GENTOO, GIMP, GNUPG, QT and
SAMBA macros.

Also, replace some EXTRACT_SUFX occurences with USES=tar:*.

Checked by:	make fetch-urlall-list
With hat:	portmgr
Sponsored by:	Absolight

New port: security/clambc:

The ClamAV bytecode compiler allows users to build their own bytecode
signatures for use with ClamAV.

WWW: https://www.clamav.net/