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

Remove # $FreeBSD$ from Makefiles.

security/cryptopp: Update to 8.4.0

Bump PORTREVSION on all consumers. ABI-breaking changes were introduced and
recompile of consumers is necessary.

Remove unused cryptopp dependency from devel/xeus. Upstream migrated to OpenSSL
several releases ago. [1]

[1]
https://github.com/jupyter-xeus/xeus/commit/c98c44c174cafcf424f4203dc3c61564118feb3e

Changes:	https://www.cryptopp.com/release840.html

devel/xeus: Update 0.24.3 -> 0.24.4

Reported by:	portscout

devel/xeus: Update 0.23.14 -> 0.24.3

Reported by:	portscout

devel/xeus: Unbreak on systems incompatible with the system where the package
was built

-march=native caused SEGVs on incompatible systems

The cmake option that turned it off was renamed. I also added the NATIVE option
that now drives the -march flag.

MFH:		2020Q2

devel/xeus: Update 0.23.13 -> 0.23.14

Reported by:	portscout

devel/xeus: Update 0.23.12 -> 0.23.13

Reported by:	portscout

devel/xeus: Update 0.23.10 -> 0.23.12

Reported by:	portscout

devel/xeus: Update 0.23.9 -> 0.23.10

Reported by:	portscout

devel/xeus: Update 0.23.8 -> 0.23.9

Reported by:	portscout

devel/xeus: Update 0.23.7 -> 0.23.8

Reported by:	portscout

devel/xeus: Update 0.23.6 -> 0.23.7

Reported by:	portscout

devel/xeus: Update 0.23.5 -> 0.23.6

Project's GH account is renamed.
WWW has been updated accordingly.

devel/xeus: Update 0.23.2 -> 0.23.5

Reported by:	portscout

devel/xeus: don't optimize for the host CPU

It causes a build error on powerpc64:
g++9: error: unrecognized command line option '-march=native'; did you mean
'-mcpu=native'?

And may cause runtime issues even when it builds.

PR:		242582
Approved by:	yuri (maintainer)

Update security/cryptopp to 8.2.0

Remove THREADS option - upstream recommends building with threads and the
build system now adds the appropriate flags automatically

Bump PORTREVISION on consumers due to shared lib version increase

PR:		241132
Submitted by:	Farid Hajji <farid@hajji.name>

devel/xeus: Update 0.19.2 -> 0.23.2

Reported by:	repology

Remove the -mtune=generic/-march=native fiddling on all archs, not just
GCC-based ones.

This will unbreak the build on aarch64.

Approved by:	portmgr (tier-2 blanket)

Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.

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, everything INDEX-11 shows with a dependency on lang/gcc9 now.

PR:		238330

For GCC-based systems, edit top-level CMakeLists.txt to eliminate
either of the following two problems:

  g++8: error: unrecognized command line option '-march=native'
  g++8: error: unrecognized argument in option '-mtune=generic'

Approved by:	portmgr (tier-2 blanket)

devel/xeus: Update 0.19.1 -> 0.19.2

Reported by:	portscout

devel/xeus: Update 0.18.1 -> 0.19.1

Reported by:	portscout

net/openpgm: Do not add -I to non-existing directory in openpgm-5.2.pc

foo/lib/pgm-5.2/include does not exist, so applications using strict
compiler flags will fail to build due to this.

Here this breaks devel/xeus build after r491260 [1]:

CMake Error in CMakeLists.txt:
  Imported target "cppzmq" includes non-existent path

    "/usr/local/lib/pgm-5.2/include"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

Mark BROKEN: fails to configure

CMake Error in CMakeLists.txt:
  Imported target "cppzmq" includes non-existent path
    "/usr/local/lib/pgm-5.2/include"

Reported by:	pkg-fallout

Change cmake default behaviour to outsource.

Ports that build out of source now simply can use "USES=cmake"
instead of "USES=cmake:outsource". Ports that fail to build
out of source now need to specify "USES=cmake:insource".

I tried to only set insource where explictely needed.

PR:		232038
Exp-run by:	antoine

devel/xeus: Update 0.13.0 -> 0.18.1

Reported by:	portscout

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

Pursuant to r483670, PORTREVISION should have been bumped.

Reported by:	jbeich

Fix build with GCC-based architectures.

PR:		232077
Submitted by:	Piotr Kubaj
Approved by:	portmgr (tier-2 blanket)

Update security/cryptopp to 7.0.0

We now install a pkgconfig file which will allow ports to check whether
cryptopp was built with assembly instructions enabled or not. There are
a few functions that will be undefined if built without assembly and
-DCRYPTOPP_DISABLE_ASM needs to be passed to the compiler in that case
to avoid build failures. This is not new, but the pkgconf file should
make it easier to determine if the flag is needed or not.

Fix several ports due to API changes and to use the new pkgconf file
to determine cryptopp location and build flags. Special cases below.

deskutils/cdcat
- Use cryptopp shared library instead of static, detect with pkgconf

devel/xeus: Fix build on 10 by adding USES=compiler:c++14-lang

Reported by:	fallout

devel/xeus: Patch installed cmake files: ZeroMQ doesn't provide *.cmake files.

New port: devel/xeus: C++ implementation of the Jupyter kernel protocol