|
I compile from source fldigi 4.2.04 in my Raspberry Pi, Bullseye 32 bit. There are some warnings, but at the end the compile and installation works.
But when I run the software, after the configuration wizard it crashes.
The log file in the .fldigi folder is empty, so I cannot share any info.
The step followed to compile it, are described in this page
I use hamlib 4.6 beta.
If I download the fldigi available on the Debian repository, v.4.1.18, it works well but uses hamlib 4.0.4 and I need the 4.6.
Can someone help me to have fldigi working?
|
I recommend this link as it's what I use and works every time. I've been compiling on my Pi for years.
toggle quoted message
Show quoted text
On Apr 9, 2024, at 13:25, Johnny, IZ8EWD via < js.slave@...> wrote:
I compile from source fldigi 4.2.04 in my Raspberry Pi, Bullseye 32 bit. There are some warnings, but at the end the compile and installation works.
But when I run the software, after the configuration wizard it crashes.
The log file in the .fldigi folder is empty, so I cannot share any info.
The step followed to compile it, are described in this page
I use hamlib 4.6 beta.
If I download the fldigi available on the Debian repository, v.4.1.18, it works well but uses hamlib 4.0.4 and I need the 4.6.
Can someone help me to have fldigi working?
|
Looking at your link it doesn't mention the libraries that are probably missing. Following the details on the link I sent and you'll see what I mean.
toggle quoted message
Show quoted text
I recommend this link as it's what I use and works every time. I've been compiling on my Pi for years.
On Apr 9, 2024, at 13:25, Johnny, IZ8EWD via < js.slave@...> wrote:
I compile from source fldigi 4.2.04 in my Raspberry Pi, Bullseye 32 bit. There are some warnings, but at the end the compile and installation works.
But when I run the software, after the configuration wizard it crashes.
The log file in the .fldigi folder is empty, so I cannot share any info.
The step followed to compile it, are described in this page
I use hamlib 4.6 beta.
If I download the fldigi available on the Debian repository, v.4.1.18, it works well but uses hamlib 4.0.4 and I need the 4.6.
Can someone help me to have fldigi working?
|
If I use apt build-dep as suggested in the fldigi wiki, it install also an old version of libhamlib4 and I don't want to use it.
|
If you can find a newer one then can't you install that to replace the older one?
Please post the errors you got in the "make" so we can see the issues.
toggle quoted message
Show quoted text
On Apr 9, 2024, at 15:13, Johnny, IZ8EWD via < js.slave@...> wrote:
If I use apt build-dep as suggested in the fldigi wiki, it install also an old version of libhamlib4 and I don't want to use it.
|
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.
|
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
|
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.
|
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.
|
Sorry, another question.
fldigi needs static hamlib? Because usually i compile only the shared libraries in order to short the computation time.
|
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.
|
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.
|
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.
|
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.
|
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.
|
I follow the previous suggestions but nothing to do. Compile is ok, but fldigi crashes after the configuration wizard.
Attached the config.log
|
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
|
And attached is the output of make, with several warnings
|
|
|
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
|
Dave, W1HKJ