From: Willy Tarreau <w@1wt.eu>
To: Mark Brown <broonie@kernel.org>, "Paul E. McKenney" <paulmck@kernel.org>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
"Shuah Khan" <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] tools/nolibc: Fix build of stdio.h due to header ordering
Date: Thu, 13 Apr 2023 19:08:59 +0200 [thread overview]
Message-ID: <ZDg3K2nI+5l6as/L@1wt.eu> (raw)
In-Reply-To: <20230413-nolibc-stdio-fix-v1-1-fa05fc3ba1fe@kernel.org>
Hi Mark,
Sorry for this issue, I don't know why it didn't trigger in our tests,
maybe due to the includes being explicit in the test program.
On Thu, Apr 13, 2023 at 05:26:32PM +0100, Mark Brown wrote:
> When we added fd based file streams we created references to STx_FILENO in
> stdio.h but these constants are declared in unistd.h which is the last file
> included by the top level nolibc.h meaning those constants are not defined
> when we try to build stdio.h. This causes programs using nolibc.h to fail
> to build.
>
> Reorder the headers to avoid this issue.
>
> Fixes: d449546c957f ("tools/nolibc: implement fd-based FILE streams")
> Signed-off-by: Mark Brown <broonie@kernel.org>
Acked-by: Willy Tarreau <w@1wt.eu>
Paul, the commit above is in your rcu/next branch but fortunately not
in the series you've prepared for 6.4, so it will be sufficient to pick
it on top of next and you can take it directly if you want.
Thanks!
Willy
next prev parent reply other threads:[~2023-04-13 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 16:26 Mark Brown
2023-04-13 17:08 ` Willy Tarreau [this message]
2023-04-13 17:33 ` Paul E. McKenney
2023-04-13 17:42 ` Willy Tarreau
2023-04-13 18:25 ` Paul E. McKenney
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=ZDg3K2nI+5l6as/L@1wt.eu \
--to=w@1wt.eu \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=paulmck@kernel.org \
--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 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®