Tom Hughes wrote:
> Commit history explains:
>
>https://sourceware.org/git/?p=glibc.git;a=commit;h=12cbde1da
For what it's worth, I think this is a completely pointless incompatibility.
It costs almost nothing to maintain this function (and in fact they have to
do it anyway for old binaries
solved now with this patch:
diff --git a/eit.c b/eit.c
index 50d8229..82294dc 100644
--- a/eit.c
+++ b/eit.c
@@ -391,7 +391,9 @@ cTDT::cTDT(const u_char *Data)
if (abs(diff) > MAX_TIME_DIFF) {
mutex.Lock();
if (abs(diff) > MAX_ADJ_DIFF) {
-if (stime(&dvbtim) == 0)
+t
Yup. To be precise, quoting from the NEWS entry added for the change:
* The obsolete function stime is no longer available to newly linked
binaries and it has been removed from header. This function
has been deprecated in favor of clock_settime.
__
ok, that means
stime () has been deprecated in glibc 2.31 and replaced with clock_settime ().
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://doc
On 13/12/2019 07:46, Martin Gansser wrote:
was the stime () declaration moved in another header file ?
What is the reason for this.
Commit history explains:
https://sourceware.org/git/?p=glibc.git;a=commit;h=12cbde1da
But summary seems to be, as was said when the same question
was asked ye
was the stime () declaration moved in another header file ?
What is the reason for this.
Regards
Martin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
h
