From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/coreutils: drop gl_cv_func_fstatat_zero_flag=no from config env
Date: Mon, 27 Dec 2021 09:57:54 +0100 [thread overview]
Message-ID: <20211227095754.16d3c31f@windsurf> (raw)
In-Reply-To: <20211227072344.16697-1-jcmvbkbc@gmail.com>
On Sun, 26 Dec 2021 23:23:44 -0800
Max Filippov <jcmvbkbc@gmail.com> wrote:
> Configuring coreutils with gl_cv_func_fstatat_zero_flag=no results in
> non-functional lchmod library function which causes 'mkfifo -m' to
> always complete with the message 'cannot set permissions of ...: Invalid
> argument' and an error exit code. gl_cv_func_fstatat_zero_flag=no is not
> needed when building coreutils-9.0 for linux and its setting should be
> correctly determined by the configure script.
> Drop gl_cv_func_fstatat_zero_flag=no from the coreutils configure
> environment.
>
> For more details see
> https://lists.buildroot.org/pipermail/buildroot/2021-December/631388.html
>
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> ---
> package/coreutils/coreutils.mk | 1 -
> 1 file changed, 1 deletion(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-27 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 7:23 [Buildroot] [PATCH] package/coreutils: drop gl_cv_func_fstatat_zero_flag=no from config env Max Filippov
2021-12-27 8:57 ` Thomas Petazzoni [this message]
2022-01-24 17:36 ` Peter Korsgaard
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=20211227095754.16d3c31f@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=jcmvbkbc@gmail.com \
/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