--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: efitools: FTBFS on i386: efibind.h: No such file or directory
- From: "Aaron M. Ucko" <amu@alum.mit.edu>
- Date: Tue, 26 Apr 2016 15:29:56 -0400
- Message-id: <146169899601.23300.10200203782295140646.reportbug@ghostwheel.internal.ucko.debian.net>
Source: efitools
Version: 1.4.2-2
Severity: important
Justification: fails to build from source
Thanks for fixing efitools's Build-Depends setting! Automated builds
now get further, but still fail on i386, with
In file included from simple_file.c:7:0:
/usr/include/efi/efi.h:35:21: fatal error: efibind.h: No such file or irectory
(kfreebsd-amd64 builds also still fail, but with a different error
I'll report separately.)
The i386 version of this header turns out to be in
/usr/include/efi/ia32, not /usr/include/efi/i686. I see no sign of a
config script that would report this location, so I suppose efitools
will need to hardcode the mapping.
I also noticed two further complications that will affect linking on
i386: the crt0 file is likewise named crt0-efi-ia32.o, and 32-bit
gnu-efi libraries are in /usr/lib32, which isn't in the default search
path.
Could you please take a look?
Thanks!
--- End Message ---
--- Begin Message ---
- To: Luca Boccassi <bluca@debian.org>, 822724-done@bugs.debian.org
- Subject: Re: Bug#822724: Bug#822725: Bug#822724: efitools: FTBFS on i386: efibind.h: No such file or directory
- From: Steve McIntyre <steve@einval.com>
- Date: Tue, 24 May 2022 18:52:54 +0100
- Message-id: <20220524175254.GA9728@tack.einval.com>
- In-reply-to: <1548433239.8759.66.camel@debian.org>
- References: <146169899601.23300.10200203782295140646.reportbug@ghostwheel.internal.ucko.debian.net> <572389E7.9010401@wzdftpd.net> <20160429165815.GA31950@einval.com> <57239A5F.5040507@wzdftpd.net> <20160429174519.GD23867@einval.com> <146169899601.23300.10200203782295140646.reportbug@ghostwheel.internal.ucko.debian.net> <1548433239.8759.66.camel@debian.org>
On Fri, Jan 25, 2019 at 04:20:39PM +0000, Luca Boccassi wrote:
>
>The latest upload from December builds fine on i386, amd64, armhf and
>arm64, and as far as I can see it's building the EFI binaries with the
>right LD scripts from gnu-efi, eg: elf_aarch64_efi.lds,
>elf_ia32_efi.lds
>
>So I think we can close this one too?
Agreed, let's close this now!
--
Steve McIntyre, Cambridge, UK. steve@einval.com
Getting a SCSI chain working is perfectly simple if you remember that there
must be exactly three terminations: one on one end of the cable, one on the
far end, and the goat, terminated over the SCSI chain with a silver-handled
knife whilst burning *black* candles. --- Anthony DeBoer
--- End Message ---