All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16066] New: buildroot toolchain fails to build on arm if BR2_TIME_BITS_64=Y
Date: Fri, 10 May 2024 09:24:02 +0000	[thread overview]
Message-ID: <bug-16066-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 16066
           Summary: buildroot toolchain fails to build on arm if
                    BR2_TIME_BITS_64=Y
           Product: buildroot
           Version: 2024.02.1
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: Jorgen.Pihlflyckt@ajeco.fi
                CC: buildroot@uclibc.org
  Target Milestone: ---

This is a problem cased by the dreaded Y2038 issue.

The toolchain build fails when compiling libsanitizer at the host-final build
stage. The following post on gcc-patches seems to fix the problem:

https://gcc.gnu.org/pipermail/gcc-patches/2024-February/646317.html

However, this patch is not yet included in the gcc versions included with the
buildroot toolchain in version 2024.02.2
-----
Cheers. Jorgen.Pihlflyckt@ajeco.fi

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2024-05-10  9:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10  9:24 bugzilla [this message]
2024-06-15 15:21 ` [Buildroot] [Bug 16066] buildroot toolchain fails to build on arm if BR2_TIME_BITS_64=Y 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-16066-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.