failed to generate boot.vfat

Ma3ztro · 2017-06-16T20:19:30+00:00

I'm building the batocera-x86_64_defconfig on Ubuntu 17.04. The process ends up with this output (any idea how to fix/workaround this?): Executing post-im...

nadenislamarre

i've ubuntu 16.10 i think. possibly an issue related to that.
how long to compile on a vm ?!? virtual disk are so slow that it slows down the compilation a lot.

you can run the genimage and isolate the issue to found a solution :

target_dir is output/target
binaries_dir is probably output/images
outputpath is probably output/images/recalbox
for tmppath i remember i put something like output/genimage or ouput/build/genimage (you can found values in the script)

genimage --rootpath="${TARGET_DIR}" --inputpath="${BINARIES_DIR}" --outputpath="${RECALBOX_BINARIES_DIR}" --config="${BINARIES_DIR}/genimage.cfg" --tmppath="${GENIMAGE_TMP}" || exit 1

Ma3ztro

nadenislamarre Thanks. I'll experiment with that...

Yep, it takes HOURS to compile! Hehe... but I gave the VM only one CPU core... that is likely not helping... and I changed it for the next time! 🙂

...how long does it take on a real hardware config?

nadenislamarre

for the x86_64, it takes about 8 hours for a full compilation.
for rpi1, rp2, it's more about 5 hours because there are less things to compile (wii/dreamcast/...)

jdorigao

I'm having the same error use Ubuntu 17.04 - 64. @Ma3ztro has solved your problem?

@nadenislamarre What is the operating system and version you are using to compile batocera.linux?

They're doing a good job ...!!!

jdorigao

In my case I was able to solve it by running the command below as root:
echo "mtools_skip_check=1" >> .mtoolsrc

Ma3ztro

jdorigao This shall work, although I made a fix so that this warning error does not trigger. It seems it does not take effect for RPI target... I'll need to review the solution with nadenislamarre.

Here is the delta of the fix:
https://github.com/S3riousSam/batocera.linux/commit/cbf8ee53945ae30682886020e5aedaf6aa19707e

jdorigao

Thanks for the info! @Ma3ztro
Actually the error occurs in Ubuntu 17.04 and not in 16.04, and the tests I did was for the RPI for PC I'm having problems that I'm still checking.

Ma3ztro

As a matter of fact, this problem is 17.04 specific.

nadenislamarre

@Ma3ztro in fact, since the values were changed (probably to fix in 17.04 or 16.10), i got the issue in 16.04. Strange.

jdorigao

Error generating the image at the end of batocera compilation in Ubuntu 17.10

Executing post-image script board/recalbox/copy-recalbox-archives.sh

----- Generating images/recalbox files -----

creating /home/juliano/GitHub/batocera.linux/output/images/recalbox/boot.tar.xz
creating /home/juliano/GitHub/batocera.linux/output/images/recalbox/batocera.img
Total number of sectors (2457568) not a multiple of sectors per track (63)!
Add mtools_skip_check=1 to your .mtoolsrc file to skip this test
Total number of sectors (2457568) not a multiple of sectors per track (63)!
Add mtools_skip_check=1 to your .mtoolsrc file to skip this test
vfat(boot.vfat): adding file 'boot/grub/grub.cfg' as 'boot/grub/grub.cfg' ...
Total number of sectors (2457568) not a multiple of sectors per track (63)!
Add mtools_skip_check=1 to your .mtoolsrc file to skip this test
vfat(boot.vfat): failed to generate boot.vfat
Makefile:749: recipe for target 'target-post-image' failed
make: *** [target-post-image] Error 1

Ma3ztro

This is easy to work around using the hint in the error message:

Add mtools_skip_check=1 to your .mtoolsrc file to skip this test

jdorigao

Ma3ztro It worked, thank you!

nadenislamarre

you can change the value in https://github.com/batocera-linux/batocera.linux/blob/master/board/recalbox/grub2/genimage.cfg#L51
too,

from one version to an other, we get this warning.
i've not understand what's the correct value to put so that it works on all ubuntu versions.

jdorigao

This value is being a puzzle if it works in one way does not work in the other.
Using the (Add mtools_skip_check = 1 to your .mtoolsrc file to skip this test) is a good alternative until we find the correct value

d3m0n1q_733rz

The problem may be related to GCC 7.0 which the newest Ubuntu utilizes. GCC 7 utilizes the latest C++ standards and tends to error or warn on code that would have otherwise compiled regardless of whether it was actually "correct". The are a number of packages which fall victim to this standard change, though you should be able to pass a flag to use C99 by default or a standard between now and 1999.
Hope this helps.