public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: newlib@sourceware.org
Subject: Re: [PATCH] Cygwin: signal.cc: Include <unistd.h>
Date: Thu, 12 May 2022 08:48:12 -0600	[thread overview]
Message-ID: <0856b9dc-ef50-234e-9327-32eff276dda4@SystematicSw.ab.ca> (raw)
In-Reply-To: <YnzJaQLNgsLVKFRX@calimero.vinschen.de>

On 2022-05-12 02:46, Corinna Vinschen wrote:
> On May 12 10:22, Sebastian Huber wrote:
>> On 12/05/2022 10:14, Corinna Vinschen wrote:
>>>>    sleep (unsigned int seconds)
>>>>    {
>>>>      struct timespec req, rem;
>>>> @@ -174,7 +175,7 @@ sleep (unsigned int seconds)
>>>>      return 0;
>>>>    }
>>>> -extern "C" unsigned int
>>>> +int
>>>>    usleep (useconds_t useconds)
>>> Good catch, otherwise, thank you!  I'd prefer if you push just the
>>> type change and keep the extern "C" as a marker for exported functions.
>>
>> Ok, what about the unistd.h include?
> 
> Let's keep it.  It might help to uncover other issues in future.

Shouldn't these Cygwin winsup patches be posted separately to
cygwin-patches rather than newlib, once any newlib patches they depend 
on have been accepted.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2022-05-12 14:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12  6:43 Sebastian Huber
2022-05-12  8:14 ` Corinna Vinschen
2022-05-12  8:22   ` Sebastian Huber
2022-05-12  8:46     ` Corinna Vinschen
2022-05-12 14:48       ` Brian Inglis [this message]
2022-05-12 16:05         ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0856b9dc-ef50-234e-9327-32eff276dda4@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=newlib@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).