From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Compiling grub on x86_64
Date: Thu, 28 Jun 2012 11:56:13 +0200 [thread overview]
Message-ID: <20120628115613.7b4f26ad@skate> (raw)
In-Reply-To: <20120628114631.25da4786@skate>
Le Thu, 28 Jun 2012 11:46:31 +0200,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> a ?crit :
> Agreed. It's however a shame that it's not possible to build a complete
> bootloader+kernel+rootfs for x86_64 with a single Buildroot
> configuration :-(
>
> How other build systems handle this?
Other questions:
* What about using the host compiler to build Grub? I know it sounds a
bit funky, but in practice, most Buildroot users will work on
x86/x86_64 machines. If they are on x86, then it just works, if they
work on x86_64, then most likely they have a multilib 32/64
toolchain installed on their host. This would at least enable, for
most users, the possibility of building Grub as part of a x86_64
target system configuration.
* What does Grub really require from gcc_s? Is it impossible to rework
Grub to make independent from the compiler companion libraries?
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-06-28 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 7:51 [Buildroot] Compiling grub on x86_64 Arnout Vandecappelle
2012-06-25 8:04 ` Thomas Petazzoni
2012-06-28 8:09 ` Arnout Vandecappelle
2012-06-28 9:46 ` Thomas Petazzoni
2012-06-28 9:56 ` Thomas Petazzoni [this message]
2012-06-28 12:44 ` Arnout Vandecappelle
2012-06-28 13:06 ` Thomas Petazzoni
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=20120628115613.7b4f26ad@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox