Re: Problemm running fldigi on Raspberry Pi
Start fldigi from the command line and once it
crashes, you should see from crash details and/or a core dump.?
Post those details here on this thread.?
If you have the advanced skillset and If you're not getting a
coredump, consider enabling core dumping on your operating system
and send us the details.? This means you can enable coredumps on
your system, rebuild Fldigi with debugging objects and DISABLE all
optimizations.? Then run the instrumented version of Fldigi, get
it to core dump, then send the decoded crashdump details (usually
done using gdb) to the list here.
--David
KI6ZHD
On 04/10/2024 11:13 AM, Johnny, IZ8EWD
via groups.io wrote:
toggle quoted message
Show quoted text
I follow the previous suggestions but nothing to do.
Compile is ok, but fldigi crashes after the configuration wizard.
Attached the config.log
|
Re: Problemm running fldigi on Raspberry Pi
Which version of the Pi ?
David
On 4/10/24 14:35, Johnny, IZ8EWD via
groups.io wrote:
toggle quoted message
Show quoted text
And attached is the output of make, with several warnings
|
Re: Problemm running fldigi on Raspberry Pi
And attached is the output of make, with several warnings
|
Re: Problemm running fldigi on Raspberry Pi
This ./config is strange:
checking for flxmlrpc >= 1.0.1... no
checking for libmbedtls >= 2.16.0... no
and flidigi use internal lib
? libmbedtls .................. internal lib
? flxmlrpc .................... internal lib
If I check with apt
libflxmlrpc-dev/oldstable,now 0.1.4-5+b6 armhf [installed]
? fldigi suite XmlRpc library - Development files
libflxmlrpc1/oldstable,now 0.1.4-5+b6 armhf [installed,automatic]
? fldigi suite XmlRpc library
libmbedtls-dev/oldstable,now 2.16.9-0.1 armhf [installed]
? lightweight crypto and SSL/TLS library - development files
libmbedtls12/oldstable,now 2.16.9-0.1 armhf [installed,automatic]
? lightweight crypto and SSL/TLS library - tls library
|
Re: Problemm running fldigi on Raspberry Pi
I follow the previous suggestions but nothing to do. Compile is ok, but fldigi crashes after the configuration wizard.
Attached the config.log
|
fldigi 4.2.04.11 developer version posted at
commit 0a2519ec3d2d5e44501724e3b989908268bf5777
Author: dave-w1hkj <w1hkj@...>
Date: Wed Apr 10 11:29:46 2024 -0500
Default language
* add code to force default language to be English
commit 0313f1a2e64632e322533621de878fc5cf10054a
Author: dave-w1hkj <w1hkj@...>
Date: Wed Apr 10 11:16:36 2024 -0500
RSID Min Bandwidth
* add user adjustable bandwidth for minimum RsID detection
range.
* display RsID detection zone on waterfall (dashed lines) when RsID
is both ON and limited to a specific bandwidth range
 color is configurable on Waterfall Display configuration tab.
73, David, W1HKJ
|
Re: Problemm running fldigi on Raspberry Pi
Hi Ken,
It sure seems to be here, at least in NE Texas. We're in our third day of rain & T-storms, 3.3" in the first 24 hours. More next week they say also, glub, glub, glub. :-)
toggle quoted message
Show quoted text
On Apr 10, 2024, at 10:19, Ken, KV5Y < kv5y@...> wrote:
Cliff,? I do not use it, just thought it might be contributing to the problem he was having, since I saw it in the command string on the website that was referenced. ? Hope Spring has arrived in Texas!! Ken ? Ken Rawlings - KV5Y
On 04/10/2024 9:11 AM MDT Cliff, AE5ZA < ae5zaham@...> wrote: ? ? Ken,? That parameter is only for 32bit RPI system. He says he is using 32 bit. If yours is 64 bit, like mine, you can't use that parameter. On Apr 10, 2024, at 09:42, Ken, KV5Y < kv5y@...> wrote:
Dave, I noticed that the procedure that he previously referenced to build fldigi has the following command extension: ? ./configure --enable-optimizations=rpi4 ? Adding this command to "./configure" causes make to error and not complete the compile, for me. ? Ken ? Ken Rawlings - KV5Y
? ? On 04/10/2024 8:30 AM MDT Dave, W1HKJ < w1hkj@...> wrote: ? ? The difference in fldigi compilation will be negligible.? Linking will be a very little bit longer, but you should be able to measure that even on the Pi.? The header files are necessary for the compilation to correctly use the hamlib API.? Memory usage should be very similar, whether using a static .a file or load the shared .so at run time.
David
On 4/10/24 09:11, Johnny, IZ8EWD via??wrote: Sorry, another question.??
fldigi needs static hamlib? Because usually i compile only the shared libraries in order to short the computation time.
|
Re: Problemm running fldigi on Raspberry Pi
Cliff,
I do not use it, just thought it might be contributing to the problem he was having, since I saw it in the command string on the website that was referenced.
?
Hope Spring has arrived in Texas!!
Ken
?
Ken Rawlings - KV5Y
On 04/10/2024 9:11 AM MDT Cliff, AE5ZA <ae5zaham@...> wrote:
?
?
Ken,
?
That parameter is only for 32bit RPI system. He says he is using 32 bit. If yours is 64 bit, like mine, you can't use that parameter.
On Apr 10, 2024, at 09:42, Ken, KV5Y < kv5y@...> wrote:
Dave,
I noticed that the procedure that he previously referenced to build fldigi has the following command extension:
?
./configure --enable-optimizations=rpi4
?
Adding this command to "./configure" causes make to error and not complete the compile, for me.
?
Ken
?
Ken Rawlings - KV5Y
?
?
On 04/10/2024 8:30 AM MDT Dave, W1HKJ < w1hkj@...> wrote:
?
?
The difference in fldigi compilation will be negligible.? Linking will be a very little bit longer, but you should be able to measure that even on the Pi.? The header files are necessary for the compilation to correctly use the hamlib API.? Memory usage should be very similar, whether using a static .a file or load the shared .so at run time.
David
On 4/10/24 09:11, Johnny, IZ8EWD via wrote:
Sorry, another question.?
fldigi needs static hamlib? Because usually i compile only the shared libraries in order to short the computation time.
|
Re: Problemm running fldigi on Raspberry Pi
Ken,
That parameter is only for 32bit RPI system. He says he is using 32 bit. If yours is 64 bit, like mine, you can't use that parameter.
toggle quoted message
Show quoted text
On Apr 10, 2024, at 09:42, Ken, KV5Y < kv5y@...> wrote:
Dave, I noticed that the procedure that he previously referenced to build fldigi has the following command extension: ? ./configure --enable-optimizations=rpi4 ? Adding this command to "./configure" causes make to error and not complete the compile, for me. ? Ken ? Ken Rawlings - KV5Y
? ? On 04/10/2024 8:30 AM MDT Dave, W1HKJ < w1hkj@...> wrote: ? ? The difference in fldigi compilation will be negligible.? Linking will be a very little bit longer, but you should be able to measure that even on the Pi.? The header files are necessary for the compilation to correctly use the hamlib API.? Memory usage should be very similar, whether using a static .a file or load the shared .so at run time.
David
On 4/10/24 09:11, Johnny, IZ8EWD via wrote: Sorry, another question.?
fldigi needs static hamlib? Because usually i compile only the shared libraries in order to short the computation time.
|
Re: Problemm running fldigi on Raspberry Pi
Dave,
I noticed that the procedure that he previously referenced to build fldigi has the following command extension:
?
./configure --enable-optimizations=rpi4
?
Adding this command to "./configure" causes make to error and not complete the compile, for me.
?
Ken
?
Ken Rawlings - KV5Y
?
?
On 04/10/2024 8:30 AM MDT Dave, W1HKJ <w1hkj@...> wrote:
?
?
The difference in fldigi compilation will be negligible.? Linking will be a very little bit longer, but you should be able to measure that even on the Pi.? The header files are necessary for the compilation to correctly use the hamlib API.? Memory usage should be very similar, whether using a static .a file or load the shared .so at run time.
David
On 4/10/24 09:11, Johnny, IZ8EWD via groups.io wrote:
Sorry, another question.
fldigi needs static hamlib? Because usually i compile only the shared libraries in order to short the computation time.
|
Re: Problemm running fldigi on Raspberry Pi
The difference in fldigi
compilation will be negligible.? Linking will be a very little
bit longer, but you should be able to measure that even on the
Pi.? The header files are necessary for the compilation to
correctly use the hamlib API.? Memory usage should be very
similar, whether using a static .a file or load the shared .so
at run time.
David
On 4/10/24 09:11, Johnny, IZ8EWD via
groups.io wrote:
toggle quoted message
Show quoted text
Sorry, another question.
fldigi needs static hamlib? Because usually i compile only the
shared libraries in order to short the computation time.
|
Re: Problemm running fldigi on Raspberry Pi
Sorry, another question.
fldigi needs static hamlib? Because usually i compile only the shared libraries in order to short the computation time.
|
fldigi 4.2.04.10 development release posted at
Latest change:
commit d93f4b89c44d0cd17e66bd926fa793f3742f51ed
Author: dave-w1hkj <w1hkj@...>
Date: Wed Apr 10 07:07:29 2024 -0500
RSID Min Bandwidth
??? * add user adjustable bandwidth for minimum RsID detection
range.
This will allow up to 16 simultaneous THOR-11 signals (channels) to
be contained in a passband of 200 to 3400 Hertz spaced at 200 Hertz
intervals.? This change is in support of the development and testing
of emergency digital communicators that can be easily interfaced to
Android devices.
73, David, W1HKJ
|
Re: Problemm running fldigi on Raspberry Pi
That is correct.? Make sure
that libudev and libxft were both included with build-dep as
those are now required libraries.
David
On 4/10/24 06:00, Johnny, IZ8EWD via
groups.io wrote:
toggle quoted message
Show quoted text
Dave,
thanks for your reply.
If I understand well, I have to use the build-dep command to be
sure that all the libraries are available.
After that I can remove the old hamlib 4.0 installed from the
Bullseye repository and replace with the latest 4.6 github
snapshot as I need.
Then proceed with fldigi compilation.
|
Re: Problemm running fldigi on Raspberry Pi
Dave,
thanks for your reply.
If I understand well, I have to use the build-dep command to be sure that all the libraries are available.
After that I can remove the old hamlib 4.0 installed from the Bullseye repository and replace with the latest 4.6 github snapshot as I need.
Then proceed with fldigi compilation.
|
Re: Problemm running fldigi on Raspberry Pi
fldigi builds without error
using the either the hamlib 4.6 archive source, or the latest
pull from the hamlib remote git repository.
As you probably already know, avoiding library conflicts is not
the responsibility of the target application, but the person
doing the compilation.
- remove all of the hamlib
library installation.? Do this using apt-get, aptitude, or
the synaptic.? You need to be sure that the .a, .so and all
header files are not on your system.
- download and install the
latest 4.6 tar.gz file, or clone the hamlib git repository
- compile and install
hamlib 4.6
./configure && make && sudo make install
The Pi build instructions:
? works
correctly on my Pi3, Pi4, and Pi5
Synaptic being used to
"remove all" references to hamlib 4.3.x
fldigi build info after
successful installation of latest hamlib built from git
repository clone:
73, David, W1HKJ
|
Re: Problemm running fldigi on Raspberry Pi
Hi Cliff,
I will post the make output asap.
Some observations:
- There was a change in the hamlib library, some reference were converted to pointers, so older version of fldigi doesn't compile. I try with the last issue of 4.1.27 and it doesn't complie.
- If I install hamlib from the Bullseye repository, I'm not able to replace it by compiling the last 4.6, applications see the ones installed by the apt, I have to remove this one to make visible the 4.6.
- Actually, when I compile fldigi using the guide I posted??, there aren't warning or errror for missing libraries.
|
Re: [winfldigi] flamp 2.2.11.14 development version posted
All builds completed on EPEL 8 through Fedora Rawhide:
Thanks, Richard
KF5OIM
|
flamp 2.2.11.14 development version posted
at
Author: kk5vd <kk5vd@...>
Date:?? Tue Apr 9 16:45:37 2024 -0500
??? Compatibility/Modem Switch
?? ?
???? * Add leading linefeed to [bxx:end] tags
???? * Add delay to allow FLDIGI the time to switch modems.
Author: kk5vd <kk5vd@...>
Date:?? Sun Mar 3 19:49:04 2024 -0600
??? Document/GUI/Header Modem/Default Modems
???? * Update User Manual for recent changes.
???? * Estimated Relay transmit time not updating on TX panel
modem change.
???? * Header Modem using interval timer RX state delay,
corrected.
???? * Olivia Modem Names to Uppercase.
???? * Remove redundant TX_SEGMENTED check.
???? * Add code for relay repeat counters, interval timer.
Author: dave-w1hkj <w1hkj@...>
Date:?? Sun Jan 7 10:20:11 2024 -0600
??? font browser
?? ?
????? * update font browser class to use std::list vice
??????? computed array size to enumerate system fonts
Author: kk5vd <kk5vd@...>
Date:?? Sun Jan 28 15:45:52 2024 -0700
??? Tabs/Relay Options/GUI/Fluid
???? * Save selected Tab panel state on exit
???? * Restore selected panel on restart.
???? * Corrected Widget Event Settings (FLUID).
???? * Add Header/Data Repeat Counters for Relay file
transmissions.
???? * Add transmit time widget for relay files.
???? * Move relay auto save checkboxes to config panel.
???? * Corrected default Olivia modem tag names.
???? * Add code to correctly restore RX panel data on file
selection changes.
Should resove the incompatibility issue? between 2.2.11 and
2.2.11.13
73, David, W1HKJ
|
Re: Minor bug - Re: [nbems] flamp 2.2.11.13 development version posted at
Bob,
I was not able to confirm the issue. However, I added a small delay to the calling code to switch the modem using FLAMP. If you have the ability to compile code you can download a snapshot of the source code here.
and test it, otherwise going to wait awhile for more possible issues before we release another development version.
Robert.
|
Dave, W1HKJ
Richard Shaw, KF5OIM