Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13851] New: timespec on 32bit systems requires some toolchain header minimums if using a kernel over 5.6+
Date: Tue, 15 Jun 2021 15:05:42 +0000	[thread overview]
Message-ID: <bug-13851-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=13851

            Bug ID: 13851
           Summary: timespec on 32bit systems requires some toolchain
                    header minimums if using a kernel over 5.6+
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: matthew.weber at rockwellcollins.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

The header mismatch seems like a dependency Buildroot could check to prevent
hidden time bugs where the kernel/glibc are all good(kernel 5.6+ and Glibc
2.32+), but someone uses old toolchain headers < 5.6 resulting in the
application using a 32bit timespec@runtime.

https://stackoverflow.com/questions/14361651/is-there-any-way-to-get-64-bit-time-t-in-32-bit-programs-in-linux/60709400#60709400

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-06-15 15:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 15:05 bugzilla at busybox.net [this message]
2022-07-25 14:27 ` [Buildroot] [Bug 13851] timespec on 32bit systems requires some toolchain header minimums if using a kernel over 5.6+ bugzilla
2024-06-15 14:58 ` bugzilla

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-13851-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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