From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12946] New: Grub: Decompressor is too big.
Date: Mon, 25 May 2020 14:46:11 +0000 [thread overview]
Message-ID: <bug-12946-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12946
Bug ID: 12946
Summary: Grub: Decompressor is too big.
Product: buildroot
Version: 2020.02.2
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: stefan.walter at iml.fraunhofer.de
CC: buildroot at uclibc.org
Target Milestone: ---
I'm using grub-mkimage from a Buildroot SDK built with "make sdk" to create a
boot loader image that is later combined with a home partition image (using
genimage). After updating (from 2018.02.12) to 2020.02.2, when running
grub-mkimage --config="$grub_early.cfg" --directory="$GRUB_DIR" -o
"$OUTPUT_PATH"/grub_core.img --format=i386-pc --prefix==/boot/grub
${GRUB_MODULES}
I'm now seeing this:
grub-mkimage: error: Decompressor is too big.
I'm building on Ubuntu 19.10 with GCC 9.2.1. The problem itself seems to be
known with the Grub developers:
https://lists.gnu.org/archive/html/grub-devel/2020-03/msg00217.html
Is it possible to integrate the fix mentioned there for 2020.02.3?
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-05-25 14:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 14:46 bugzilla at busybox.net [this message]
2020-05-25 14:46 ` [Buildroot] [Bug 12946] Grub: Decompressor is too big bugzilla at busybox.net
2020-05-25 18:01 ` bugzilla at busybox.net
2020-05-26 6:17 ` bugzilla at busybox.net
2020-05-26 18:28 ` bugzilla at busybox.net
2020-05-27 7:19 ` bugzilla at busybox.net
2020-05-27 11:55 ` bugzilla at busybox.net
2020-05-27 20:20 ` bugzilla at busybox.net
2020-05-28 5:47 ` bugzilla at busybox.net
2020-05-28 20:21 ` bugzilla at busybox.net
2020-05-29 9:25 ` bugzilla at busybox.net
2020-05-29 9:38 ` bugzilla at busybox.net
2020-06-04 22:10 ` bugzilla at busybox.net
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=bug-12946-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.