comms/wsjtx2.5.4_17

*/*: update boost consumers after boost-1.92

*/*: bump consumers after devel/boost update

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

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

devel/boost: bump consumers after Boost update

devel/boost: bump consumers after Boost-1.87 update

Sponsored by:	Future Crew, LLC

comms/wsjtx: Give bin/jt9 an executable stack

jt9 is supposed to have an executable stack, but a bug in lld (now
fixed upstream) prevents that.

This change explicitly sets the required exectuable stack for jt9.
Much simpler than using mprotect et. al.

PR:		278939
Reported by:	jeffpc@josefsipek.net
Reviewed by:	adrian
Differential Revision: https://reviews.freebsd.org/D48572

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

Sponsored by:	Future Crew, LLC

*/*: bump consumers after devel/boost* update

With hat:	office
Sponsored by:	Future Crew, LLC

devel/boost: bump consumers after library update

devel/boost*: bump all consumers after 1.83.0

comms/wsjtx: Stray line left in broke build

wsjtx has it's own patch system which is hard to work with.
I goofed and somehow left a line in which broke the build completely. :-(

PR:		ports/262937

comms/wsjtx: Fix Fortran runtime error

Suggested fixes did not work for FreeBSD because of clang differences
this should fix problem.

PR:		PR:	262937

*/*: bump all direct Boost cunsumers

*: Bump PORTREVISIONs for math/mpc update to 1.3.1

comms/wsjtx: Same bug as hamlib treating a function like a variable

wsjtx insist on packaging their own version of hamlib which means
the fix to hamlib meant the bug was still in wsjtx

*/*:	bump libboost*.so libraries consumert after Boost upgrade

Mk/Uses: always use colon for build/run suffix

Most USES use a colon for build/run(/test) suffixes. Change kde.mk,
qt.mk and pyqt.mk to do the same, and update all ports using that.

Document in CHANGES.

PR:			266034
Exp-run by:		antoine
Approved by:		tcberner (mentor)
Differential Revision:	https://reviews.freebsd.org/D36349

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.

This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.

There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.

The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.

Approved by:		portmgr (tcberner)

*/*: bump all consumers after recent boost upgrade

devel/boost-all: bump all library consumers after boost upgrade

PR:	246106

devel/cmake: Update to 3.23.0

Update to 3.23.0.
Fix pkg-plist: using the default share/man location

Release Notes:
  https://cmake.org/cmake/help/v3.23/release/3.23.html

PR:		262886
Exp-run by:	antoine

devel/libtool, devel/libltdl: update to 2.4.7

comms/wsjtx: patch configure instead of configure.ac to avoid autotools.
The build runs autoconf to regenerate configure but forgets to run
libtoolize to update ltmain.sh.

PR:		263151
Exp-run by:	antoine

Fix CONFLICTS entries of multiple ports

There have been lots of missing CONFLICTS_INSTALL entries, either
because conflicting ports were added without updating existing ports,
due to name changes of generated packages, due to mis-understanding
the format and semantics of the conflicts entries, or just due to
typoes in package names.

This patch is the result of a comparison of all files contained in
the official packages with each other. This comparison was based on
packages built with default options and may therefore have missed
further conflicts with optionally installed files.

Where possible, version numbers in conflicts entries have been
generalized, some times taking advantage of the fact that a port
cannot conflict with itself (due to logic in bsd.port.mk that
supresses the pattern match result in that case).

A few ports that set the conflicts variables depending on complex
conditions (e.g. port options), have been left unmodified, despite
probably containing outdated package names.

These changes should only affect the installation of locally built
ports, not the package building with poudriere. They should give an
early indication of the install conflict in cases where currently
the pkg command aborts an installation when it detects that an
existing file would be overwritten,

Approved by:	portmgr (implicit)

comms/wsjtx:  Update to 2.5.4

Release: WSJT-X 2.5.4
	             Dec 28, 2021
	        ----------------------

This is mostly a bug fix  release.  It has the following changes since
release 2.5.3:

WSJTX:
 - Repair a defect that caused occasional crashes when in QSO with
   stations using nonstandard callsigns.

Reported by:	@portscout

comms/wsjtx: Update to 2.5.2

- Repair a  longstanding regression  that caused signal  reports from
  tail-ended Tx2 messages to be omitted from logged information

- Parse   "dx-call-1 RR73; dx-call-2 <de-call> +nn"  messages  (i3=0,
  n3=1 DXpedition mode) in regular 77-bit modes

- Repair a regression  associated with setting the  main window width
  on program startup.

