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

Bug#918188: linux: FTBFS on arm64



On Fri, Jan 04, 2019 at 06:57:21AM +0100, Salvatore Bonaccorso wrote:
> >   LD      vmlinux.o
> >   MODPOST vmlinux.o
> >   GEN     .version
> >   CHK     include/generated/compile.h
> >   UPD     include/generated/compile.h
> >   CC      init/version.o
> >   LD      init/built-in.o
> > ./drivers/firmware/efi/libstub/lib.a(arm64-stub.stub.o): In function `handle_kernel_image':
> > ./debian/build/build_arm64_none_arm64/./drivers/firmware/efi/libstub/arm64-stub.c:63: undefined reference to `__efistub__GLOBAL_OFFSET_TABLE_'
> > ld: ./drivers/firmware/efi/libstub/lib.a(arm64-stub.stub.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against external symbol `__efistub__GLOBAL_OFFSET_TABLE_' can not be used when making a shared object; recompile with -fPIC
> > /<<PKGBUILDDIR>>/Makefile:1010: recipe for target 'vmlinux' failed
> > make[5]: *** [vmlinux] Error 1
> > Makefile:152: recipe for target 'sub-make' failed
> > make[4]: *** [sub-make] Error 2
> > Makefile:24: recipe for target '__sub-make' failed
> > make[3]: *** [__sub-make] Error 2
> > make[3]: Leaving directory '/<<PKGBUILDDIR>>/debian/build/build_arm64_none_arm64'
> > debian/rules.real:190: recipe for target 'debian/stamps/build_arm64_none_arm64' failed
> > make[2]: *** [debian/stamps/build_arm64_none_arm64] Error 2
> > make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> > debian/rules.gen:400: recipe for target 'build-arch_arm64_none_arm64_real' failed
> > make[1]: *** [build-arch_arm64_none_arm64_real] Error 2
> > make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> > debian/rules:41: recipe for target 'build-arch' failed
> > make: *** [build-arch] Error 2
> > dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
> 
> https://buildd.debian.org/status/fetch.php?pkg=linux&arch=arm64&ver=4.9.144-1&stamp=1546572157&raw=0

The problem was introduced with upstream commit
27b5ebf61818749b3568354c64a8ec2d9cd5ecca. Reverting that commit fixes
the build, but there may be a better option.

Attachment: signature.asc
Description: PGP signature


Reply to: