From: Giacomo Tesio <giacomo@tesio.it>
To: "newlib@sourceware.org" <newlib@sourceware.org>,
Giacomo Tesio <giacomo@tesio.it>
Subject: unknown type name 'cpu_set_t' in newlib/libc/include/sched.h
Date: Mon, 12 Aug 2019 09:12:00 -0000 [thread overview]
Message-ID: <CAHL7psHs8gOfYdkftAPQYWFtWr3f9h11KrmBPLrEi-aFEgZiUQ@mail.gmail.com> (raw)
In-Reply-To: <20190812075243.GC11632@calimero.vinschen.de>
On Monday, 12 August 2019, Corinna Vinschen <vinschen@redhat.com> wrote:
> On Aug 12 02:28, Giacomo Tesio wrote:
>> Hello everybody,
>>
>> apparently commit 383e19ca552234fa9af47e80cb00d843a96de9e3 moved the
>> cpu_set_t typedef from newlib/libc/include/sched.h to cygwin specific
>> stuff, but left a few functions using such type behind and
>> unprotected.
>>
>> Is it intended?
>
> Probably not, if it leads to build errors on non-Cygwin, non-RTEMS.
>
> Does it?
Yes it produce build errore in my os port because I don't have it defined
anywhere.
You could either protect the functions with an ifdef or move back the
typedef to sched.h
Giacomo
next prev parent reply other threads:[~2019-08-12 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 0:28 Giacomo Tesio
2019-08-12 7:52 ` Corinna Vinschen
2019-08-12 9:12 ` Giacomo Tesio [this message]
2019-08-12 10:16 ` Corinna Vinschen
2019-08-12 23:47 ` Giacomo Tesio
2019-08-12 12:42 ` Joel Sherrill
2019-08-12 17:01 ` Giacomo Tesio
2019-08-12 18:13 ` Joel Sherrill
2019-08-13 5:00 ` Sebastian Huber
2019-08-13 7:39 ` 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=CAHL7psHs8gOfYdkftAPQYWFtWr3f9h11KrmBPLrEi-aFEgZiUQ@mail.gmail.com \
--to=giacomo@tesio.it \
--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).