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
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)
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
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)
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
- 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
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
/!\ 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)
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)
- 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
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.
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
- 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
- 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.
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] 5c2cbfccf9
[2] 2ed5054e3a
[3] 009f5ebb4b
Bump all ports that depend on Qt5.
PR: 234070
Exp-run by: antoine
Approved by: kde (adridg)
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
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
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
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.
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
(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
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
-----------------------------
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.
11. Power settings optionally remembered for Transmit and Tune on a
band-by-band basis.
New Modes
---------
1. MSK144 is intended for meteor scatter at 50 MHz and higher. It
uses a low-density parity check code (LDPC) designed by Steve Franke,
K9AN. The mode is a direct descendant of the now-defunct mode JTMSK,
with a number of improvements for better performance on weak and short
meteor pings. The effective character transmission rate is about 250
cps, compared with 147 cps for FSK441. Like JT4, JT9, JT65, and
QRA64, MSK144 uses strong forward error correction. Message decoding
is all or nothing: partial decodes do not occur, and you will see
little or no garbage on your screen.
Standard MSK144 message frames are 72 ms long, compared with about 120
ms for an equivalent FSK441 message. The MSK144 waveform allows
coherent demodulation, allowing up to 3 dB better sensitivity. After
QSO partners have exchanged callsigns, MSK144 can use even shorter
messages, only 20 ms long. As in all the fast modes in WSJT-X, the 72
ms (or 20 ms) messages are repeated without gaps for the duration of a
transmission cycle. For most purposes we recommend a T/R cycle
duration of 15 s, but 5 s and 10 s sequences are also supported.
Short ("Sh") messages in MSK144 are intended primarily for 144 MHz and
higher frequencies, where most pings are very short. These messages
do not contain full callsigns; instead, they contain a hash of the two
callsigns along with a report, acknowledgement, or 73. Short messages
are fully decodable only by the station to whom they are addressed, as
part of an ongoing QSO, because only then will the received hash match
that calculated using the known strings for "My Call" and "DX Call".
If you are monitoring someone else's QSO, you will not be able to
decode its Sh messages.
An MSK144 signal occupies the full bandwidth of a typical SSB
transmitter, so transmissions are always centered at an offset of
1500Hz. For best results, selectable or adjustable Rx and Tx filters
should be set to provide the flattest possible response over at least
300 - 2700 Hz. The maximum permissible frequency offset between you
and your QSO partner is 200 Hz, and less is better.
2. QRA64 is a intended for EME and other weak-signal use. Its
internal code was designed by Nico Palermo, IV3NWV, and implemented in
WSJT-X by K1JT. The protocol uses a "Q-ary Repeat Accumulate" code --
along with LDPC, another one of the latest research areas in
communication theory. The QRA64 code is inherently better than the
Reed Solomon (63,12) code used in JT65, yielding already a 1.3 dB
advantage. QRA64 uses a new synchronizing scheme based on a 7 x 7
Costas array, so you will not see a bright sync tone at the lowest
tone frequency. This change yields another 1.9 dB advantage.
In most respects our implementation of QRA64 is operationally similar
to JT65. QRA64 does not use two-tone shorthand messages, and it makes
no use of a callsign database. Rather, additional sensitivity is
gained by making use of "already known" information as a QSO
progresses -- for example, when reports are being exchanged and you
have already decoded both callsigns in a previous transmission. QRA64
presently offers no message averaging capability, though that may be
added. In our early tests, many EME QSOs have already been made using
submodes QRA64A-E on bands from 144 MHz to 10 GHz.
3. ISCAT is essentially the same as in recent versions of program WSJT.
For details consult the WSJT User Guide:
http://physics.princeton.edu/pulsar/K1JT/doc/wsjt/
Program Setup
-------------
Many of the new program capabilities are enabled when you check
"Enable VHF/UHF/Microwave features" on the Settings | General tab.
For MSK144 mode, we suggest setting "T/R 15 s" and "F Tol 100 Hz".
Check "Sh" to enable the use of short messages and "Auto Seq" for
auto-sequencing. For QRA64 mode, set Tx and Rx frequencies to 1000
Hz. We encourage you to check "Save all" when making tests, and to
save any of the resulting .wav files that might help us to improve
program performance or behavior, or to illustrate a problem that you
identify.
Final Comments
--------------
We will be grateful for any and all reports from users; these will
surely help us to make further improvements to WSJT-X. The most
helpful bug reports describe the problem clearly and include a
complete recipe to reproduce it. Feature requests are also welcome.
Send your reports to wsjtgroup@yahoogroups.com, or to the developers
list wsjt-devel@lists.sourceforge.net.
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
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
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.)
Tools for accurate frequency calibration of your radio, so you can
be always on-frequency to within about 1 Hz.
Mode-specific standard working frequencies accessible from the
drop-down band selector.
A number of corrections to the Hamlib library, fixing balky rig-control
features. A few unreliable features peculiar to particular radios
have been removed.
Working around bugs with a2x for now
PR: ports/208350
Submitted by: takefu@airport.fm
