All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10316] Building grub fails on debian stretch
Date: Fri, 15 Sep 2017 05:45:17 +0000	[thread overview]
Message-ID: <bug-10316-163-Dg0UXI1HgH@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10316-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=10316

--- Comment #2 from dde at innovaphone.com ---
I never played with grub2.
We build a buildroot ova image with qemu from a binary image where I use an
automated process which builds the partition table along with stage1/1.5 of
grub.

In the end, if you're going to remove grub, I can still either use already
built grub files and copy them manually or I need to figure out how to move to
grub2.

Greetings,
Daniel

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2017-09-15  5:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 11:32 [Buildroot] [Bug 10316] New: Building grub fails on debian stretch bugzilla at busybox.net
2017-09-15  0:10 ` [Buildroot] [Bug 10316] " bugzilla at busybox.net
2017-09-15  5:45 ` bugzilla at busybox.net [this message]
2018-01-10 22:09 ` 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-10316-163-Dg0UXI1HgH@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.