From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building x86_64 failes
Date: Fri, 19 Jan 2007 16:08:06 +0100 [thread overview]
Message-ID: <20070119150806.GA16887@aon.at> (raw)
In-Reply-To: <20070119133153.GH14371@priv.blacknet.de>
On Fri, Jan 19, 2007 at 02:31:53PM +0100, Goetz Bock wrote:
>Dear list,
>
>after I've successfully build buildroot for i586 on my
>amd64/debian/sarge box, I wanted to build the same rootfs for amd64.
>
>So I copied the existing buildroot, removed build_i586 and
>toolchain_build_i586, ran make clean and make menuconfig to
>reconfigureit for x86_64.
>
>But building the toolchain failes with:
>
>/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?
>
>It does not matter what version of binutils/gcc I use, it's always the
>same error.
>(I've tried binutuils: 2.16.1, 2.17, 2.17.50.0.7, 2.17.50.0.9 and gcc
>4.0.3, 4.1.1, 4.2)
>
>The i386 realy irritates me, and I've no idea where it comes from.
The config/i386 is ok
What kernel-headers do you use?
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.
next prev parent reply other threads:[~2007-01-19 15:08 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 [this message]
2007-01-20 12:51 ` Goetz Bock
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=20070119150806.GA16887@aon.at \
--to=rep.dot.nop@gmail.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