From: peter.mueller@ipfire.org
To: development@lists.ipfire.org
Subject: Current 'next' branch fails to compile grub
Date: Sat, 07 Sep 2019 19:23:00 +0000 [thread overview]
Message-ID: <8e0229e6-e4f8-8bcc-e23a-ee0c0ad1669c@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2408 bytes --]
Hello *,
the current 'next' branch of IPFire 2.x fails to compile grub:
> grub (2.02) [ 34 ][ FAIL ]
>
> config.status: creating config-util.h
> config.status: linking include/grub/x86_64 to include/grub/cpu
> config.status: linking include/grub/x86_64/efi to include/grub/machine
> config.status: executing depfiles commands
> config.status: executing po-directories commands
> config.status: creating po/POTFILES
> config.status: creating po/Makefile
> *******************************************************
> GRUB2 will be compiled with following components:
> Platform: x86_64-efi
> With devmapper support: Yes
> With memory debugging: No
> With disk cache statistics: No
> With boot time statistics: No
> efiemu runtime: No (not available on efi)
> grub-mkfont: Yes
> grub-mount: No (need FUSE library)
> starfield theme: No (No DejaVu found)
> With libzfs support: No (need zfs library)
> Build-time grub-mkfont: Yes
> With unifont from ./unifont.pcf.gz
> With liblzma from -llzma (support for XZ-compressed mips images)
> *******************************************************
> cd /usr/src/grub-2.02-efi && make -j5
> make[1]: Entering directory '/usr/src/grub-2.02-efi'
> python gentpl.py Makefile.util.def Makefile.utilgcry.def > Makefile.util.am.new || (rm -f Makefile.util.am.new; exit 1)
> /bin/sh: python: command not found
> make[1]: *** [Makefile:12159: Makefile.util.am] Error 1
> make[1]: Leaving directory '/usr/src/grub-2.02-efi'
> make: *** [grub:108: /usr/src/log/grub-2.02] Error 2
>
> ERROR: Building grub [ FAIL ]
> Check /home/pmu/working/ipfire-2.x/log/_build.ipfire.log for errors if applicable [ FAIL ]
Anything I am doing wrong? Anybody else experiencing this error?
Footnote: Intention was to update Tor, iptables and libnetfilter_queue.
Just in case anybody else is currently at these, too. iproute2 also needs
a major update, but that will be a second step.
Thanks, and best regards,
Peter Müller
next reply other threads:[~2019-09-07 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 19:23 peter.mueller [this message]
2019-09-09 10:00 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8e0229e6-e4f8-8bcc-e23a-ee0c0ad1669c@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox