On 2025-05-01 06:29, Christian Franke wrote:
Jon Turney wrote:
On 30/04/2025 12:33, Christian Franke wrote:
Christian Franke wrote:
Jon Turney wrote:
On 28/04/2025 16:43, Christian Franke wrote:
A followup to:
https://sourceware.org/pipermail/cygwin-patches/2025q2/013678.html
Thanks!
The
Jon Turney wrote:
On 30/04/2025 12:33, Christian Franke wrote:
Christian Franke wrote:
Jon Turney wrote:
On 28/04/2025 16:43, Christian Franke wrote:
A followup to:
https://sourceware.org/pipermail/cygwin-patches/2025q2/013678.html
Thanks!
The SUS page for clock_settime() contains the foll
On 30/04/2025 12:33, Christian Franke wrote:
Christian Franke wrote:
Jon Turney wrote:
On 28/04/2025 16:43, Christian Franke wrote:
A followup to:
https://sourceware.org/pipermail/cygwin-patches/2025q2/013678.html
Thanks!
The SUS page for clock_settime() contains the following text:
[EINV
Christian Franke wrote:
Jon Turney wrote:
On 28/04/2025 16:43, Christian Franke wrote:
A followup to:
https://sourceware.org/pipermail/cygwin-patches/2025q2/013678.html
Thanks!
The SUS page for clock_settime() contains the following text:
[EINVAL]
The tp argument specified a nanosecond
Jon Turney wrote:
On 28/04/2025 16:43, Christian Franke wrote:
A followup to:
https://sourceware.org/pipermail/cygwin-patches/2025q2/013678.html
Thanks!
The SUS page for clock_settime() contains the following text:
[EINVAL]
The tp argument specified a nanosecond value less than zero or
On 28/04/2025 16:43, Christian Franke wrote:
A followup to:
https://sourceware.org/pipermail/cygwin-patches/2025q2/013678.html
Thanks!
The SUS page for clock_settime() contains the following text:
[EINVAL]
The tp argument specified a nanosecond value less than zero or greater than or equ
A followup to:
https://sourceware.org/pipermail/cygwin-patches/2025q2/013678.html
--
Regards,
Christian
From bbdaf4cfb487b7d134b5fda00447f77b6d0cfd27 Mon Sep 17 00:00:00 2001
From: Christian Franke
Date: Mon, 28 Apr 2025 17:27:28 +0200
Subject: [PATCH] Cygwin: clock_settime: fail with EINVAL