From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15778] strace comilation fails on Fedora39/gcc13
Date: Wed, 20 Sep 2023 15:39:42 +0000 [thread overview]
Message-ID: <bug-15778-163-EXAQMJFgYe@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15778-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15778
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
CC| |yann.morin.1998@free.fr
Status|NEW |RESOLVED
--- Comment #3 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Ian, All,
As you noticed, this is already fixed on the master branch.
On 2023.08, the latest kernel headers version that is supported is
6.4. So, if the build issue is due to an incompatibility with headers
from kernel 6.5, that does not apply to 2023.08.
strace is not a host package either, so the kernel headers used on
the build host should not matter. If they do, then this is another
bug in strace.
As such, I'm closing the bug. Thanks for the report!
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
prev parent reply other threads:[~2023-09-20 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 13:12 [Buildroot] [Bug 15778] New: strace comilation fails on Fedora39/gcc13 bugzilla
2023-09-19 10:11 ` [Buildroot] [Bug 15778] " bugzilla
2023-09-20 7:36 ` bugzilla
2023-09-20 15:39 ` bugzilla [this message]
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-15778-163-EXAQMJFgYe@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