From: Goetz Bock <bock@blacknet.de>
To: buildroot@busybox.net
Subject: [Buildroot] Building x86_64 failes
Date: Sat, 20 Jan 2007 13:51:16 +0100 [thread overview]
Message-ID: <20070120125116.GJ14371@priv.blacknet.de> (raw)
In-Reply-To: <20070119150806.GA16887@aon.at>
On Fri, Jan 19 '07 at 16:08, Bernhard Fischer wrote:
> On Fri, Jan 19, 2007 at 02:31:53PM +0100, Goetz Bock wrote:
> > [ ... I'm unable to build buildroot toolchain for x96_64 ... ]
> >/build/buildroot.amd64/toolchain_build_x86_64/gcc-4.1.1/gcc/config/i386/linux-unwind.h:
> >In function 'x86_fallback_frame_state':
> >/build/buildroot.amd64/toolchain_build_x86_64/gcc-4.1.1/gcc/config/i386/linux-unwind.h:152:
> >error: 'struct sigcontext' has no member named 'esp'
> >.
> >. [ more missing e?? members ]
> >.
>
> Can you check that uClibc has the correct arch set?
The toolchain_build_x86_64/uClibc-0.9.28/.config lists:
TARGET_x86_64=y
ARCH_SUPPORTS_LITTLE_ENDIAN=y
TARGET_ARCH="x86_64"
ARCH_LITTLE_ENDIAN=y
KERNEL_SOURCE="/build/buildroot.amd64/toolchain_build_x86_64/linux"
In the KERNEL_SOURCE dir include/asm is linked to asm-x86_64
> What kernel-headers do you use?
I'm using the 2.6.12.0 headers, as my kernel will be 2.6.18 from Etch
> hm. Could it be that you try to compile a 32bit x86-64 compiler? For the
> 64bit, there is definately no (resp. shouldn't be a) esp.
That's at last not what I intend. I want to build a small rescueue
system to work with Debian Etch kernels.
--
/"\ Goetz Bock at blacknet dot de -- secure mobile Linux everNETting
\ / (c) 2006 Creative Commons, Attribution-ShareAlike 2.0 de
X [ 1. Use descriptive subjects - 2. Edit a reply for brevity - ]
/ \ [ 3. Reply to the list - 4. Read the archive *before* you post ]
next prev parent reply other threads:[~2007-01-20 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 13:31 [Buildroot] Building x86_64 failes Goetz Bock
2007-01-19 15:08 ` Bernhard Fischer
2007-01-20 12:51 ` Goetz Bock [this message]
2007-01-20 17:29 ` Bernhard Fischer
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=20070120125116.GJ14371@priv.blacknet.de \
--to=bock@blacknet.de \
--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