Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: buildroot@busybox.net
Subject: [Buildroot] Impossible to build EABI ARM gcc toolchain using	Buildroot ?
Date: Fri, 01 Dec 2006 03:11:39 -0500	[thread overview]
Message-ID: <1164960699.4870.67.camel@dv> (raw)
In-Reply-To: <loom.20061130T112254-849@post.gmane.org>

On Thu, 2006-11-30 at 11:14 +0000, MikeW wrote:
> This seems to be due to an incompatibility between:
> 1) toolchain.../gcc-x.x.x/config/arm/linux-elf.h
> 2) toolchain.../binutils-x.x.x/ld/earmelf_linux_eabi.c
> 
> In 1) there is a setting TARGET_LINKER_EMULATION "armelf_linux"
> In 2) there is a string (part of a struct initialiser) "armelf_linux_eabi"
> 
> so unless I can find matching strings in a version of gcc and ld,
> buildroot will never be able to build a toolchain.

There are already patches for gcc in buildroot that change
TARGET_LINKER_EMULATION for bigendian systems and uClibc.  I think
support for EABI belongs there too.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2006-12-01  8:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29 13:25 [Buildroot] Impossible to build EABI ARM gcc toolchain using Buildroot ? MikeW
2006-11-30  1:07 ` Pavel Roskin
2006-11-30 11:14   ` MikeW
2006-12-01  8:11     ` Pavel Roskin [this message]
2006-12-01 10:13       ` MikeW
2006-12-01 10:28         ` MikeW
2006-12-13 12:08       ` MikeW
2006-12-13 19:22         ` [Buildroot] Impossible to build EABI ARM gcc toolchain?using?Buildroot ? Bernhard Fischer
2006-12-14  9:40   ` [Buildroot] Impossible to build EABI ARM gcc toolchain using Buildroot ? MikeW
2006-12-18 11:37     ` MikeW
2006-12-18 12:15       ` [Buildroot] Impossible to build EABI ARM gcc toolchain?using?Buildroot ? Bernhard Fischer
2006-11-30 10:20 ` [Buildroot] Impossible to build EABI ARM gcc toolchain using Buildroot ? + MikeW

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=1164960699.4870.67.camel@dv \
    --to=proski@gnu.org \
    --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