[yocto] [x32 ABI] Bit size mismatch in grub-efi

Michel D'HOOGE michel.dhooge at free.fr
Thu Oct 6 05:43:01 PDT 2016


Hi,

I'd like to give the x32 ABI a try, so I followed the steps in section 4.4 of the reference manual.

First, I tried the core-image-sato recipe, and then switched to core-image-minimal because it is faster to recompile from scratch… However I assume both should work since Sato is explicitly referred to in the manual, and minimal should always work! And for completeness, I am on the master branch of poky.

So, this doesn't work and I get many lines like the following ones from grub-efi:

ERROR: grub-efi-2.00-r3 do_package_qa: QA Issue: Bit size did not match (32 to 64) grub-efi on /work/x86_64_x32-poky-linux-gnux32/grub-efi/2.00-r3/packages-split/grub-efi/usr/libx32/grub/x86_64-efi/kernel.img
Bit size did not match (32 to 64) grub-efi on /work/x86_64_x32-poky-linux-gnux32/grub-efi/2.00-r3/packages-split/grub-efi/usr/libx32/grub/x86_64-efi/trig.mod
Bit size did not match (32 to 64) grub-efi on /work/x86_64_x32-poky-linux-gnux32/grub-efi/2.00-r3/packages-split/grub-efi/usr/libx32/grub/x86_64-efi/cs5536.mod
Bit size did not match (32 to 64) grub-efi on /work/x86_64_x32-poky-linux-gnux32/grub-efi/2.00-r3/packages-split/grub-efi/usr/libx32/grub/x86_64-efi/usb.mod
Bit size did not match (32 to 64) grub-efi on /work/x86_64_x32-poky-linux-gnux32/grub-efi/2.00-r3/packages-split/grub-efi/usr/libx32/grub/x86_64-efi/usbserial_common.mod

And then, it fails:
ERROR: grub-efi-2.00-r3 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: grub-efi-2.00-r3 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /mnt/Yocto/Fabric-x32/build/tmp/work/x86_64_x32-poky-linux-gnux32/grub-efi/2.00-r3/temp/log.do_package_qa.11229
ERROR: Task (/mnt/Yocto/Fabric-x32/sources/poky/meta/recipes-bsp/grub/grub-efi_2.00.bb:do_package_qa) failed with exit code '1'


AFAIK, the image won't use EFI. And I guess this package is only required by the native part "by default".

What is the proper solution to bypass these errors?

Thanks
Michel



More information about the yocto mailing list