public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arnout at mind dot be" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/29403] New: st_atim, st_mtim, st_ctim stat struct members are missing on microblaze with largefile Date: Mon, 25 Jul 2022 09:31:39 +0000 [thread overview] Message-ID: <bug-29403-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29403 Bug ID: 29403 Summary: st_atim, st_mtim, st_ctim stat struct members are missing on microblaze with largefile Product: glibc Version: 2.36 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: arnout at mind dot be CC: drepper.fsp at gmail dot com Target Milestone: --- Created attachment 14230 --> https://sourceware.org/bugzilla/attachment.cgi?id=14230&action=edit Make struct stat posix conformant on microblaze with __USE_FILE_OFFSET64 Commit a06b40cdf5ba0d2ab4f9b4c77d21e45ff284fac7 updated stat.h to use __USE_XOPEN2K8 instead of __USE_MISC to add the st_atim, st_mtim and st_ctim members to struct stat. However, for microblaze, there are two definitions of struct stat, depending on the __USE_FILE_OFFSET64 macro. The second one was not updated. Fix attached. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-07-25 9:31 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-25 9:31 arnout at mind dot be [this message] 2022-07-25 9:55 ` [Bug libc/29403] " arnout at mind dot be 2022-07-25 9:56 ` arnout at mind dot be 2022-07-25 9:56 ` arnout at mind dot be 2022-07-25 14:05 ` adhemerval.zanella at linaro dot org 2022-07-25 14:08 ` adhemerval.zanella at linaro dot org
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=bug-29403-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).