From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] sh: Add SH2A CodeSourcery external toolchain
Date: Sun, 8 May 2011 20:28:47 +0200 [thread overview]
Message-ID: <20110508202847.0996a987@surf> (raw)
In-Reply-To: <1304691784-29011-1-git-send-email-phil.edworthy@renesas.com>
Hello,
On Fri, 06 May 2011 15:23:04 +0100
Phil Edworthy <PHIL.EDWORTHY@renesas.com> wrote:
> Added the CodeSourcery uCLinux/uClibc toolchain for the SH2A big
> endian devices.
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
However, I have a question regarding the sh2a_nofpueb and sh2eb target
architecture variants to which this toolchain applies. In Buildroot, we
use the target architecture variant to build the host tuple, which is
then used as the --host=XXX-YYY argument to build autotools-based
packages.
So for example, when sh2eb is selected, we pass "--host=sh2eb-linux" to
the ./configure script of all autotools-based packages.
Unfortunately, neither sh2a_nofpueb nor sh2eb are recognized as correct
machine types by config.sub. From packages/gnuconfig/config.sub:
| sh | sh[1234] | sh[24]a | sh[24]aeb | sh[23]e | sh[34]eb | sheb | shbe | shle | sh[1234]le | sh3ele \
| sh64 | sh64le \
So, a package such as dropbear fails to build with:
checking host system type... Invalid configuration `sh2eb-linux': machine `sh2eb' not recognized
I don't know anything about the various CPU types in the SuperH world,
so I can't fix it myself, but obviously the target variants do need
some cleanup/improvements. Could you help us to improve this ?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-05-08 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 14:23 [Buildroot] [PATCH] sh: Add SH2A CodeSourcery external toolchain Phil Edworthy
2011-05-08 18:28 ` Thomas Petazzoni [this message]
2011-05-09 6:54 ` PHIL.EDWORTHY at renesas.com
2011-07-12 21:30 ` Peter Korsgaard
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=20110508202847.0996a987@surf \
--to=thomas.petazzoni@free-electrons.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