From: MikeW <mw_phil@yahoo.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Impossible to build EABI ARM gcc toolchain using Buildroot ?
Date: Fri, 1 Dec 2006 10:13:59 +0000 (UTC) [thread overview]
Message-ID: <loom.20061201T110658-119@post.gmane.org> (raw)
In-Reply-To: 1164960699.4870.67.camel@dv
Pavel Roskin <proski@...> writes:
> 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.
>
So looking at 800-arm-bigendian.patch, it would appear
that I need to
1) in config.gcc, have a case $target that detects
*eabi and sets a TARGET_EABI flag
2) in linux-elf.h, have another #if TARGET_EABI ... #else ... #endif
which just tags "_eabi" onto all of the other strings, if EABI is active
Does this make sense ?
Or is there an official GCC patch to do this (I have searched!)
Since other people are building ARM EABI versions of gcc, there must
be a patch that they are using which somehow has been omitted
from Buildroot :(
Regards,
Mike
next prev parent reply other threads:[~2006-12-01 10:13 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
2006-12-01 10:13 ` MikeW [this message]
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=loom.20061201T110658-119@post.gmane.org \
--to=mw_phil@yahoo.co.uk \
--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