From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16096] New: iproute musl + gcc-14 compile error w/ 2024.05-rc1
Date: Tue, 04 Jun 2024 20:06:01 +0000 [thread overview]
Message-ID: <bug-16096-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=16096
Bug ID: 16096
Summary: iproute musl + gcc-14 compile error w/ 2024.05-rc1
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: lancethepants@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
I'm getting the below error with gcc-14 and musl using 2024.05-rc1.
There's is an upstream patch that fixes this.
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=53a89bfd86fff1a00cc77cabb8457a03eaa3bc7d
../include/json_print.h:58:48: error: passing argument 5 of ‘print_color_tv’
from incompatible pointer type [-Wincompatible-pointer-types]
58 | value);
\
| ^~~~~
| |
| const struct timeval *
BR2_x86_64=y
BR2_TOOLCHAIN_BUILDROOT_MUSL=y
BR2_KERNEL_HEADERS_6_6=y
BR2_BINUTILS_VERSION_2_42_X=y
BR2_GCC_VERSION_14_X=y
BR2_PACKAGE_IPROUTE2=y
--
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:[~2024-06-04 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 20:06 bugzilla [this message]
2024-06-04 20:18 ` [Buildroot] [Bug 16096] iproute musl + gcc-14 compile error w/ 2024.05-rc1 bugzilla
2024-06-04 20:42 ` bugzilla
2024-06-15 15:20 ` 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-16096-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox