Thread: [Hamlib-developer] pkg-config 0.29.1 vs 0.29.2
Library to control radio transceivers and receivers
Brought to you by:
n0nb
Menu
▾
▴
hamlib-developer
|
From: Uwe, D. <dg...@gm...> - 2025-11-20 19:27:20
|
Dear Hamlib developers, I noticed that the newest Hamlib source code can no longer be built on Linux Mint 20.3 because pkg-config 0.29.2 has been specified in configure.ac as the minimum version (see the following lines). dnl Ensure that the PKG_PREREQ macro is defined: m4_ifndef([PKG_PREREQ], [m4_fatal([must install pkg-config (or pkgconf) 0.29.2 or later before running bootstrap])]) PKG_PREREQ([0.29.2]) PKG_PROG_PKG_CONFIG([0.29.2]) However, I found out that Hamlib still builds fine when I change this to pkg-config 0.29.1, and that WSJT-X (Improved) works well with such a Hamlib build in Mint 20.3. So my question is. Is there a specific reason why the pkg-config specification has been changed to 0.29.2? I mean, I now know how to work around this, but in case it is just a self-imposed hurdle, could this perhaps be set to 0.29.1? FYI: I still need my old Mint 20.3 system from time to time to create Debian packages of WSJT-X (Improved) for OMs who cannot handle my usual packages which are compiled on the latest Mint 22.2 system. 73 de DG2YCB, Uwe ________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg...@gm... Info: www.qrz.com/db/DG2YCB |
|
From: Adrian <vk...@gm...> - 2025-11-20 22:54:28
|
Uwe, Perhaps the wrong place to ask, but I did not realize you use Mint for the deb packages for 'improved' Is it useful for me to do them for you on debian trixie as well as macos Darwin ? I always do my own here and do not use your debs. 73 vk4tux On 21/11/25 05:27, Uwe, DG2YCB via Hamlib-developer wrote: > Dear Hamlib developers, > > I noticed that the newest Hamlib source code can no longer be built on > Linux Mint 20.3 because pkg-config 0.29.2 has been specified in > configure.ac as the minimum version (see the following lines). > > dnl Ensure that the PKG_PREREQ macro is defined: > m4_ifndef([PKG_PREREQ], > [m4_fatal([must install pkg-config (or pkgconf) 0.29.2 or later > before running bootstrap])]) > > PKG_PREREQ([0.29.2]) > PKG_PROG_PKG_CONFIG([0.29.2]) > > However, I found out that Hamlib still builds fine when I change this > to pkg-config 0.29.1, and that WSJT-X (Improved) works well with such > a Hamlib build in Mint 20.3. > > So my question is. Is there a specific reason why the pkg-config > specification has been changed to 0.29.2? > > I mean, I now know how to work around this, but in case it is just a > self-imposed hurdle, could this perhaps be set to 0.29.1? > > FYI: I still need my old Mint 20.3 system from time to time to create > Debian packages of WSJT-X (Improved) for OMs who cannot handle my > usual packages which are compiled on the latest Mint 22.2 system. > > 73 de DG2YCB, > Uwe > ________________________________________ > German Amateur Radio Station DG2YCB > Dr. Uwe Risse > eMail: dg...@gm... > Info: www.qrz.com/db/DG2YCB > > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
|
From: Uwe, D. <dg...@gm...> - 2025-11-21 11:44:37
|
Hi Adrian, Mint is not the problem. The .deb and .rpm packages created with it do the job on all Linux distributions. However, backward compatibility is always problematic. You know this from your Darwin packages for macOS as well (10.13 or 14 vs newer systems). In the case I mentioned, an OM was unable to install my Debian packages created with Mint 22.1 on his Mint 21.2 system. I then created one for him on my old Mint 20.3 system, which worked perfectly. That's why I continue to maintain this old system. (I have a triple-boot system on my main machine with Windows 11, Mint 22.2, and Mint 20.3; the latter two slightly modified to resemble Windows 10.). But for Mint 20.3, I need pkg-config 0.29.1 to be allowed if I want to compile Hamlib with it. I think others will also fall into this trap with the latest Hamlib versions. So the question is, does it really have to be that way, or is pkg-config 0.29.2 a self-imposed hurdle? 73 de DG2YCB, Uwe ________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg...@gm... Info: www.qrz.com/db/DG2YCB Am 20.11.2025 um 23:54 schrieb Adrian: > > Uwe, Perhaps the wrong place to ask, but I did not realize you use > Mint for the deb packages for 'improved' > > Is it useful for me to do them for you on debian trixie as well as > macos Darwin ? > > I always do my own here and do not use your debs. > > > 73 > > > vk4tux > > On 21/11/25 05:27, Uwe, DG2YCB via Hamlib-developer wrote: >> Dear Hamlib developers, >> >> I noticed that the newest Hamlib source code can no longer be built >> on Linux Mint 20.3 because pkg-config 0.29.2 has been specified in >> configure.ac as the minimum version (see the following lines). >> >> dnl Ensure that the PKG_PREREQ macro is defined: >> m4_ifndef([PKG_PREREQ], >> [m4_fatal([must install pkg-config (or pkgconf) 0.29.2 or later >> before running bootstrap])]) >> >> PKG_PREREQ([0.29.2]) >> PKG_PROG_PKG_CONFIG([0.29.2]) >> >> However, I found out that Hamlib still builds fine when I change this >> to pkg-config 0.29.1, and that WSJT-X (Improved) works well with such >> a Hamlib build in Mint 20.3. >> >> So my question is. Is there a specific reason why the pkg-config >> specification has been changed to 0.29.2? >> >> I mean, I now know how to work around this, but in case it is just a >> self-imposed hurdle, could this perhaps be set to 0.29.1? >> >> FYI: I still need my old Mint 20.3 system from time to time to create >> Debian packages of WSJT-X (Improved) for OMs who cannot handle my >> usual packages which are compiled on the latest Mint 22.2 system. >> >> 73 de DG2YCB, >> Uwe >> ________________________________________ >> German Amateur Radio Station DG2YCB >> Dr. Uwe Risse >> eMail: dg...@gm... >> Info: www.qrz.com/db/DG2YCB >> >> >> >> >> _______________________________________________ >> Hamlib-developer mailing list >> Ham...@li... >> https://lists.sourceforge.net/lists/listinfo/hamlib-developer > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
|
From: Nate B. <n0...@n0...> - 2025-11-22 12:09:07
Attachments:
signature.asc
|
* On 2025 20 Nov 13:27 -0600, Uwe, DG2YCB via Hamlib-developer wrote: > Dear Hamlib developers, > > I noticed that the newest Hamlib source code can no longer be built on Linux > Mint 20.3 because pkg-config 0.29.2 has been specified in configure.ac as > the minimum version (see the following lines). > > dnl Ensure that the PKG_PREREQ macro is defined: > m4_ifndef([PKG_PREREQ], > [m4_fatal([must install pkg-config (or pkgconf) 0.29.2 or later before > running bootstrap])]) > > PKG_PREREQ([0.29.2]) > PKG_PROG_PKG_CONFIG([0.29.2]) > > However, I found out that Hamlib still builds fine when I change this to > pkg-config 0.29.1, and that WSJT-X (Improved) works well with such a Hamlib > build in Mint 20.3. > > So my question is. Is there a specific reason why the pkg-config > specification has been changed to 0.29.2? As I worked on FreeBSD build support, pkg-config became the easiest and most reliable way to handle the FreeBSD path differences from GNU. It quickly became apparent that pkg-config is no longer maintained as 0.29.2 is the last release from March 2017. It has been supplanted by pkgconf which is actively developed. > I mean, I now know how to work around this, but in case it is just a > self-imposed hurdle, could this perhaps be set to 0.29.1? It appears that 0.29.2 fixes some bugs: https://gitlab.freedesktop.org/pkg-config/pkg-config/-/raw/master/NEWS?ref_type=heads Perhaps these aren't relevant to building Hamlib on GNU based systems, but I've not tested on FreeBSD, although the VM I used has a far more recent version of pkgconf with pkg-config nowhere to be found. > FYI: I still need my old Mint 20.3 system from time to time to create Debian > packages of WSJT-X (Improved) for OMs who cannot handle my usual packages > which are compiled on the latest Mint 22.2 system. Mint 20 support ended in April 2025 so security updates are no longer available. I understand that in some cases this is not a priority, especially on a system that isn't connected to a network or other considerations. I'm reluctant to change the minimum version as 0.29.2 is already nearing nine years of age and is the last release of that project. Perhaps a simple script to call sed to replace the 2 with a 1 would work and do the Hamlib build. That would only need to be done on the Mint 20 system. 73, Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 |
Thanks for helping keep SourceForge clean.
X