Search Criteria
Package Details: fldigi 4.1.23-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/fldigi.git (read-only, click to copy) |
---|---|
Package Base: | fldigi |
Description: | Digital Modem Program for Amateur Radio |
Upstream URL: | http://w1hkj.com |
Keywords: | ham radio |
Licenses: | GPL |
Submitter: | Allan |
Maintainer: | not_anonymous |
Last Packager: | not_anonymous |
Votes: | 52 |
Popularity: | 0.33 |
First Submitted: | 2008-12-19 03:37 (UTC) |
Last Updated: | 2022-06-23 18:17 (UTC) |
Dependencies (10)
- cty (cty, bigcty)
- fltk (fltk-xcas, fltk-mod, fltk-git)
- flxmlrpc
- hamlib (hamlib4, hamlib-git)
- hamradio-menus
- libpulse (libpulse-bluedio, pulseaudio-pali, pulseaudio-dummy, libpulse-nosystemd-git, libpulse-nosystemd, libpulse-nosystemd-minimal-git, libpulse-airplay, pulseaudio-git)
- libsamplerate (libsamplerate-git, libsamplerate-minimal-git)
- portaudio
- libsndfile (libsndfile-minimal-git, libsndfile-git) (optional) – sound file support
- pulseaudio (pulseaudio-bluedio, pulseaudio-pali, pulseaudio-dummy, pulseaudio-nosystemd-git, pulseaudio-nosystemd-minimal-git, pulseaudio-airplay, pulseaudio-git, pipewire-pulse-git, pipewire-common-pulse-git, pipewire-full-pulse-git, pipewire-pulse) (optional) – pulseaudio support
Required by (14)
- cqrlog-bin (optional)
- cqrlog-git (optional)
- cqrlog-source (optional)
- flamp
- flcluster (optional)
- fldigi-docs (optional)
- flmsg
- flrig (optional)
- flrig-git (optional)
- flwkey (optional)
- kcat (optional)
- tlf (optional)
- tlf-git (optional)
- yfklog (optional)
Latest Comments
chainofflowers commented on 2022-05-06 21:58 (UTC)
v4.1.21 is not available anymore, now there's v4.1.22...
not_anonymous commented on 2022-02-21 01:53 (UTC)
Well..20-1 had a work around for flxmprpc being stuck at 0.1.4.... BUT (drum roll please), while waiting on Dave to deal with his various repos, I decided to get flxmlrpc up to 1.0.1 (which I did by going to Dave's upstream repo at Sourceforge...) TADA...this package is now up-tp-date as well...
dviktor commented on 2021-08-06 20:22 (UTC)
4.1.20 is avail. Moreover it seems like it requires now new flxmlrpc (>= 1.0.1) but the author hasn't released it yet
not_anonymous commented on 2021-06-25 23:15 (UTC)
Updated
not_anonymous commented on 2020-11-18 01:29 (UTC)
Well, it's NOT LIKE the upstream author isn't having LOTS of problems and releasing quite often these days. Hi Hi.... Anyways, I decided to "comment-out" the conflicts field AND add the suggested "--without-asciidoc" as a config directive. *** Hope this helps !
linkjay commented on 2020-11-17 23:57 (UTC) (edited on 2020-11-17 23:58 (UTC) by linkjay)
This package is out-of-date because it attempts to download the version of fldigi 4.1.15 which does not appear to be there anymore because they updated it to 4.1.16. Maintainer, please fix!
For the time being, download the current PKGBUILD, edit change the "pkgver" variable from 4.1.15 to 4.1.16. You will also have to update the md5sum and sha256sum. Download fldigi from the official link found in the PKGBUILD or google it. You should download "fldigi-4.1.16.tar.gz". Then run
sha256sum
andmd5sum
on the file and replace the sums in the PKGBUILD. Now runmakepkg -si
where it should now attempt to download and build fldigi.It might fail because you are missing some dependent packages, these are found in the aur and I just downloaded them using my aur-helper:
yay -S cty flxmlrpc hamradio-menus
Should work after updating pkgver, updating the sums, and downloading the proper packages!
nickoe commented on 2020-11-02 23:13 (UTC)
Do we even need asciidoc enabled for this package? I would expect that to only be fore developers which would probably build fldigi locally?
mykhal commented on 2020-11-01 18:21 (UTC)
Possible build error related to broken dialogs/guide.cxx is caused by that asciidoc is for some reason inserting several \x0D (^M) characters. It can be fixed, for manual builds by adding
into PKGBUILD:build() just above make ..., after first makepkg failed, then running makepkg -e, then makepkg -U <generated pkg file>.
Or by adding --without-asciidoc configure flag.
grandchild commented on 2020-10-22 22:53 (UTC)
you are right, the patch doesn't cleanly apply. and i found out that that is because the lines are fine when the source is first extracted. they only get changed during the build process, by some process that is prefixed with "GUIDE" in the build output. i will try and figure out what that process is, but that's gonna be tomorrow... sleep now. :P
not_anonymous commented on 2020-10-22 22:07 (UTC) (edited on 2020-10-22 22:27 (UTC) by not_anonymous)
Actually that patch is being "rejected" on the latest source.;
a) malformed: i.e. some of the lines begin like this;
\n\iv id=\"toc\">
b) Um...AND the line numbers do not match the source. (Off by one line)
c) finally it is written so to ADD newline characters (which are already there....)
ANYWAYS ...that's why I didn't use it.....Would/could you please check it grandchild ?
grandchild commented on 2020-10-22 21:01 (UTC)
Sorry, but the solution is not to simply conflict with
asciidoc
.asciidoc
is actually an optional make dependency. If it is present, then more things get built.The solution would either be to apply the patch I made, or to explicitly disable the part that gets built when
asciidoc
is present. I haven't checked which part that is, and if it has a configure flag to disable it. Maybe it does?not_anonymous commented on 2020-10-22 20:03 (UTC)
Okey dokey.....made the appropriate change....thanks OM's ...es vy 73
df8oe commented on 2020-10-21 07:47 (UTC) (edited on 2020-10-21 07:48 (UTC) by df8oe)
Thanks for your very fast reactions. I can confirm that "asciidoc" causes the issue. I deinstalled it, after that the build process finished successfully. Then I reinstalled asciidoc. It is a workaround - but it works :)
grandchild commented on 2020-10-20 19:49 (UTC)
Hah, I found it. It fails to compile if you have
asciidoc
installed!I guess that technically counts as a problem with this package...
grandchild commented on 2020-10-20 17:16 (UTC)
Alright, in a new Archlinux VM it does compile and work. I will figure out what configure/make does different on my system...
grandchild commented on 2020-10-20 17:00 (UTC)
Java? It's not a Java problem. df8oe said something about Javascript, which is irrelevant anyway, since it's an encoding problem in a C++ file.
not_anonymous commented on 2020-10-20 13:59 (UTC) (edited on 2020-10-20 14:09 (UTC) by not_anonymous)
Before I submitted this latest PKGBUILD, I updated my system and then tested both the build and execution of this software WITHOUT ANY PATCHES being applied. i.e. The software package works FB here including the results that the patch supposedly fixes without needing the patch.
SO..; I will spend a couple of days and think through whether this patch should be applied. (And I will go look at Dave's info on what is going on. LOTS of problems, it appears, with other linux distros and Windows.)
For what it is worth; that this is a java problem surprises me NOT... Hi Hi.
P.S.... I'm running jre8 (openjdk) for what it is worth.....hmmm......
grandchild commented on 2020-10-20 11:02 (UTC) (edited on 2020-10-20 11:05 (UTC) by grandchild)
Same here. The issue is that in src/dialogs/guide.cxx in line 738, 739 and 740 there are stray 0x0d (CR/carriage return) characters. Something went wrong somewhere (commit from Windows?).
This patch fixes it (can't post it literally here, because the CR character would probably get mangled):
https://effekthasch.org/Ohseiz9Rui0Thah/fix-fldigi-aur-dialogs-guide-cr.patch
df8oe commented on 2020-10-20 08:11 (UTC)
Does not build... It looks like there is a html page with included javascript that throws tons of errors so that the name of the file itself or any further informations have left screen buffering. Occurs on all of my machines.
not_anonymous commented on 2020-07-18 18:43 (UTC)
(my turn) - UPDATED to ....14-1 .
dviktor commented on 2020-07-18 07:21 (UTC)
@freswa works fine, thank you! Now I see that there is
libxft
among other deps of fldigi:freswa commented on 2020-07-17 22:28 (UTC)
Checkout the latest fltk.
dviktor commented on 2020-07-17 14:27 (UTC)
@freswa I already have fldigi installed and working. If I install fltk from [community] then fldigi doesn't start up at all - you can see that there no dependencies on libxft and related libs in
lddtree
output. However if I rebuild fltk from community with-DOPTION_USE_XFT
(and only with that) then fldigi works fine. No need to rebuild fldigi itself, it's only related to the fltk packagefreswa commented on 2020-07-17 14:18 (UTC)
We don't fix packages that are not broken. fltk is working for all our rebuilds, so it's up to you to file a proper bug report which points us to a reproducible error in a clean chroot. Your bug report states, that the application doesn't run. I compiled fldigi several times against fltk in [community] and the application started fine for every rebuild.
If you need help debugging, please feel free to ask for help in the forum, the IRC or on the ML.
dviktor commented on 2020-07-17 12:36 (UTC) (edited on 2020-07-17 12:38 (UTC) by dviktor)
Unfortunately, my request for rebuilding fltk with Xft support was unsuccessful. This is the answer from project manager:
Famous "works for me", sad
Actual fix for that is to enable
-DOPTION_USE_XFT=ON
during CMake call inPKGBUILD
and addlibxft
dependency where neededdviktor commented on 2020-07-12 07:40 (UTC)
@mh00h great work! but I still don't understand - it's only a matter of specifying
libxft
inmakedepends
. when I tried to build 1.3.5-2 by hands I got the problem but when I built 1.3.5-3 (modified by me in the same way as maintainer did with the exception of changing dependencies) things worked finemh00h commented on 2020-07-12 01:20 (UTC) (edited on 2020-07-12 01:20 (UTC) by mh00h)
For those who are still struggling with this, the issue turned out to be that a dependency, fltk, is not compiled with --enable-xft in the official arch repo.
dviktor commented on 2020-07-09 09:18 (UTC) (edited on 2020-07-09 09:19 (UTC) by dviktor)
Well, I've found something interesting. Actually splitting package to examples and base doesn't break fldigi. But exclusion of some dependencies breaks it completely. I've compared
lddtree
output of/usr/bin/fldigi
executable with fltk-1.3.5-1 and fltk-1.3.5-2 installed and that's the difference between two outputs (fldigi lacks these libs when fltk-1.3.5-2 is installed):And this is modified PKGBUILD which works just fine (you could try it):
I've requested re-opening of bug mentioned by @Dieter9 so will see if David will try to fix it
Dieter9 commented on 2020-07-09 08:08 (UTC)
I had the same problems like dviktor. It was clearly related to the update of the packet fltk. I wrote a bug-report for fltk: https://bugs.archlinux.org/task/67089?string=fltk&project=0&search_name=&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=2020-06-01&openedto=&closedfrom=&closedto= But the Project Manager has denied the request. Later I fond the solution to compile the fltk package with makepkg on my computer. I informed the Project Manager of fltk again, but he does not care about. Perhaps someone can prove this correlation and could open a new Bug-Report for fltk.
not_anonymous commented on 2020-07-07 22:54 (UTC)
Um, since this DOES turn out to be an upstream issue and not (apparently) something to do the the current PKGBUILDs (both this one AND the fldigi-git); I un-flagged the "out-of-date". i.e The current PKGBUILD is correct v/v the upstream repo's indication of the current package. Anything else is either an ALPHA package or from the author's git repo; which is to say a TESTING version and NOT something I should be using for the "release" PKGBUILD.
Since this appears to be an issue that only affects SOME of the users (which have numerous ttf packages loaded up), I would suggest either using the fldigi-git PKGBUILD OR simply editing this PKGBUILD as you need for testing UNTIL SUCH TIME as the patching/corrections are FULLY tested.
mh00h commented on 2020-07-07 22:39 (UTC)
agreed not working for me either
dviktor commented on 2020-07-07 22:37 (UTC)
@mh00h I've backported patch but it doesn't solve the problem =\
mh00h commented on 2020-07-07 22:05 (UTC)
Maybe it's in alpha. http://www.w1hkj.com/alpha/fldigi/
dviktor commented on 2020-07-07 21:57 (UTC)
@mhooh could you please provide a link? I can't find any info in git...
mh00h commented on 2020-07-07 21:52 (UTC)
A new release came out today that is supposed to fix the font issue (4.1.13.24). Please could someone update this PKGBUILD to assist us with confirming the patch?
mh00h commented on 2020-07-07 17:01 (UTC)
I have the same problem and have traced it back to having too many fonts. Someone else has run into this too (https://primalcortex.wordpress.com/2019/03/02/fldigi-slow-startup-on-linux/?unapproved=18496&moderation-hash=4ce7ad0633dd1678f01be7050c5122c2#comment-18496). Can you confirm if this applies to you?
not_anonymous commented on 2020-07-07 15:34 (UTC)
Runs fb here om....both from the command line and from the "desktop" file. Namcap is happy too, although there could be a missing dep. I'd sure like to know more about exactly what the problem might be. (i.e. Is it the PKGBUILD, or is it something upstream, or is it local to your situation.) To wit;
Perhaps you could try this: https://sourceforge.net/p/fldigi/wiki/linux_debug_howto/
dviktor commented on 2020-07-07 09:56 (UTC)
Can't start application. No output in console and no GUI is shown
petris commented on 2020-05-08 16:30 (UTC)
@not_anonymous I just wanted to mention that it's also possible to build this package directly from the git repository (https://sourceforge.net/p/fldigi/fldigi/ci/master/tree/) by using the pkgver as the tag, for instance:
source=("${pkgname}::git+https://git.code.sf.net/p/fldigi/${pkgname}#tag=v${pkgver}")
...then it won't matter whether the author removes the tar files on update or not; it will continue working with git.
The only other change that would need to be made with this is adding "autoreconf --install" before calling "./configure" since the configure script appears to be generated prior to packaging up the release tar.
not_anonymous commented on 2020-05-04 15:58 (UTC) (edited on 2020-05-04 16:00 (UTC) by not_anonymous)
Updated several times since the comment below.... others have used the flag it out-of-date to get an update to happen; and that generally within a few days. (Sigh)
freaknils commented on 2020-03-18 06:47 (UTC)
Hi could you please update the PKGBUILD? Otherwise disown this package.
Thanks!
djringjr commented on 2020-01-26 19:59 (UTC)
Edit PKGBUILD and change these lines:
pkgver=4.1.09
sha512sums=('b4c284f599f7985205c8198df32f02fade55bfba6c4630b0c385f9f2d734ef0be11b5620e73324d88a5d5dfc4258c44c8e1759a57cd8da77186bb7d4277e1503')
ra1nb0w commented on 2020-01-20 08:10 (UTC)
the author deletes the old versions. Now it is 4.1.09. if you want the old one see http://distfiles.macports.com/fldigi/
mh00h commented on 2020-01-20 02:52 (UTC)
ERROR: Failure while downloading http://w1hkj.com/files/fldigi/fldigi-4.1.08.tar.gz
ra1nb0w commented on 2019-12-12 11:14 (UTC)
This and flrig should be on repo community or extra like any other distro. what is the impediment?
anyway, thanks for supporting it.
ve7it commented on 2019-08-10 23:28 (UTC) (edited on 2019-08-10 23:33 (UTC) by ve7it)
package is flagged as out of date and fails installation as the 4.1.06 version is no longer available. Until the repository is updated, you can manually edit your pkgbld file as follows:
to build fldigi 4.1.07 using fldigi 4.1.06-1 pkgbld: change pkgver=4.1.06 to pkgver=4.1.07 change sha512sums=('fc3ef66e9ce8c231af27d17f098e1767ba35038afac124be2a1db846246bf2e6d86ba078cd82e28d73b7389079eff87545c2f3e81bef95c525b90a8886c612be') to
sha512sums=('61fa649e589e6d34515e3d7f2f10098ac9e876d04a22d344a8e21f4dc8fc8bcf568e5d64f334a245923492c573175bfff75d39f81dbf49a808132660f02d792b')
this worked for me on 10 Aug 2019
nl13067 commented on 2019-04-21 21:28 (UTC)
4.1.03 released
thedanbob commented on 2019-03-24 01:12 (UTC)
The only fltk-related packages I've installed are this one and flrig.
AxPU commented on 2019-03-21 22:54 (UTC)
Well I still face the same problem. Compiling and installing is fine but it crashes when I run it. If it runs on your end, maybe the error is on my install. Have you installed any fltk packages via AUR?
Updating the AUR Package and looking for feedback. If it crahes you can always restore the previous version...
thedanbob commented on 2019-03-21 01:20 (UTC)
FWIW, I was able to install and run 4.1.01 successfully with no changes to the package script (besides version and shasum of course). Maybe the latest version of fltk fixed the issue?
AxPU commented on 2019-03-12 21:11 (UTC)
Same story. The reason for the crash might not even be in fltk but due to some compiler flag error.
I found similar error reports all over the net but not yet a solution. Ideas welocme!
pegasus commented on 2019-03-12 17:45 (UTC)
4.1.01 released http://w1hkj.com/files/fldigi/fldigi-4.1.01.tar.gz
AxPU commented on 2019-02-15 09:15 (UTC)
Version 4.1.00 does build fine but crash on startup du to some fltk error. I'm investigating!
ganthore commented on 2018-08-31 14:42 (UTC)
Please bump the version to 4.0.18: https://github.com/ganthore/arch-fldigi/blob/master/PKGBUILD
numinit commented on 2018-01-29 00:18 (UTC)
4.0.15 is now out.
http://w1hkj.com/files/fldigi/fldigi-4.0.15.tar.gz
AxPU commented on 2018-01-18 21:29 (UTC)
The fldigi site says "Do not user version 4.0.14!" The sources for the current AUR package 4.0.13 are not easily available too so we have to wait for the next version it seems.
I'm not yet sure regarding the dependencies. I did check that in the past but it might have changed. Will have a closer look but that may take a bit longer.
not_anonymous commented on 2018-01-05 11:52 (UTC)
With the current version and PKGBUILD; the resulting binary requires 'libpulse' to be added to the deps array. ALSO; libsamplerate is already in the dep. tree, so it is redundant in the deps. array. (It is supplied through portaudio.) FINALLY; hamlib seems to be required in the dep array. (In fact it may not be needed. I am not sure on this at this time, as I have not tested a compile without hamlib extent.)
kbeckmann commented on 2017-10-19 16:55 (UTC)
AxPU commented on 2017-06-27 19:49 (UTC)
petris commented on 2017-06-25 14:44 (UTC)
not_anonymous commented on 2017-02-08 17:17 (UTC) (edited on 2017-02-08 20:30 (UTC) by not_anonymous)
dpello commented on 2017-02-03 12:12 (UTC)
lagagnon commented on 2016-12-12 03:22 (UTC)
commented on 2016-12-10 07:14 (UTC)
int_0xFF commented on 2016-08-07 22:41 (UTC)
maze commented on 2016-02-14 08:28 (UTC)
AxPU commented on 2016-01-26 21:41 (UTC)
ronoverdrive commented on 2016-01-23 19:24 (UTC)
ronoverdrive commented on 2016-01-06 23:31 (UTC)
phillid commented on 2015-11-22 02:59 (UTC)
AxPU commented on 2015-03-24 19:58 (UTC)
AxPU commented on 2014-12-08 01:11 (UTC)
AxPU commented on 2014-12-08 01:00 (UTC)
rcf commented on 2014-12-02 22:51 (UTC)
AxPU commented on 2014-11-23 21:05 (UTC)
minorsecond commented on 2014-11-23 00:00 (UTC)
ormandj commented on 2014-10-31 00:36 (UTC)
AxPU commented on 2014-10-30 20:11 (UTC)
AxPU commented on 2014-10-29 23:23 (UTC)
AxPU commented on 2014-02-02 20:55 (UTC)
AxPU commented on 2013-11-18 23:53 (UTC)
adx commented on 2013-09-08 17:03 (UTC)
AxPU commented on 2013-09-03 22:41 (UTC)
chuser commented on 2013-08-13 09:58 (UTC)
u2ix commented on 2013-06-19 21:39 (UTC)
Hibou commented on 2013-06-19 03:29 (UTC)
swiftgeek commented on 2013-03-01 23:18 (UTC)
radio_rogal commented on 2012-12-23 19:03 (UTC)
qs9rx commented on 2012-12-20 23:10 (UTC)
lagagnon commented on 2012-11-28 23:55 (UTC)
commented on 2012-08-23 16:09 (UTC)
commented on 2012-01-24 02:45 (UTC)
commented on 2011-11-11 05:30 (UTC)
commented on 2011-11-11 04:43 (UTC)
commented on 2011-11-11 04:42 (UTC)
commented on 2011-11-11 02:41 (UTC)
radio_rogal commented on 2011-11-07 20:12 (UTC)
commented on 2011-11-07 15:23 (UTC)
commented on 2011-07-20 12:43 (UTC)
commented on 2011-07-19 10:16 (UTC)
commented on 2011-07-13 12:28 (UTC)
radio_rogal commented on 2011-07-06 19:36 (UTC)
commented on 2011-07-06 16:39 (UTC)
radio_rogal commented on 2011-06-22 21:28 (UTC)
Frikilinux commented on 2011-06-21 16:01 (UTC)
commented on 2011-05-28 08:08 (UTC)
radio_rogal commented on 2011-05-23 05:56 (UTC)
Frikilinux commented on 2011-05-22 22:12 (UTC)
radio_rogal commented on 2011-04-05 21:49 (UTC)
commented on 2011-04-05 19:57 (UTC)
radio_rogal commented on 2011-03-30 05:57 (UTC)
commented on 2011-03-26 09:38 (UTC)
radio_rogal commented on 2010-11-30 21:56 (UTC)
radio_rogal commented on 2010-09-21 06:21 (UTC)
AxPU commented on 2010-08-03 15:41 (UTC)
AxPU commented on 2010-08-03 15:30 (UTC)
radio_rogal commented on 2010-06-14 20:57 (UTC)
commented on 2010-06-13 18:26 (UTC)