All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: shuah@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] tools/nolibc: add the more portable inttypes.h
Date: Sun, 2 Nov 2025 12:18:55 +0100	[thread overview]
Message-ID: <20251102111855.GA24871@1wt.eu> (raw)
In-Reply-To: <cc94509b-a87b-410e-a601-6381c2a2e6e1@t-8ch.de>

On Sun, Nov 02, 2025 at 12:04:01PM +0100, Thomas Weißschuh wrote:
> On 2025-11-02 11:46:09+0100, Willy Tarreau wrote:
> > It's often recommended to only use inttypes.h instead of stdint.h for
> > portability reasons since the former is always present when the latter
> > is present, but not conversely, and the former includes the latter. Due
> > to this some simple programs fail to build when including inttypes.h.
> > Let's add one that simply includes stdint.h to better support these
> > programs.
> > 
> > Signed-off-by: Willy Tarreau <w@1wt.eu>
> > ---
> >  tools/include/nolibc/Makefile   | 1 +
> >  tools/include/nolibc/inttypes.h | 8 ++++++++
> >  2 files changed, 9 insertions(+)
> >  create mode 100644 tools/include/nolibc/inttypes.h
> 
> I think this should also interact with the big nolibc.h.
> Both being included from it and including it itself, to follow the
> generally used pattern.
> 

You mean you'd prefer "include nolibc.h" from inttypes and
"include inttypes" from nolibc, that's it ?

Willy

  reply	other threads:[~2025-11-02 11:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-02 10:46 [PATCH v2 0/4] tools/nolibc: assorted fixes and small updates Willy Tarreau
2025-11-02 10:46 ` [PATCH v2 1/4] tools/nolibc: fix misleading help message regarding installation path Willy Tarreau
2025-11-02 11:03   ` Thomas Weißschuh
2025-11-02 10:46 ` [PATCH v2 2/4] tools/nolibc: add the more portable inttypes.h Willy Tarreau
2025-11-02 11:04   ` Thomas Weißschuh
2025-11-02 11:18     ` Willy Tarreau [this message]
2025-11-02 11:41       ` Thomas Weißschuh
2025-11-02 10:46 ` [PATCH v2 3/4] tools/nolibc: add missing memchr() to string.h Willy Tarreau
2025-11-02 11:10   ` Thomas Weißschuh
2025-11-02 10:46 ` [PATCH v2 4/4] tools/nolibc: provide the portable sys/select.h Willy Tarreau
2025-11-02 12:51   ` Thomas Weißschuh

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=20251102111855.GA24871@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=shuah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.