From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: RFC: grub-efi native tools
Date: Tue, 22 Nov 2011 23:44:06 -0800 [thread overview]
Message-ID: <4ECCA446.7080509@linux.intel.com> (raw)
In-Reply-To: <4ECC9A64.4080009@linux.intel.com>
On 11/22/2011 11:01 PM, Darren Hart wrote:
> 2) Only build grub-efi-native.
> - The above grub-mkimage command fails with some incorrect elf format
> error messages on the grub kernel.img file. A similar error was
> reported on the grub mailing list when compiling with cygwin.
> Some work may be required to fix GRUB here.
This turned out to be the result of TARGET_ARCH changing from the real
target arch to the BUILD_ARCH via the native.bbclass. I can force a
correct build by hard coding my target. So GRUB is off the hook.
If I cannot access the real TARGET_ARCH when building natively, then
perhaps I should not be trying to assemble a target image during this
step. I could install the native binaries and all the supporting files
in the native sysroot and assemble the target bootia32.efi binary either
as part of the bootimg functions (via a grub-efi.bbclass which depends
on the grub-efi-native do_sysroot)...
This seems pretty round about, and I would prefer for a grub-efi recipe
to deploy (to tmp/deploy/images) a bootia32.efi file. This means that
the grub utilities need to be built native, but grub needs to be
configured with --target=i586 (even when my BUILD_ARCH is x86_64). This
seems to not fit well with how the tooling is setup.
Is there perhaps a better approach?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
prev parent reply other threads:[~2011-11-23 7:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 7:01 RFC: grub-efi native tools Darren Hart
2011-11-23 7:36 ` Koen Kooi
2011-11-23 8:01 ` Darren Hart
2011-11-23 8:10 ` Paul Eggleton
2011-11-23 8:14 ` Darren Hart
2011-11-23 7:44 ` Darren Hart [this message]
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=4ECCA446.7080509@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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