Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14826] make qemu_x86_64_defconfig stopped working
Date: Tue, 31 May 2022 09:28:38 +0000	[thread overview]
Message-ID: <bug-14826-163-nldL2IftG7@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14826-163@https.bugs.busybox.net/>

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

--- Comment #4 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Hello,

This issue is caused by a gcc-12 extra check about use-after-free,
which has been fixed in the kernel with:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=52a9dab6d892763b2a8334a568bd4e2c1a6fde66

You hit this issue because Archlinux is now using gcc-12.1.0 as the
default compiler, and because the kernel uses -Werror to build that
host tool.

So, either update your kernel to one that has the fix, or backport it
yourself, or downgrade your compiler to a (slightly) older one.

Regards,
Yann E. MORIN.

-- 
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

  parent reply	other threads:[~2022-05-31  9:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 19:41 [Buildroot] [Bug 14826] New: make qemu_x86_64_defconfig stopped working bugzilla
2022-05-30 22:04 ` [Buildroot] [Bug 14826] " bugzilla
2022-05-30 23:40 ` bugzilla
2022-05-30 23:41 ` bugzilla
2022-05-31  9:28 ` bugzilla [this message]
2022-05-31 12:15 ` bugzilla
2022-05-31 17:48 ` bugzilla
2022-06-04  8:24 ` 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-14826-163-nldL2IftG7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox