From: Romain Naour <romain.naour@smile.fr>
To: Bernd Kuhls <bernd@kuhls.net>,
buildroot@uclibc.org, Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] package/gnu-efi: bump to version 3.0.17
Date: Tue, 27 Feb 2024 13:58:59 +0100 [thread overview]
Message-ID: <d9e46b02-e299-46b7-9fd9-bbe43ecd9afe@smile.fr> (raw)
In-Reply-To: <pan$8ffb8$216c5e07$61fb4f0$f3d6d79f@ID-313208.user.individual.net>
Hello Julien, Bernd, All,
Le 19/02/2024 à 21:04, Bernd Kuhls a écrit :
> Am Sun, 11 Feb 2024 22:49:35 +0100 schrieb Julien Olivain:
>
>> For commit logs, see:
>> https://sourceforge.net/p/gnu-efi/code/ci/3.0.17/log/
>
> Hi Julien,
>
> this bump breaks building syslinux (not yet caught by the autobuilders):
> https://bugs.gentoo.org/921597
Not by autobuilders but by the gitlab-ci:
https://gitlab.com/buildroot.org/buildroot/-/jobs/6256880937
https://gitlab.com/buildroot.org/buildroot/-/jobs/6256880949
The issue was introduced in gnu-efi 3.0.16 [1] that seems wrong/incomplete if we
compare with inttypes.h header from glibc [2].
Julien, can you have a look?
Thanks!
[1]
https://sourceforge.net/p/gnu-efi/code/ci/189200d0b0f6fff473d302880d9569f45d4d8c4d
[2]
https://sourceware.org/git/?p=glibc.git;a=blob;f=stdlib/inttypes.h;h=cfda146aa9b956dc9f462bd65fb828e5929bc90b;hb=HEAD#l29
Best regards,
Romain
>
> Regards, Bernd
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-02-27 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240211214935.1603160-1-ju.o__4871.99223586998$1707688208$gmane$org@free.fr>
2024-02-19 20:04 ` [Buildroot] [PATCH 1/1] package/gnu-efi: bump to version 3.0.17 Bernd Kuhls
2024-02-27 12:58 ` Romain Naour [this message]
2024-02-27 21:39 ` Julien Olivain
2024-02-11 21:49 Julien Olivain
2024-02-12 21:55 ` Thomas Petazzoni 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=d9e46b02-e299-46b7-9fd9-bbe43ecd9afe@smile.fr \
--to=romain.naour@smile.fr \
--cc=bernd@kuhls.net \
--cc=buildroot@uclibc.org \
--cc=ju.o@free.fr \
/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.