- Repair a problem with Q65 decodes  of type 'q3' for messages of the
  form "<Call_1> Call_2"

- Execute code associated with Q65 decodes of type 'q5' only when the
  Max   Drift   control   is   set  to   50.    This   fix   prevents
  double-incrementing of  the message averaging counter  on the first
  decoding sequence.

- Polarization offset 'Dpol' from the astronomical data window is now
  written    to    file     azel.dat    if    environment    variable
  WSJT_AZEL_EXTRA_LINES has  been defined as  1 or greater.   Dpol is
  especially useful for EME on the higher microwave bands.

- The Auto  Log QSO option  in "Settings->Reporting" now  behaves the
  same  as  the Prompt  to  log  QSO option  when  not  in a  special
  operating context mode.

- The Fast/Normal/Deep  setting in  Q65 mode is  now a sticky setting
  and is no longer reset to Fast on program startup or  when Settings
  has  been opened. The user selection is used for automatic decodes,
  but Deep is used for any subsequent manual decode attempts.

- New hamlib code to correct minor flaws in controlling several rigs.

- Update  the  Chinese  and  Hong   Kong  translations  of  the  user
  interface.

PR:		ports/260618
Reported by:	hellocodebsd@gmail.com

graphics/mesa-libs: Bump reverse deps for libglvnd

Per discussion with bapt on helping pkg handle the changing of these
deps and avoiding impossible upgrade senarios.

PR:		246767
Reviewed by:	manu, bapt
Approved by:	x11
Differential Revision:	https://reviews.freebsd.org/D30824

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

Remove # $FreeBSD$ from Makefiles.

Fix r561520

/!\ wsjtx-2.1.2_2: Makefile errors /!\

you cannot include bsd.port[.pre].mk twice

Defining both PORTVERSION and DISTVERSION is wrong, only set one, if necessary,
set DISTNAME

*** Error code 1

Stop.
make: stopped in /usr/ports/comms/wsjtx

Approved by:	portmgr (blanket)

Update GCC_DEFAULT from 9 to 10.

A few (mostly Fortran-based) ports need to be patched because GCC 10
is stricter.  A handful of ports need to be restricted to GCC 9 because
they fail with 10.

5 ports still fail with GCC 10.  However, seeing as this work has been
ongoing since 2020-05-24, it is simply time to make the commit and
notify the affected maintainers.

While here, pet portlint (Makevar order).

PR:		246700
Submitted by:	gerald
Approved by:	antoine (after many, many, -exp runs)

Fix build under clang-11

comms/wsjtx: prepare for cmake-3.18.x

- this belongs into the "let's forget this ever happened category".
- with cmake-3.18 the target to patch the thirdparty sources gets
  ran twice. Onde during build and once during the install phase.
- we silently remove the patches again after the build is done, so
  that during the install phase, the patching is a no-op.

PR:		248003

comms/wsjtx: Prepare for Qt5-5.14

PR:		244964

Drop dependency on devel/openmp

- Drop if devel/llvm* was used as a substitute

Approved by:	yuri, rene (earlier version)
Differential Revision:	https://reviews.freebsd.org/D23020

Update to 2.1.2 remove clogf now that we have clogf in libm

-- partial release notes from upstream

Copyright 2001 - 2019 by Joe Taylor, K1JT.

		   Release: WSJT-X 2.1.1
		     November 25, 2019
		   ---------------------

WSJT-X 2.1.1 is a bug fix only release addressing regressions in the
prior v2.1.0 release.

 - Document rules for the UDP message protocol.
 - Fix bug that could cause display of a blank Settings window.
 - Fix message parsing to properly handle 4-character directed CQs
 - Fix a potential crash in the interface to Omni-Rig.
 - Improve handling of unexpected rig off line status changes from
   Omni-Rig.
 - Add an option to highlight unworked 2-character grid fields rather
   than 4-character grid squares.
 - Fix bug that caused unwanted disabling of "Enable Tx" in Fox mode.
 - Log duplicate contacts in FT8 DXpedition Fox mode.
 - Regenerate the GFSK Tx waveform if Tx audio frequency is changed.
 - Fix the behavior of double-clicking on a decoded message with first
   callsign displayed as an unresolved hash code <...>.
 - Fix a problem with determining "worked before" status after a band
   change.
 - Updates to the WSJT-X 2.1 User Guide.
 - Fix a production issue with the macOS tool chain that generated
   broken executables.

		   Release: WSJT-X 2.1
		      July 15, 2019
		   -------------------

WSJT-X 2.1 is a major update that introduces FT4, a new protocol
targeted at HF contesting.  Other improvements have been made in the
following areas:

  - FT8 waveform generated with GMSK, fully backward compatible
  - user options for waterfall and spectrum display
  - contest logging
  - rig control
  - user interface
  - UDP messaging for inter-program communication
  - accessibility

There are numerous minor enhancements and bug fixes.

We now provide a separate installation package for 64-bit Windows 7
and later, with significant improvements in decoding speed.

devel/openmp: update to 9.0.0

- Connect tests to the framework to help QA remaining patches
- Force rebuild all consumers after https://reviews.llvm.org/D59783

Changes:	http://llvm.org/viewvc/llvm-project/openmp/tags/RELEASE_900/final/?view=log
ABI:		https://abi-laboratory.pro/tracker/timeline/llvm_openmp/

comms/wsjtx: Update 2.0.1 -> 2.1.0

PR:		240224
Requested by:	kunda <chitty_cloud@me.com>

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

WSJT-X requires sqlite, not just sql.

Reported by:	Mike English <mike.english@gmail.com>

devel/openmp: phase out

- Expire after the last version without /usr/lib/libomp.so
- Drop SOVERSION for seamless transition (i.e., avoid conditionals)

PR:		236907
Approved by:	bapt (maintainer)
Differential Revision:	https://reviews.freebsd.org/D19767

Related to revision 499061 bump ports with USES=fortran to have them benefit from the improved situation where libgcc_s is only used when absolutely necessary.

Suggested by:	tijl

Fix build when hamlib is installed.

Put /usr/local/include at end of AM_CPPFLAGS instead of at beginning,
ensures the included header files are used.

Link included hamlib using ${libdir}/libhamlib.a rather than -lhamlib to
ensure the included static hamlib is used instead of a dynamic one in the
library path.

MFH:		2019Q2 (build fix)

Update devel/readline to 8.0

- Bump PORTREVISION of dependent ports for shlib change

Changes:	https://tiswww.case.edu/php/chet/readline/CHANGES
PR:		236156
Exp-run by:	antoine

- update to 2.0.1 - builds on i386 now - remove MAKE_JOBS_UNSAFE - Upstream wsjtx build instructions call for their forked   version of hamlib for wsjtx to work correctly.   Upstream distribution includes both wsjtx and a copy of their   forked hamlib with their own build system. This is now used in   this updated port. The cmake build provided does not have an   install/strip target which forces 

N.B. If hamlib is already installed, this port will incorrectly
link against the shared library version of hamlib instead of the
private copy provided. There seems no easy solution to this.

comms/wsjtx: Only append to EXTRA_PATCHES after bsd.port.pre.mk

Untangle it from do-extract too while here

Fix Qt5 symbol version scripts to put the catch-all clause first.  When a symbol matches multiple clauses the last one takes precedence.  If the catch-all is last it captures everything.  In the case of Qt5 libraries this caused all symbols to have a Qt_5 label while some should have Qt_5_PRIVATE_API.  This only affects lld because GNU ld always gives the catch-all lowest priority.

Older versions of Qt5Webengine exported some memory allocation symbols from
the bundled Chromium.  Version 5.9 stopped exporting these [1] but the
symbols were kept as weak wrappers for the standard allocation functions to
maintain binary compatibility. [2][3]  The problem is that the call to the
standard function in these weak wrappers is only resolved to the standard
function if there's a call to this standard function in other parts of
Qt5Webengine, because only then is there a non-weak symbol that takes
precedence over the weak one.  If there's no such non-weak symbol the call
in the weak wrapper resolves to the weak wrapper itself creating an infinite
call loop that overflows the stack and causes a crash.  Some of the
allocation functions are variants of C++ new and delete and it probably
depends on the compiler whether these variants are used in other parts of
Qt5Webengine.

Remove the weak wrappers (make them Linux specific).  This isn't binary
compatible but we are already breaking that with the changes to the symbol
versions.

[1] https://github.com/qt/qtwebengine/commit/5c2cbfccf9aafb547b0b30914c4056abd25942a4
[2] https://github.com/qt/qtwebengine/commit/2ed5054e3a800fa97c2c9e920ba1e6ea4b6ef2a5
[3] https://github.com/qt/qtwebengine/commit/009f5ebb4bd6e50188671e0815a5dae6afe39db5

Bump all ports that depend on Qt5.

PR:		234070
Exp-run by:	antoine
Approved by:	kde (adridg)

Update to 2.0.0

1.x is obsolete as of Jan. 1st, and is already hard to find QSOs with.
Not sure if we need to MFH this, since the quarterly should branch soon.

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

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