Re: help? efivar 0.20-3 fails to build on arm64
On Wed, Jun 24, 2015 at 03:47:13PM -0500, Dominguez, Jared wrote:
So I just got an email about efivar 0.20-3 failing to build only on
arm64. See the log here:
https://buildd.debian.org/status/fetch.php?pkg=efivar&arch=arm64&ver=0.20-3&stamp=1435172463
I notice that the failure happens in dh_auto_test:
"""
dh_auto_test -a
make -j1 test
make[1]: Entering directory '/«PKGBUILDDIR»'
make -C src TOPDIR=/«PKGBUILDDIR» SRCDIR=/«PKGBUILDDIR»/src/
ARCH=aarch64
make[2]: Entering directory '/«PKGBUILDDIR»/src'
make[3]: Entering directory '/«PKGBUILDDIR»/src/test'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/«PKGBUILDDIR»/src/test'
make[2]: Leaving directory '/«PKGBUILDDIR»/src'
make -C docs TOPDIR=/«PKGBUILDDIR» SRCDIR=/«PKGBUILDDIR»/docs/
ARCH=aarch64
make[2]: Entering directory '/«PKGBUILDDIR»/docs'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/«PKGBUILDDIR»/docs'
make[2]: Entering directory '/«PKGBUILDDIR»/src'
make[3]: Entering directory '/«PKGBUILDDIR»/src/test'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/«PKGBUILDDIR»/src/test'
make -C test TOPDIR=/«PKGBUILDDIR» SRCDIR=/«PKGBUILDDIR»/src/ test
make[3]: Entering directory '/«PKGBUILDDIR»/src/test'
./tester
FAIL: "one"(line 111) (-1) set test failed: Permission denied
About to test empty
testing efi_set_variable()
testing efi_get_variable_size()
testing efi_get_variable()
testing efi_get_variable_attributes()
testing efi_del_variable()
testing efi_set_variable() with too many arguments
testing efi_append_variable()
testing efi_get_variable()
testing efi_del_variable()
About to test one
testing efi_set_variable()
make[3]: *** [test] Error 1
Makefile:18: recipe for target 'test' failed
make[2]: *** [test] Error 2
make[3]: Leaving directory '/«PKGBUILDDIR»/src/test'
Makefile:100: recipe for target 'test' failed
make[2]: Leaving directory '/«PKGBUILDDIR»/src'
make[1]: *** [test] Error 2
Makefile:23: recipe for target 'test' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_test: make -j1 test returned exit code 2
make: *** [build-arch] Error 2
"""
But then I looked at the log for 0.20-2:
https://buildd.debian.org/status/fetch.php?pkg=efivar&arch=arm64&ver=0.20-2&stamp=1435096092
"""
dh_auto_test -a
make -j1 test
make[1]: Entering directory '/«PKGBUILDDIR»'
make -C src TOPDIR=/«PKGBUILDDIR» SRCDIR=/«PKGBUILDDIR»/src/
ARCH=aarch64
make[2]: Entering directory '/«PKGBUILDDIR»/src'
make[3]: Entering directory '/«PKGBUILDDIR»/src/test'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/«PKGBUILDDIR»/src/test'
make[2]: Leaving directory '/«PKGBUILDDIR»/src'
make -C docs TOPDIR=/«PKGBUILDDIR» SRCDIR=/«PKGBUILDDIR»/docs/
ARCH=aarch64
make[2]: Entering directory '/«PKGBUILDDIR»/docs'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/«PKGBUILDDIR»/docs'
make[2]: Entering directory '/«PKGBUILDDIR»/src'
make[3]: Entering directory '/«PKGBUILDDIR»/src/test'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/«PKGBUILDDIR»/src/test'
make -C test TOPDIR=/«PKGBUILDDIR» SRCDIR=/«PKGBUILDDIR»/src/ test
make[3]: Entering directory '/«PKGBUILDDIR»/src/test'
./tester
UEFI variables not supported on this machine.
make[3]: Leaving directory '/«PKGBUILDDIR»/src/test'
make[2]: Leaving directory '/«PKGBUILDDIR»/src'
make[2]: Entering directory '/«PKGBUILDDIR»/docs'
make[2]: Nothing to be done for 'test'.
make[2]: Leaving directory '/«PKGBUILDDIR»/docs'
make[1]: Leaving directory '/«PKGBUILDDIR»'
"""
Well, okay, and it seems that generally builds succeed when the arm64
system doesn't support UEFI variables:
https://buildd.debian.org/status/logs.php?pkg=efivar&arch=arm64
So then, I've got questions:
1. Are some of the arm64 buildd's UEFI-enabled and some not? If so,
should they actually be segmented?
2. Would someone involved in the arm64 port be willing to look at this
build issue? Alternatively, I would need access to an arm64 system.
--Jared
Okay, so I talked to upstream, and he says I should only run "make test"
for efivar if I'm actually doing development. Otherwise, I'm more likely
to run into firmware bugs than actual bugs in efivar. #2 is not an
important question then.
#1 still is relevant.
--
Jared Domínguez
Infrastructure Software Engineering
Dell | Enterprise Solutions Group
Reply to: