comms/uhd: Update to 4.9.0.1

Seems to embed flatbuffers now.

	../../cad/kicad-library-symbols-devel/kicad-symbols/

devel/boost: bump consumers after boost upgrade (+)

Get rid of direct dependency ob libbost_system.so, use libboost_thread.so
instead

python.mk: rename PYTHON_EXT_SUFFIX to PYTHON_TAG, document, etc

EXT_SUFFIX, according to PEP 3149, refers to the full tag and
extension for compiled extension module objects, eg .cpython-311.so,
.cpython-313t.so, etc. We do not use the correct semantic meaning,
and this usage becomes ambiguous and confusing when tags do not
match between bytecode and compiled extension module objects.

Rename our PYTHON_EXT_SUFFIX to PYTHON_TAG to align with PEP 3147's
specification of a magic tag, which consists of implementation name
and shorthand version only. This is meant for bytecode and other
files containing this tag in their filename that do not depend on
a specific Python ABI for the same version. Chase all existing
consumers.

devel/boost: bump consumers after Boost update

comms/uhd: Updates uhd to unbreak it and build with boost 1.87

Unbreak build due to change to boost 1.87
* Highlights / Main Changes
  - Addition of rfnoc_modtool and further improvements to RFNoC Image Builder
    toolsets. This further improves the ability to design RFNoC blocks and
    create custom FPGA bitfiles.
  - Replaced RFNoC FFT block with a new version
  - Improved Windows installation capabilities including distribution
    of binary Python bindings for Windows though PyPI

Remove obsolete patches.

PR:		286080

Reported by:	Diane Bruce

comms/uhd: mark as BROKEN with Boost>=1.87 (+)

Since 1.87 release some long-time-ago deprecated Boost.asio facilities was
dropped off

Sponsored by:	Future Crew, LLC

devel/boost: bump consu,ers after update Boost to 1.86 release

Sponsored by:	Future Crew, LLC

comms/uhd: unbreak build with boost-1.85

With hat:	office
Sponsored by:	Future Crew, LLC

*/*: Sunset 12.4-RELEASE/12-STABLE from ports tree

- Remove all references to defunct ARCH arm
- Remove all references to defunct ARCH sparc64
- Remove x11-drivers/xf86-video-sunffb which requires defunct sparc64
  ARCH
- Remove sysutils/afbinit requires defunct sparc64 ARCH
- Remove all references to bktr driver
- Remove all references to defunct FreeBSD_12
- Remove all references to OSVERSION/OSREL corresponding to 12
- Remove conditionals in Mk/Uses/cabal.mk
- Remove sparc reference from Mk/Uses/qt-dist.mk
- Remove BROKEN_sparc64/NOT_FOR_ARCH=sparc64
- Remove BROKEN_FreeBSD_12* from:
- Remove OpenSSL patches from:
- Remove conditional flags for OSVERSION >= 1300000 to fixed flags.
  Also move conditional flags for non sparc64/arm ARCH to fixed flags.

Reviewed by:	brooks, jbeich, rene, salvadore
Differential Revision: https://reviews.freebsd.org/D42068

comms/uhd: Remove PORTDOCS macro

The PORTDOCS macro was duplicating the files already listed in
pkg-plist.

===>  Building package for uhd-4.6.0.0_1
pkg-static: duplicate file listing: /usr/local/share/doc/uhd/LICENSE, fatal
(developer mode)
pkg-static: duplicate file listing: /usr/local/share/doc/uhd/README.md, fatal
(developer mode)

Approved by:	portmgr (blanket)

comms/uhd: Fix pkg-plist

comms/uhd: Update to 4.6.0

all: remove explicit versions in USES=python for "3.x+"

The logic in USES=python will automatically convert this to 3.8+ by
itself.

Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.

finance/quickfix: mark BROKEN with PYTHON

libtool: compile:  c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp  -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
          ^~~~~~~~~~
1 warning and 1 error generated.

Reviewed by:	portmgr, vishwin, yuri
Differential Revision:	<https://reviews.freebsd.org/D40568>

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

*/*: bump all consumers after recent boost upgrade

comms/uhd: Fix pkg-plist and update

Try to unbreak the build and update to 4.2.0.0

comms/uhd: update to 4.1.0.5 release to unbreakd build after boost upgrade

RP:	246106

*/*: Remove redundant '-[0-9]*' from CONFLICTS

The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").

Many CONFLICTS definitions used patterns like "bash-[0-9]*" to filter
for the bash package in any version. But that pattern is functionally
identical with just "bash".

Approved by:	portmgr (blanket)

*: fix tab vs. space issues, and comments according to the guide.

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

Remove # $FreeBSD$ from Makefiles.

Clean up some things

- Fix typos
- Remove duplicate variables
- Remove nop variables
- Sort categories

Reported by:	portscan

devel/doxygen: Update to 1.9.0

- regen patches by 'make makepatch'
- adjust consumers which affected by new doxygen styles
- take maintainersip

Changelog: https://www.doxygen.nl/manual/changelog.html#log_1_9_0

PR:		242347
Submitted by:	fluffy
Reported by:	Naram Qashat (ex-maintainer)
Exp-run by:	antoine

comms/uhd: fix build on GCC architectures

/usr/local/bin/ld: lib/libuhd.so.4.0.0: undefined reference to
`__atomic_compare_exchange_16'
/usr/local/bin/ld: lib/libuhd.so.4.0.0: undefined reference to
`__atomic_store_16'
/usr/local/bin/ld: lib/libuhd.so.4.0.0: undefined reference to
`__atomic_load_16'

Try to fix i386 build

Update to release 4.0.0.0 and use python 3.6+

PR:		249591
Submitted by:	rhurlin@

comms/uhd: unbreak on powerpc64

Builds fine

MFH:		2020Q1 (fix build blanket)

comms/uhd: Prune duplicate BROKEN_powerpc64

devel/boost-*: update to 1.72.0

Changes:	http://www.boost.org/users/history/version_1_72_0.html
PR:		241449
Exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D22136

Try to Unbreak, builds directly and with poudriere.

PR:		225462
Submitted by:	John Hein

Mark BROKEN: fails to package

pkg-static: Unable to access file
/wrkdirs/usr/ports/comms/uhd/work/stage/usr/local/share/uhd/examples/python/benchmark_rate.py:No
such file or directory
pkg-static: Unable to access file
/wrkdirs/usr/ports/comms/uhd/work/stage/usr/local/share/uhd/examples/python/curses_fft.py:No
such file or directory
pkg-static: Unable to access file
/wrkdirs/usr/ports/comms/uhd/work/stage/usr/local/share/uhd/examples/python/rx_to_file.py:No
such file or directory
pkg-static: Unable to access file
/wrkdirs/usr/ports/comms/uhd/work/stage/usr/local/share/uhd/examples/python/tx_waveforms.py:No
such file or directory

Reported by:	pkg-fallout

Try to unbreak and update to 3.14.1.1

Mark BROKEN

pkg-static: Unable to access file
/wrkdirs/usr/ports/comms/uhd/work/stage/usr/local/share/uhd/examples/python/benchmark_rate.py:No
such file or directory
pkg-static: Unable to access file
/wrkdirs/usr/ports/comms/uhd/work/stage/usr/local/share/uhd/examples/python/curses_fft.py:No
such file or directory
pkg-static: Unable to access file
/wrkdirs/usr/ports/comms/uhd/work/stage/usr/local/share/uhd/examples/python/rx_to_file.py:No
such file or directory
pkg-static: Unable to access file
/wrkdirs/usr/ports/comms/uhd/work/stage/usr/local/share/uhd/examples/python/tx_waveforms.py:No
such file or directory

Reported by:	pkg-fallout

Apply some cleanup from the PR and update to 3.14.1.0

PR:             225462
Submitted by:   John Hein

devel/boost-*: update to 1.71.0

Changes:	http://www.boost.org/users/history/version_1_71_0.html
PR:		238827
Exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D20774

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

devel/boost-*: update to 1.70.0

Changes:	http://www.boost.org/users/history/version_1_70_0.html
PR:		235956
Exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D19303

Update devel/doxygen to 1.8.15

PR:		236110

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

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

devel/boost-*: update to 1.69.0

Changes:	http://www.boost.org/users/history/version_1_69_0.html
PR:		232525
Exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D17645

Expand FreeBSD 12 conditionals to include 13.0-CURRENT

Add DOCS options to ports that should have one.

Also various fixes related to said option.

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

devel/boost-*: update to 1.68.0

- Switch to C++14 for libboost_system to support C++14 consumers

Changes:	http://www.boost.org/users/history/version_1_68_0.html
PR:		229569
Exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D16165

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

Mark broken on arm-current.

Approved by:	portmgr (tier-2 blanket)

devel/boost-*: update to 1.67.0

Changes:	http://www.boost.org/users/history/version_1_67_0.html
PR:		227427
Exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D15030

comms/uhd: unbreak with boost 1.67

host/lib/usrp/cores/rx_vita_core_3000.cpp:77:35: error:
      no matching conversion for functional-style cast from 'double' to
'boost::posix_time::milliseconds' (aka
      'subsecond_duration<boost::posix_time::time_duration, 1000>')
        boost::this_thread::sleep(boost::posix_time::milliseconds(1.0));
                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PR:		227427
Reported by:	antoine (via exp-run)

Update to 3.10.3.0 and try to fix compilation under current.

devel/boost-python-libs got forgotten in the python flavorization, fix
this oversight.

Reviewed by:	antoine
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D14368

Try to unbreak the build for boost 1.66

PR:		224087

devel/boost-*: update to 1.66.0

Changes:	http://www.boost.org/users/history/version_1_66_0.html
PR:		223922
Exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D13279

Update to rel. 3.10.2.0

- Add explicit FLAVOR to a few dependencies
- Remove FLAVOR from py-docutils dependency in comms/uhd, in this case
  it needs the rst2html command, not the docutils module
- Mark some ports as not compatible with python3

Convert Python ports to FLAVORS.

  Ports using USE_PYTHON=distutils are now flavored.  They will
  automatically get flavors (py27, py34, py35, py36) depending on what
  versions they support.

  There is also a USE_PYTHON=flavors for ports that do not use distutils
  but need FLAVORS to be set.  A USE_PYTHON=noflavors can be set if
  using distutils but flavors are not wanted.

  A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
  added to cope with Python ports that did not have the Python
  PKGNAMEPREFIX but are flavored.

  USES=python now also exports a PY_FLAVOR variable that contains the

devel/boost-*: update to 1.65.1

Changes:	http://www.boost.org/users/history/version_1_65_1.html
PR:		218835
Approved by:	maintainer timeout (1.65.1: 2 weeks; 1.65.0: 1 month)
Tested by:	jhibbits (on powerpc64, earlier version)
Exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D11582

devel/boost-*: enable C++11 features

PR:		218835
Obtained from:	https://github.com/DragonFlyBSD/DeltaPorts/pull/690
Approved by:	maintainer timeout (2 months)
Exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D11582

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

Update to version 3.10.1.1

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

Use MAKE_CMD instead of MAKE in do-install.

This is more consistent and translates into gmake instead of make.

Fix shebangs.

Approved by:	rakuco (mentor, implicit)

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)

devel/boost-*: update to 1.64.0

Changes:	http://www.boost.org/users/history/version_1_64_0.html
PR:		218835
Approved by:	office (bapt)
Exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D10472

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

devel/boost-*: update to 1.63.0

Changes:	http://www.boost.org/users/history/version_1_63_0.html
PR:		215598
Exp-run by:	antoine
Approved by:	office (bapt)
MFH:		2017Q1

devel/boost-*: update to 1.62.0

- Enable `long double` C99 math usage
- Switch 9.x back to building with GCC

Changes:	http://www.boost.org/users/history/
PR:		199601
Submitted by:	Chen Xu, bapt, amdmi3, truckman (based on)
Reviewed by:	rakuco (kde) (earlier version)
Exp-run by:	antoine (3 tries), truckman (consumers only, earlier versions)
Approved by:	bapt (office)

Conditionalize sse flags on amd64/i386.  They make no sense elsewhere
and cause breakages.

Approved by:	portmgr (tier-2 blanket)

comms/uhd: Document ncurses requirement

Approved by:	ncurses blanket

UHD seems to use SSE2 functions and seems to need the addional compiler spitch
for FreeBSD 11+ i386

devel/pkgconf doesn't search under lib/pkgconfig by default

Whatever you do, ${PORTSDIR} always creeps in depends.

Sponsored by:	Absolight

- Update devel/doxygen to 1.8.12
- Adjust plist of ports depending on it

PR:		212869

Try to fix the package build for DOXYGEN=ON/OFF

Some fixes for better ports compatibility suggested my Mathieu.

Submitted by:	mat@

Add the latest stable Ettus-Research USRP Hardware Driver (UHD) Software and
firmware images.
In contrast to comms/usrp it compiles only the host part and not the images.
The images are the binaries from ettus.

While the port compiles cleanly it doesn't fully work for my B200
but this could be a local HW problem since the B* series is picky about the USB3
HW...
Therefore this port is currently not connected to gnuradio.