From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15141] New: kernel 5.16.2 (realtime patch 19) fails to build
Date: Wed, 23 Nov 2022 08:54:07 +0000 [thread overview]
Message-ID: <bug-15141-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15141
Bug ID: 15141
Summary: kernel 5.16.2 (realtime patch 19) fails to build
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: ian_ormshaw@waters.com
CC: buildroot@uclibc.org
Target Milestone: ---
Created attachment 9411
--> https://bugs.busybox.net/attachment.cgi?id=9411&action=edit
Build log
Using buildroot 20022-11 rc2 kernel 5.16.2 (with realtime patch 19) fails to
build.
This is the case for gcc 11 and 12
--
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
next reply other threads:[~2022-11-23 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 8:54 bugzilla [this message]
2022-11-23 10:09 ` [Buildroot] [Bug 15141] kernel 5.16.2 (realtime patch 19) fails to build bugzilla
2022-11-23 10:42 ` bugzilla
2022-11-23 16:39 ` 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-15141-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.