[Buildroot] [Bug 16096] New: iproute musl + gcc-14 compile error w/ 2024.05-rc1

[Buildroot] [Bug 16096] New: iproute musl + gcc-14 compile error w/ 2024.05-rc1

[bugzilla]

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

[Buildroot] [Bug 16096] iproute musl + gcc-14 compile error w/ 2024.05-rc1

[bugzilla]

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

--- Comment #1 from Lance Fredrickson <lancethepants@gmail.com> ---
After applying that fix it still fails with the following.

rdma.c:110:20: error: implicit declaration of function ‘basename’; did you mean
‘rename’? [-Wimplicit-function-declaration]
  110 |         filename = basename(argv[0]);
      |                    ^~~~~~~~
      |                    rename
rdma.c:110:18: error: assignment to ‘char *’ from ‘int’ makes pointer from
integer without a cast [-Wint-conversion]
  110 |         filename = basename(argv[0]);


hmmmm, basename, looks familiar.

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

[Buildroot] [Bug 16096] iproute musl + gcc-14 compile error w/ 2024.05-rc1

[bugzilla]

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

--- Comment #2 from Lance Fredrickson <lancethepants@gmail.com> ---
Created attachment 9754
  --> https://bugs.busybox.net/attachment.cgi?id=9754&action=edit
Fix iproute2 with musl 1.2.5

This patches fixes the basename issue for me.

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

[Buildroot] [Bug 16096] iproute musl + gcc-14 compile error w/ 2024.05-rc1

[bugzilla]

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

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |yann.morin.1998@free.fr
         Resolution|---                         |MOVED

--- Comment #3 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Thank you for your report.

The issue tracker for the Buildroot project has been moved to
the Gitlab.com issue tracker:
    https://gitlab.com/buildroot.org/buildroot/-/issues

We are taking this opportunity to close old issues in this old
tracker. If you believe your issue is still relevant, please
open one in the new issue tracker.

Thank you!

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