[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: fwupdate not building; efibootmgr 0.11.0 crashes with efivar 0.18



On Wed, May 27, 2015 at 05:44:23PM -0500, D. Jared Dominguez wrote:
> On Wed, May 27, 2015 at 01:38:23PM -0500, Peter Jones wrote:
> >On Wed, May 20, 2015 at 08:42:15PM -0500, D. Jared Dominguez wrote:
> >>Hi Peter,
> >
> >Just catching up on email from last week...
> >
> >>
> >>I'm trying to build fwupdate. I know it's early, but I'd like to make it
> >>testable on Debian. It's not buildable for me because it barfs on this:
> >>make[3]: Entering directory '/«BUILDDIR»/fwupdate-0.2+git20150520/efi'
> >>gcc -O0 -g3 -fpic -Wall -fshort-wchar -fno-strict-aliasing -fno-merge-constants -ffreestanding -fno-stack-protector -fno-stack-check --std=c11 -DCONFIG_x86_64 -D__KERNEL__ -I/usr/include/efi/ -I/usr/include/efi/x86_64/ -iquote/«BUILDDIR»/fwupdate-0.2+git20150520/include -mno-mmx -mno-sse -mno-red-zone -nostdinc -maccumulate-outgoing-args -DEFI_FUNCTION_WRAPPER -DGNU_EFI_USE_MS_ABI -I/usr/lib/gcc/x86_64-linux-gnu/4.9/include -c -o fakeesrt2.o fakeesrt2.c
> >>fakeesrt2.c:1:17: fatal error: efi.h: No such file or directory
> >>  #include <efi.h>
> >>                  ^
> >>compilation terminated.
> >>make[3]: *** [fakeesrt2.o] Error 1
> >>Makefile:53: recipe for target 'fakeesrt2.o' failed
> >>make[3]: Leaving directory '/«BUILDDIR»/fwupdate-0.2+git20150520/efi'
> >>
> >>I'm actually not sure where efi.h is supposed to come from. I see a
> >>fwup-efi.h in fwupdate's source and no efi.h in efivar's source. Am I
> >>missing something?
> >
> >That's from gnu-efi (or gnu-efi-devel in recent fedora) - I don't know
> >how debian breaks down those packages.
> 
> Sending you a patch to your spec file for this.

Great - I just came back to my mailbox to look for exactly this and
there it was! :)

> 
> >>A Debian user
> >>has also reported that efibootmgr crashes on him when using libefivar0 0.18:
> >>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785786
> >
> >I'm not seeing a /crash/ there, but that's certainly a failure
> >somewhere.  Hard to know if it's in efibootmgr or efivar or grub without
> >the command line, though :/
> 
> I ended up reverting to efivar 0.15 since you're in the middle of
> updating/refactoring all the efi things.
> 
> --Jared
> 
> 
> -- 
> Jared Domínguez
> Infrastructure Software Engineering
> Dell | Enterprise Solutions Group

-- 
        Peter


Reply to: