unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Elichai Turkel <elichai.turkel@gmail.com>
Cc: Christian Brauner <christian@brauner.io>,
	 linux-api@vger.kernel.org,
	 libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Missing size_t declaration in UAPI
Date: Sat, 09 Nov 2019 13:27:30 +0100	[thread overview]
Message-ID: <87d0e19qvh.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CALN7hC+YmHGpniNKBiD03cBnTyO+cqXhrVvE7SdtgEb7GkG-LQ@mail.gmail.com> (Elichai Turkel's message of "Sat, 9 Nov 2019 13:52:11 +0200")

* Elichai Turkel:

> I'm proposing to move `linux/tools/include/nolibc/nolibc.h` to the
> UAPI interface.
> It would then be included in `linux/types.h`
> Would love feedback before I work on a patch.

I do not think nolibc.h is a good starting point.  The header is
pretty much incompatible with everything, including multiple
translation units that include it, so including it from
<linux/types.h> will not work.

>>> Currently compiling the following program fails:
>>> ```
>>> #include "linux/signal.h"
>>> void main(void){}
>>> ```
>>> Because of `./asm/signal.h:127:2: error: unknown type name ‘size_t’`.
>>>
>>> I tried patching with `#include <stddef.h>` but there's a local file
>>> with the same name overriding the include.

<stddef.h> is expected to be provided by the compiler. It's probably
easier to fix your build environment.

  parent reply	other threads:[~2019-11-09 12:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALN7hCJRe1uL6pd+VwgzDt=5giMVjvX+YpF28f5qbLOVCZf4GQ@mail.gmail.com>
     [not found] ` <04EB5627-FD42-4397-995B-FDF051CFCFB5@brauner.io>
2019-11-09 11:52   ` Missing size_t declaration in UAPI Elichai Turkel
2019-11-09 12:15     ` Elichai Turkel
2019-11-09 12:27     ` Florian Weimer [this message]
     [not found]       ` <CALN7hC+QS=PJLvtH4k8paVae6PzLdAQJXyU64gUxXu-ULMKvng@mail.gmail.com>
     [not found]         ` <87sgmv5s8l.fsf@mid.deneb.enyo.de>
2020-01-29 11:41           ` Elichai Turkel

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

  List information: https://www.gnu.org/software/libc/involved.html

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

  git send-email \
    --in-reply-to=87d0e19qvh.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=christian@brauner.io \
    --cc=elichai.turkel@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-api@vger.kernel.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).