Bug#994274: syslinux: FTBFS with gnu-efi 3.0.13

Philipp Kern <[email protected]>
Newsgroups gmane.linux.debian.devel.cd
Message-ID <Y0vM5RJM1mTPXwOL__39265.2297554136$1665912274$gmane$org@master.debian.org>
On Wed, Sep 15, 2021 at 12:34:53AM +0200, Lukas Schwaighofer wrote:
> With the new version of gnu-efi that was recently uploaded [1] to
> unstable, syslinux fails to build from source.
> 
> So far I tried applying a simple fix from the upstream mailing list [2]
> which result in a successful build, but the efi binaries from that
> build are unbootable.

It looks like Ubuntu added a patch to fix this slightly differently
(adding <setjmp.h> to efi/main.c instead of adding <efisetjmp.h>[1]).
With that it compiles as well. I don't quite understand the reference
to glibc in the changelog[2], though. This is reusing syslinux's
internal setjmp logic copied from klibc while gnu-efi rolled its own.
It's also possible that by including the "wrong" header you get the
wrong linkage against the wrong implementation.

Could you try this out? Apparently I cannot test this within qemu OVMF
(per [3] and it also didn't boot for me).

Kind regards
Philipp Kern

[1] http://launchpadlibrarian.net/553034379/syslinux_3%3A6.04~git20190206.bf6db5b4+dfsg1-3_3%3A6.04~git20190206.bf6db5b4+dfsg1-3ubuntu1.diff.gz
[2] https://launchpad.net/ubuntu/+source/syslinux/3:6.04~git20190206.bf6db5b4+dfsg1-3ubuntu1
[3] https://wiki.archlinux.org/title/syslinux#Limitations_of_UEFI_Syslinux
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.