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

Bug#836839: marked as done (fwupdate: FTBFS against efivar 27)



Your message dated Wed, 7 Sep 2016 19:39:06 +0000
with message-id <4a3b906cdf6b4b5f8b0f48c7baf9830e@ausx13mpc124.AMER.DELL.COM>
and subject line 
has caused the Debian Bug report #836839,
regarding fwupdate: FTBFS against efivar 27
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
836839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836839
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: fwupdate
Version: 0.5-4
Severity: serious
Justification: fails to build from source

Hi,

fwupdate FTBFS against the new efivar in sid:

https://buildd.debian.org/status/package.php?p=fwupdate

make[3]: Entering directory '/«PKGBUILDDIR»/linux'
Package efiboot was not found in the pkg-config search path.
Perhaps you should add the directory containing `efiboot.pc'
to the PKG_CONFIG_PATH environment variable
No package 'efiboot' found
gcc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-unused-result -Wno-unused-function -Wsign-compare -Werror=sign-compare -fshort-wchar --std=gnu11 -DLOCALEDIR=\"/usr/share/locale/\" -D_GNU_SOURCE -DFWUP_EFI_DIR_NAME=\"debian\" -I/«PKGBUILDDIR»/linux/include -iquote/«PKGBUILDDIR»/include/  -I/usr/include/efivar    -fPIC -c -o libfwup.o libfwup.c
libfwup.c:12:21: fatal error: efiboot.h: No such file or directory
 #include <efiboot.h>
                     ^
compilation terminated.


Andreas

--- End Message ---
--- Begin Message ---

Package: fwupdate

Version: 8-1

 

Fixed in new version of fwupdate.


--- End Message ---

Reply to: