All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15006] toolchain Arm AArch64 toolchain 11.2-2022.02
Date: Wed, 21 Sep 2022 21:16:07 +0000	[thread overview]
Message-ID: <bug-15006-163-2ecgukOUga@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15006-163@https.bugs.busybox.net/>

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

--- Comment #1 from romain.naour@gmail.com ---
Hello,

It seems this is a similar issue than for arm-gnu-toolchain (bare-metal
toolchain) [1]

[1]
https://gitlab.com/buildroot.org/buildroot/-/commit/f1017a5834b744e6f87c3372a6de60d553566fd2

There is even a new release 11.3.Rel1 but the prebuilt binaries still crash.

Best regards,
Romain

-- 
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:[~2022-09-21 21:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 20:19 [Buildroot] [Bug 15006] New: toolchain Arm AArch64 toolchain 11.2-2022.02 bugzilla
2022-09-21 21:16 ` bugzilla [this message]
2022-10-25 20:13 ` [Buildroot] [Bug 15006] " 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-15006-163-2ecgukOUga@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.