grub-devel
[Top][All Lists]
Advanced

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

Re: make check: grub-mkrescue fails missing unicode.pf2. Leftovers in /t


From: Thomas Schmitt
Subject: Re: make check: grub-mkrescue fails missing unicode.pf2. Leftovers in /tmp
Date: Mon, 13 Feb 2023 09:53:20 +0100

Hi,

Vladimir Serbinenko wrote:
> Look at the end of configure message. Is free type enabled? Was unifont
> found?

--------------------------------------------------------------------
$ ./configure
...
checking whether -Wtrampolines work... yes
checking for freetype2... yes
checking ft2build.h usability... yes
checking ft2build.h presence... yes
checking for ft2build.h... yes
checking whether byte ordering is bigendian... no
checking for freetype2... yes
checking ft2build.h usability... yes
checking ft2build.h presence... yes
checking for ft2build.h... yes
checking for fuse3... no
...
*******************************************************
GRUB2 will be compiled with following components:
Platform: i386-pc
With devmapper support: No (need libdevmapper header)
With memory debugging: No
With disk cache statistics: No
With boot time statistics: No
efiemu runtime: Yes
grub-mkfont: Yes
grub-mount: No (need fuse or fuse3 libraries)
starfield theme: No (No DejaVu found)
With libzfs support: No (need zfs library)
Build-time grub-mkfont: No (no fonts)
Without unifont (no build-time grub-mkfont)
With liblzma from -llzma (support for XZ-compressed mips images)
With stack smashing protector: No
*******************************************************
--------------------------------------------------------------------

So i would say "freetype2" yes, "unifont" no.

(The system is Debian 11 amd64.)


The test log says:
  FAIL grub_func_test (exit status: 1)
In ./grub_func_test i see

  # Increase memory as some of tests are high-resolution and need a lot of 
memory.
  out=`echo all_functional_test | ./grub-shell --timeout=3600 
--files="/boot/grub/fonts/unicode.pf2"="./"unicode.pf2 --qemu-opts="-m $mem"`

I believe to see the grub-mkrescue invocation in tests/util/grub-shell.in

    exec_show_error "${builddir}/grub-mkrescue" "--output=${isofile}" \
        "--override-directory=${builddir}/grub-core" \
        --rom-directory="${rom_directory}" \
        --locale-directory="${srcdir}/po" \
        --themes-directory="${srcdir}/themes" \
        $mkimage_extra_arg ${mkrescue_args} \
        "/boot/grub/grub.cfg=${cfgfile}" "/boot/grub/testcase.cfg=${source}" \
        ${files} || exit $?

As proof i added a pathspec with an existing filename before ${files}:

-        ${files} || exit $?
+        /x=/home/thomas/x ${files} || exit $?

This file path then appears in the test failure message:

  Added to ISO image: file '/x'='/home/thomas/x'
  xorriso : FAILURE : Cannot determine attributes of source file 
'/home/thomas/projekte/grub_dir/grub/unicode.pf2' : No such file or directory

So i am sure that the xorriso run in grub-shell.in is the one which fails
and that the bad filename comes from ${files}.
I suspect that ${files} comes from the "--files=" argument that is given
to ./grub-shell by tests/util/grub-shell.in.


Have a nice day :)

Thomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]