WSJT ("Weak Signal Communication, by K1JT") offers specific digital protocols
optimized for meteor scatter, ionospheric scatter, and EME (moonbounce)
at VHF/UHF, as well as HF skywave propagation. The program can decode
fraction-of-a-second signals reflected from ionized meteor trails and
steady signals 10 dB below the audible threshold.
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
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: 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
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.
(Only the first 15 lines of the commit message are shown above )
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
(Only the first 15 lines of the commit message are shown above )
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
(Only the first 15 lines of the commit message are shown above )
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
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)
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
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.
(Only the first 15 lines of the commit message are shown above )
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/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 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 use of do-install.
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.
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
(Only the first 15 lines of the commit message are shown above )
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
Replace bsd.qt.mk by Uses/qt.mk and Uses/qt-dist.mk
From now on, ports that depend on Qt4 will have to set
USES= qt:4
USE_QT= foo bar
ports depending on Qt5 will use
USES= qt:5
USE_QT= foo bar
PR: 229225
Exp-run by: antoine
Reviewed by: mat
Approved by: portmgr (antoine)
Differential Revision: -https://reviews.freebsd.org/D15540
Upgrade to 1.9.1
Use NetBSD clogf for FreeBSD systems that are not at HEAD
Release: WSJT-X Version 1.9.1
June 1, 2018
-----------------------------
This critical bug fix release repairs an unintended restriction in the FT8
DXpedition mode. It supersedes v1.9.0 and must be used for DXpedition Fox
operators.
The WSJT Development Group is pleased to announce the full General
Availability release of WSJT-X Version 1.8.0.
Changes since "Release Candidate 3" (wsjtx-1.8.0-rc3) are very minor; they are
described in the Release Notes posted here:
http://physics.princeton.edu/pulsar/k1jt/Release_Notes_1.8.0.txt
Installation packages for Windows, Linux, Macintosh, and Raspian Jessie
have been posted on the WSJT web site here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/wsjtx-1.8.0-rc3/
(It may take a short time for the SourceForge site to be updated.)
If you are upgrading from -rc1, you will need to do a one-time reset of
the default list of suggested operating frequencies. Go to
*File->Settings->Frequencies*, right click on the table and select *Reset*.
We hope you will enjoy using WSJT-X Version 1.8.0.
-- 73, Joe, K1JT, for the WSJT Development Group
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
Revision bump of all ports with USE_GL after consolidation of mesa-libs
Approved by: swills (mentor)
Differential Revision: https://reviews.freebsd.org/D10845
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
Release: WSJT-X Version 1.7.0
-----------------------------
Short list of new features
--------------------------
1. New modes: ISCAT, MSK144, QRA64.
2. Newly implemented submodes: JT65B-C, JT9B-H (wide and fast).
3. FT decoder replaces KV decoder for JT65; KVASD is no longer used.
4. Improvements to JT4, JT9, and JT65 decoders.
5. Multi-pass decoding now implemented for JT65 as well as WSPR.
6. Many improvements to Rig Control.
7. Improved convenience features for EME Doppler tracking.
8. Multiple configurations can be saved and restored.
9. Sample-file download facility.
10. Optional auto-sequencing for Fast modes.
(Only the first 15 lines of the commit message are shown above )
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), part II.
The first part covered 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.
This adds ports with USES=fortran and ports using Mk/bsd.octave.mk
which in turn has USES=fortran.
PR: 214965
Reported by: thierry
Fix so it does not core on 10.x (shurd@)
Add missing dependancy so it builds man pages and user manual (db@)
Since they are using Sourceforge, clean up distfiles (db@)
No binary changes.
Reviewed by: shurd,db
Upgrade to wsjtx 1.6.0
For quick reference, here's a short list of features and capabilities added
to WSJT-X since Version 1.5.0:
WSPR mode, including coordinated automatic band-hopping and a new
two-pass decoder that can decode overlapping signals.
EME-motivated features including JT4 (submodes A-G), Echo mode, and
automatic Doppler tracking. The JT4 decoder is more sensitive than
that in the latest WSJT, and message averaging is fully automated.
(Note that submodes JT65B and JT65C are also present in Version 1.6,
but the high-sensitivity decoder required for EME with JT65
is not yet included.)
(Only the first 15 lines of the commit message are shown above )
Add patch to fix the build with the upcoming Qt 5.5.1.
./WFPalette.hpp:53:1: error: unknown type name 'Q_DECLARE_METATYPE'
Q_DECLARE_METATYPE (WFPalette::Colours);
WSJTX ("Weak Signal Communication, by K1JT") offers specific digital protocols
optimized for meteor scatter, ionospheric scatter, and EME (moonbounce)
at VHF/UHF, as well as HF skywave propagation. The program can decode
fraction-of-a-second signals reflected from ionized meteor trails and
steady signals 10 dB below the audible threshold.
This version is a non python Qt app.
