From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] boot/syslinux: fix build with gcc-15.x
Date: Fri, 15 Aug 2025 12:18:15 +0200 [thread overview]
Message-ID: <20250815121815.436050ec@windsurf> (raw)
In-Reply-To: <20250730190118.448997-1-bernd@kuhls.net>
Hello,
On Wed, 30 Jul 2025 21:01:18 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> Fixes build error with gcc-15.x:
>
> drivers/net/3c509-eisa.c:39:26: error: initialization of 'void (*)(void)'
> from incompatible pointer type 'void (*)(struct nic *, struct eisa_device *)'
> [-Wincompatible-pointer-types]
>
> For a similar fix see https://bugzilla.suse.com/show_bug.cgi?id=1243225
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
This change breaks the build with older compilers:
https://gitlab.com/buildroot.org/buildroot/-/jobs/10975828975
I'm about to send a patch that will update the toolchain used in those
tests, papering over this issue, but I believe it is not normal to
break the build of syslinux with older compilers, such as:
BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-i386-pentium4-full-2017.05-1078-g95b1dae.tar.bz2"
BR2_TOOLCHAIN_EXTERNAL_GCC_6=y
BR2_TOOLCHAIN_EXTERNAL_HEADERS_3_2=y
BR2_TOOLCHAIN_EXTERNAL_LOCALE=y
# BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG is not set
BR2_TOOLCHAIN_EXTERNAL_CXX=y
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-08-15 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 19:01 [Buildroot] [PATCH 1/1] boot/syslinux: fix build with gcc-15.x Bernd Kuhls
2025-07-31 14:11 ` Julien Olivain via buildroot
2025-08-15 10:18 ` Thomas Petazzoni via buildroot [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=20250815121815.436050ec@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
/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.