All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goetz Bock <bock@blacknet.de>
To: buildroot@busybox.net
Subject: [Buildroot] Building x86_64 failes
Date: Fri, 19 Jan 2007 14:31:53 +0100	[thread overview]
Message-ID: <20070119133153.GH14371@priv.blacknet.de> (raw)

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 ]
.

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.

Any pionters?
-- 
/"\ 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 ]

             reply	other threads:[~2007-01-19 13:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 13:31 Goetz Bock [this message]
2007-01-19 15:08 ` [Buildroot] Building x86_64 failes Bernhard Fischer
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=20070119133153.GH14371@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 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.