Joshua Wood writes:
> Ran into the same thing on modern Slackware. GTimeVal has been deprecated
> for a while now.
Can you post what versions of gtk2 and glib2 you have?
When you build xlog against those, does it fail, and are you doing
something to let the deprecated warnings be warnings and
On 2020-02-28 18:57, Andy Stewart wrote:
I just checked my system, and I have gtk2 2.24.32-1ubuntu1 installed.
For glib2, I have version 2.56.4-0ubuntu0.18.04.4.
I rebuilt the source code and saw no issues with these revs on Ubuntu
18.04.4.
Thanks for checking.
Your glib2 is quite old, but
I just filed a bug about this; building 2.0.17 on NetBSD with pkgsrc
results in a GTK deprecation warning which with -Werror is fatal.
I wonder what the path/timeframe is from the 2.0.18 beta to the actual
2.0.18 release. (pkgsrc only packages releases, unless we conclude that
an upstream is so
Andy Stewart writes:
> On 2/28/20 9:39 AM, Greg Troxel wrote:
>> I just filed a bug about this; building 2.0.17 on NetBSD with pkgsrc
>> results in a GTK deprecation warning which with -Werror is fatal.
>>
>> I wonder what the path/timeframe is from the 2.0.18 b
Andy Stewart writes:
>>> adif3.c: In function ‘adif_qso_append’:
>>> adif3.c:527:4: error: ‘strncpy’ source argument is the same as destination
>>> [-Werror=restrict]
>>> strncpy (qfield, q[fld], qfield_len); // Save the string from start
>>> to space, not including the space.
>>>
Andy Stewart writes:
> Let me take another look at the code, and I'll implement it in a different
> way.
>
> Greg: do you have a way to reproduce this problem? If so, we can
> resolve the issue on the side, at which point I'll release an updated
> version of xlog.
I have not seen this
Robert Kennedy writes:
Robert Kennedy writes:
> But I want to upgrade to the latest verson of Xlog - version 2.0.22.
> So I am trying to compile XLog 2.0.22 from source.
When I read your message I did not have version numbers paged in and
totally failed to recognize this as a new number. I
