From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5024] New: grub fails to build for x86_64 target architecture
Date: Wed, 4 Apr 2012 09:15:08 +0000 (UTC) [thread overview]
Message-ID: <bug-5024-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=5024
Summary: grub fails to build for x86_64 target architecture
Product: buildroot
Version: 2012.02
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: zkdigisec at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 4232
--> https://bugs.busybox.net/attachment.cgi?id=4232
grub autoconf log file
When buildroot is configured for x86_64 as the target architecture, grub
configuration fails with the following error message:
checking for x86_64-linux-gcc... (cached)
/home/user/Downloads/buildroot-2012.02/output/host/usr/bin/x86_64-unknown-linux-uclibc-gcc
checking for C compiler default output file name... configure: error: C
compiler cannot create executables
See `config.log' for more details.
make: ***
[/home/user/Downloads/buildroot-2012.02/output/build/grub-0.97/.stamp_configured]
Error 77
The problem seems to be that the 32-bit libraries are not available (or used)
in the 64-bit cross-compiler toolchain.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-04-04 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 9:15 bugzilla at busybox.net [this message]
2013-11-14 0:22 ` [Buildroot] [Bug 5024] grub fails to build for x86_64 target architecture bugzilla at busybox.net
2013-12-04 20:40 ` 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-5024-163@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.