From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12946] Grub: Decompressor is too big.
Date: Thu, 28 May 2020 20:21:30 +0000 [thread overview]
Message-ID: <bug-12946-163-Cp08qk0uZO@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12946-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12946
--- Comment #8 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Stefan,
> which part is it that you cannot reproduce on your system - the build failure related to automake, or the original issue, i.e. the error thrown by grub-mkimage?
Obviously it is your original issue I am speaking about, and that I can't
reproduce.
> The original issue seems to depend on the environment's compiler used, not the one selected in Buildroot. According to https://lists.gnu.org/archive/html/grub-devel/2020-03/msg00217.html, it only occurs at least with GCC 8.3.0 and GCC 9.2.1 (which I am using), but not with GCC 7.5.0.
As I said, I am also on Ubuntu 19.10, so using gcc 9.2.1.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-28 20:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 14:46 [Buildroot] [Bug 12946] New: Grub: Decompressor is too big bugzilla at busybox.net
2020-05-25 14:46 ` [Buildroot] [Bug 12946] " 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 [this message]
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-Cp08qk0uZO@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.