On 27/11/2020 02:40, Andy Stewart wrote:
On 11/26/20 6:36 PM, Barry Jackson wrote:
On 31/10/2020 02:55, Andy Stewart wrote:
HI Barry,
----------
Let me know if you continue to have issues.
Hi Andy,
OK I finally found time to have another look at this.
I started by rebuilding against a recent hamlib snapshot.
Hi Barry,
I need very specific details in order to attempt to reproduce this problem.
* if the xlog version is not 2.0.19, please try again with that version,
which is the latest
* Exact version of hamlib (ideally, the link from where you downloaded it)
* Exact type and version of Linux
* If you did any custom configuration when you compiled hamlib and/or
xlog, I'll need those instructions as well
* I don't have a TS-405S, so I may not be able to reproduce the problem,
but I will try.
Thanks, and 73,
Andy
Hi Andy,
I just realized that I still had not managed to send you the info you need.
I have tried three times but every time the message is rejected as spam.
I will try again now if I can remember what this is all about ;)
The best way to give you all the info you need is to point you to my
local build server repository where you will find:
The full package build log:
http://mtf.duckdns.org/pub/linux/barjac/distrib/cauldron/x86_64/log/xlog-2.0.19-2.1.mga8_bcj.src.rpm/build.0.20201126222709.log
The versioned packages comprising the build chroot:
http://mtf.duckdns.org/pub/linux/barjac/distrib/cauldron/x86_64/log/xlog-2.0.19-2.1.mga8_bcj.src.rpm/rpm_qa.0.20201126222709.log
Hamlib snapshot git# and date are in the packagename which is listed in
the packages list above, and was taken from the hamlib site as a source
tarball. Other software like klog, wsjtx, jscall, fldigi are working
fine built against it.
I am building for the imminent release of Mageia (8 aka Cauldron where
the next release is cooked up :)
I will see if this mail sends OK. If not I will put it in a tarball and
add it as an attachment and try again.
Let me know if I can help further with maybe a back trace or strace output.
Cheers,
Barry
