mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Willy Tarreau <w@1wt.eu>
Subject: [PATCH 0/4] tools/nolibc: assorted fixes and small updates
Date: Fri, 20 Jun 2025 12:02:47 +0200	[thread overview]
Message-ID: <20250620100251.9877-1-w@1wt.eu> (raw)

Trying to port a program to nolibc triggered a few trivial errors that
are worth being addressed:
  - inttypes.h is missing, while being generally recommended over stdint.h
    for being more portable. Here we add it, which simply includes stdint.h.

  - sys/select.h is supposed to be where struct fd_set and FD_CLR() etc
    are defined. Till now it was still in types.h. Let's create the file
    and move these definitions there.

  - memchr() was still missing, thus a trivial one was added.

Finally the help message from "make help" reported an inaccurate
installation path, omitting the dependency on $OUTPUT. This was
fixed as well.

Willy Tarreau (4):
  tools/nolibc: fix misleading help message regarding installation path
  tools/nolibc: add the more portable inttypes.h
  tools/nolibc: move FD_* definitions to sys/select.h
  tools/nolibc: add missing memchr() to string.h

 tools/include/nolibc/Makefile                |  4 +-
 tools/include/nolibc/inttypes.h              |  8 +++
 tools/include/nolibc/string.h                | 15 ++++++
 tools/include/nolibc/sys/select.h            | 56 ++++++++++++++++++++
 tools/include/nolibc/types.h                 | 48 +----------------
 tools/testing/selftests/nolibc/nolibc-test.c |  2 +
 6 files changed, 85 insertions(+), 48 deletions(-)
 create mode 100644 tools/include/nolibc/inttypes.h
 create mode 100644 tools/include/nolibc/sys/select.h

-- 
2.17.5


             reply	other threads:[~2025-06-20 10:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20 10:02 Willy Tarreau [this message]
2025-06-20 10:02 ` [PATCH 1/4] tools/nolibc: fix misleading help message regarding installation path Willy Tarreau
2025-06-20 10:02 ` [PATCH 2/4] tools/nolibc: add the more portable inttypes.h Willy Tarreau
2025-06-20 10:02 ` [PATCH 3/4] tools/nolibc: move FD_* definitions to sys/select.h Willy Tarreau
2025-06-21  8:21   ` Thomas Weißschuh
2025-06-22  7:19     ` Willy Tarreau
2025-06-22 19:58       ` Thomas Weißschuh
2025-06-23  2:56         ` Willy Tarreau
2025-06-29  8:46           ` Willy Tarreau
2025-06-29  8:53             ` Thomas Weißschuh
2025-06-29  9:25               ` Willy Tarreau
2025-06-29  9:37                 ` Thomas Weißschuh
2025-06-29  9:40                   ` Willy Tarreau
2025-06-29 15:10                     ` Willy Tarreau
2025-06-29 15:54                       ` Thomas Weißschuh
2025-06-29 16:08                         ` Willy Tarreau
2025-06-29 16:14                           ` Thomas Weißschuh
2025-06-29 16:19                             ` Willy Tarreau
2025-06-29 16:27                               ` Thomas Weißschuh
2025-06-29 17:56                                 ` Willy Tarreau
2025-06-20 10:02 ` [PATCH 4/4] tools/nolibc: add missing memchr() to string.h Willy Tarreau
2025-06-21  8:27   ` Thomas Weißschuh
2025-06-21  8:42     ` Willy Tarreau
2025-06-22 19:56       ` Thomas Weißschuh
2025-06-23  3:01         ` Willy Tarreau

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=20250620100251.9877-1-w@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.weissschuh@linutronix.de \
    /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

all inboxes | Powered by JetHome®