On Dec 1 08:49, Brian Inglis wrote:
> On 2018-12-01 02:53, Corinna Vinschen wrote:
> > On Nov 30 21:27, Brian Inglis wrote:
> >> $ head /{etc,usr/lib}/os-release
> >> ==> /etc/os-release <==
> >> PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
> >> NAME="Debian GNU/Linux"
> >> VERSION_ID="9"
> >> VERSI
On 2018-12-01 02:53, Corinna Vinschen wrote:
> On Nov 30 21:27, Brian Inglis wrote:
>> On 2018-11-30 05:56, Corinna Vinschen wrote:
>>> On Nov 30 07:43, James E. King III wrote:
On Fri, Nov 30, 2018 at 7:23 AM Corinna Vinschen wrote:
> On Nov 29 17:38, James E. King III wrote:
>> On Th
On Nov 30 21:27, Brian Inglis wrote:
> On 2018-11-30 05:56, Corinna Vinschen wrote:
> > On Nov 30 07:43, James E. King III wrote:
> >> On Fri, Nov 30, 2018 at 7:23 AM Corinna Vinschen wrote:
> >>> On Nov 29 17:38, James E. King III wrote:
> On Thu, Nov 29, 2018 at 5:18 AM Corinna Vinschen wrot
On 2018-11-30 05:56, Corinna Vinschen wrote:
> On Nov 30 07:43, James E. King III wrote:
>> On Fri, Nov 30, 2018 at 7:23 AM Corinna Vinschen wrote:
>>> On Nov 29 17:38, James E. King III wrote:
On Thu, Nov 29, 2018 at 5:18 AM Corinna Vinschen wrote:
> I created a patch and uploaded new dev
On Nov 30 07:43, James E. King III wrote:
> On Fri, Nov 30, 2018 at 7:23 AM Corinna Vinschen
> wrote:
> >
> > On Nov 29 17:38, James E. King III wrote:
> > > On Thu, Nov 29, 2018 at 5:18 AM Corinna Vinschen
> > > > I created a patch and uploaded new developer snapshots to
> > > > https://cygwin.co
On Fri, Nov 30, 2018 at 7:23 AM Corinna Vinschen
wrote:
>
> On Nov 29 17:38, James E. King III wrote:
> > On Thu, Nov 29, 2018 at 5:18 AM Corinna Vinschen
> > > I created a patch and uploaded new developer snapshots to
> > > https://cygwin.com/snapshots/ Please give them a try.
> >
> > This fixed
On Nov 29 17:38, James E. King III wrote:
> On Thu, Nov 29, 2018 at 5:18 AM Corinna Vinschen
> > I created a patch and uploaded new developer snapshots to
> > https://cygwin.com/snapshots/ Please give them a try.
>
> This fixed the issue for me. What's the best way to detect cygwin
> with this s
On Thu, Nov 29, 2018 at 5:18 AM Corinna Vinschen
wrote:
>
> On Nov 26 17:46, Corinna Vinschen wrote:
> > On Nov 26 10:47, James E. King III wrote:
> > > On Mon, Nov 26, 2018 at 10:35 AM Corinna Vinschen
> > > wrote:
> > > >
> > > > On Nov 25 09:01, James E. King III wrote:
> > > > > I have isolat
On Nov 26 17:46, Corinna Vinschen wrote:
> On Nov 26 10:47, James E. King III wrote:
> > On Mon, Nov 26, 2018 at 10:35 AM Corinna Vinschen
> > wrote:
> > >
> > > On Nov 25 09:01, James E. King III wrote:
> > > > I have isolated a problem in pthread_cond_timedwait when the condattr
> > > > is used
On Nov 26 10:47, James E. King III wrote:
> On Mon, Nov 26, 2018 at 10:35 AM Corinna Vinschen
> wrote:
> >
> > On Nov 25 09:01, James E. King III wrote:
> > > I have isolated a problem in pthread_cond_timedwait when the condattr
> > > is used to set the clock type to CLOCK_MONOTONIC. In this case
On Mon, Nov 26, 2018 at 10:35 AM Corinna Vinschen
wrote:
>
> On Nov 25 09:01, James E. King III wrote:
> > I have isolated a problem in pthread_cond_timedwait when the condattr
> > is used to set the clock type to CLOCK_MONOTONIC. In this case even
> > though a target time point in the future is
On Nov 25 09:01, James E. King III wrote:
> I have isolated a problem in pthread_cond_timedwait when the condattr
> is used to set the clock type to CLOCK_MONOTONIC. In this case even
> though a target time point in the future is specified, the call
> returns ETIMEDOUT but a subsequent call to
> c
I have isolated a problem in pthread_cond_timedwait when the condattr
is used to set the clock type to CLOCK_MONOTONIC. In this case even
though a target time point in the future is specified, the call
returns ETIMEDOUT but a subsequent call to
clock_gettime(CLOCK_MONOTONIC) shows the desired time
13 matches
Mail list logo
