From: Peter Korsgaard <peter@korsgaard.com>
To: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
Cc: Romain Naour <romain.naour@gmail.com>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/glibc: fix struct stat for microblaze with largefile
Date: Wed, 17 Aug 2022 08:38:23 +0200 [thread overview]
Message-ID: <87pmgz9xy8.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220725100745.2878896-1-arnout@mind.be> (Arnout Vandecappelle's message of "Mon, 25 Jul 2022 12:07:45 +0200")
>>>>> "Arnout" == Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> writes:
> On microblaze, there is a separate version of struct stat for largefile
> and for non-largefile. When the struct was updated to include the
> st_mtim, st_atim and st_ctim members for POSIX, the largefile version
> was forgotten. Since we only use largefile in Buildroot, that means that
> microblaze didn't have these members in struct stat. This breaks the
> build of some packages.
> Change the define around st_mtim etc. to __USE_XOPEN2K8 to enable it in
> posix context (i.e. by default).
> Fixes:
> - http://autobuild.buildroot.org/results/dd944a3bd4ac0c94b2bec8ac209100daaf43903d (zstd)
> - http://autobuild.buildroot.org/results/4609c8e2af24d9536eb33397a4659ad740aca742 (dieharder)
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> Cc: Romain Naour <romain.naour@gmail.com>
Committed to 2022.05.x and 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-08-17 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 10:07 [Buildroot] [PATCH] package/glibc: fix struct stat for microblaze with largefile Arnout Vandecappelle (Essensium/Mind)
2022-07-25 10:24 ` Romain Naour
2022-07-25 10:36 ` Arnout Vandecappelle
2022-08-17 6:38 ` Peter Korsgaard [this message]
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=87pmgz9xy8.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=romain.naour@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