From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Bug in the grub patches
Date: Wed, 4 Dec 2013 09:11:34 +0100 [thread overview]
Message-ID: <20131204091134.526e0558@skate> (raw)
In-Reply-To: <OFA9DEB6A7.487A9EC5-ON86257C36.007BBF5E-86257C36.007CA347@rockwellcollins.com>
Dear Matthew Weber,
Please do not reply to an existing e-mail when you're starting a new
discussion. You're breaking discussion threads by doing so. When you
start a new discussion, simply create a new e-mail.
On Tue, 3 Dec 2013 16:41:22 -0600, Matthew Weber wrote:
> It looks like since (nov30) 9b3904543ca04c5d5fe5f6974539eed376de2290 the
> grub pkg now fails when build on a x86_64 for a x86 target. While using
> an external glibc codesourcery_x86 201209 toolchain.
> This last error looks like a 32 vs 64bit issue.
>
> I'm guessing the build for x86 on a x86_64 patches introduced this, but I
> haven't made it through all recent grub updates yet.
Thanks for this report! However, I have been unable to reproduce: I am
building on a 64 bits machine (uname -m reports x86_64), and grub
builds fine with the codesourcery x86 2012.09 toolchain. More
specifically, I've built the following configuration:
BR2_x86_64=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_INIT_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
# BR2_TARGET_ROOTFS_TAR is not set
BR2_TARGET_GRUB=y
Can you give me your Buildroot .config, as well as the complete build
log of Grub, and the Grub config.log file?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-12-04 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 22:15 [Buildroot] [PATCH v2] package/tvheadend: unbreak Yann E. MORIN
2013-12-03 22:41 ` [Buildroot] Bug in the grub patches Matthew Weber
2013-12-04 8:11 ` Thomas Petazzoni [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=20131204091134.526e0558@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