From: Lance Fredrickson <lancethepants@gmail.com>
To: Arnout Vandecappelle <arnout@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] boot/syslinux: fix build with GCC 14.x
Date: Wed, 19 Jun 2024 14:45:07 -0600 [thread overview]
Message-ID: <3dff7ff6-86fa-4861-862e-5081f56e191b@gmail.com> (raw)
In-Reply-To: <10907897-c3bc-48c9-9d11-b8966b58a612@mind.be>
I'm not sure I understand. The patch which you included in your reply
does have a "Signed-off-by" line present. Also, the last release of
syslinux was in 2014, and buildroot seems to be carrying many patches
against that release, so I was under the impression upstream is probably
not accepting patches at this point.
The "From" when sending this patch doesn't match my name in the
"Signed-off-by" as another maintainer mentioned in another patch I sent
in, but this one was also sent before I received that reply.
Lance
On 6/19/2024 2:25 PM, Arnout Vandecappelle wrote:
> Hi Lance,
>
> On 05/06/2024 23:20, lancethepants wrote:
>> Add missing stdio.h include. Without it results in the following
>> error under GCC 14.x
>>
>> ../../../com32/lib/syslinux/debug.c: In function ‘syslinux_debug’:
>> ../../../com32/lib/syslinux/debug.c:91:5: error: implicit declaration
>> of function ‘printf’ [-Wimplicit-function-declaration]
>> 91 | printf("Dynamic debug unavailable\n");
>>
>> Signed-off-by: Lance Fredrickson <lancethepants@gmail.com>
>> ---
>> .../0020-pull-in-stdio-h-for-gcc14.patch | 25 +++++++++++++++++++
>> 1 file changed, 25 insertions(+)
>> create mode 100644 boot/syslinux/0020-pull-in-stdio-h-for-gcc14.patch
>>
>> diff --git a/boot/syslinux/0020-pull-in-stdio-h-for-gcc14.patch
>> b/boot/syslinux/0020-pull-in-stdio-h-for-gcc14.patch
>> new file mode 100644
>> index 0000000000..6711c7aa78
>> --- /dev/null
>> +++ b/boot/syslinux/0020-pull-in-stdio-h-for-gcc14.patch
>> @@ -0,0 +1,25 @@
>> +From dfa2705100a893bc017d23406daa9a383fbc3c95 Mon Sep 17 00:00:00 2001
>> +From: lancethepants <lancethepants@gmail.com>
>> +Date: Wed, 5 Jun 2024 14:31:38 -0600
>> +Subject: [PATCH] com32/lib/syslinux/debug.c: add missing stdio.h
>> include.
>> +
>> +Fixes building with GCC 14.x
>
> As check-package reports, the patch is missing a Signed-off-by (to
> indicate that you are allowed to contribute it under the syslinux
> license) and an Upstream: indicator. We expect you to submit the patch
> upstream before you submit it to buildroot.
>
> Regards,
> Arnout
>
>> +---
>> + com32/lib/syslinux/debug.c | 1 +
>> + 1 file changed, 1 insertion(+)
>> +
>> +diff --git a/com32/lib/syslinux/debug.c b/com32/lib/syslinux/debug.c
>> +index d9ab863f..e8f53d57 100644
>> +--- a/com32/lib/syslinux/debug.c
>> ++++ b/com32/lib/syslinux/debug.c
>> +@@ -1,6 +1,7 @@
>> + #include <linux/list.h>
>> + #include <string.h>
>> + #include <stdbool.h>
>> ++#include <stdio.h>
>> +
>> + #ifdef DYNAMIC_DEBUG
>> +
>> +--
>> +2.39.2
>> +
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-06-19 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 21:20 [Buildroot] [PATCH 1/1] boot/syslinux: fix build with GCC 14.x lancethepants
2024-06-19 20:25 ` Arnout Vandecappelle via buildroot
2024-06-19 20:45 ` Lance Fredrickson [this message]
2024-06-20 7:02 ` Arnout Vandecappelle via buildroot
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=3dff7ff6-86fa-4861-862e-5081f56e191b@gmail.com \
--to=lancethepants@gmail.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.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