From: David Laight <David.Laight@ACULAB.COM>
To: "'Peter Seiderer'" <ps.report@gmx.net>,
"Köry Maincent" <kory.maincent@bootlin.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
"Walter, Stefan" <stefan.walter@iml.fraunhofer.de>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: [Buildroot] Grub2 changes since 2021.10.2
Date: Sat, 23 Oct 2021 16:20:41 +0000 [thread overview]
Message-ID: <e8b54604a28b4a35b266b5e788d92431@AcuMS.aculab.com> (raw)
Do the recent changes to grub2 make it any easier to install
the version of grub2 built by buildroot?
I'm pretty sure the commands in the scripts I inherited install
grub from the host system.
This is made much more likely because the actual boot disks
are made on a second system (by production, not development).
I've tried setting the BR option to include the grub objects
in the built 'root' filesystem.
While this adds files to the image, even when booted from the
disk the grub install program fails - IIRC due to missing files.
Either the host's own 'grub install' program needs to install
these files from somewhere (I could parcel them up somewhere else)
or I need to get the 'host' version of the required binaries
into my release (they should run on production's system, the
ones from the image itself won't).
This is all x86_64 using MBR disks (EFI causes too much grief).
I understand all about the x86 boot process (I rewrote NetBDS's
MBR and PBR code many years ago), but where grub2 installs anything
(and which programs update what) seems to have been deleted
from any user documentation.
AFAICT grub writes all over parts of the disk (like the rest of
track 0?) that aren't actually reserved for boot code.
I've also got a problem where the grub build objects to /usr/bin/gcc
being earlies that gcc 5.1 (it is 4.8.5 on a Centos 7 system).
I expected everything to be built with the gcc 10 I specified.
Has this been fixed by the recent changes to the CC path in the
grub package?
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2021-10-23 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 16:20 David Laight [this message]
2021-10-24 12:23 ` [Buildroot] Grub2 changes since 2021.10.2 Yann E. MORIN
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=e8b54604a28b4a35b266b5e788d92431@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=buildroot@buildroot.org \
--cc=kory.maincent@bootlin.com \
--cc=ps.report@gmx.net \
--cc=stefan.walter@iml.fraunhofer.de \
--cc=yann.morin.1998@free.fr \
/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.