[Buildroot] [PATCH] sh: Add SH2A CodeSourcery external toolchain

PHIL.EDWORTHY at renesas.com PHIL.EDWORTHY at renesas.com
Mon May 9 06:54:57 UTC 2011

Hi Thomas,

> On Fri, 06 May 2011 15:23:04 +0100
> Phil Edworthy <PHIL.EDWORTHY at renesas.com> wrote:
> > Added the CodeSourcery uCLinux/uClibc toolchain for the SH2A big
> > endian devices.
> Acked-by: Thomas Petazzoni <thomas.petazzoni at 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

Ah, I see. I just checked busybox built for sh2a.

> 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 ?

Hmm, SuperH has a lengthy mix of cpu types & pretty much everything I have done is with sh4a devices. I'll ask around to find out a bit more about sh2
devices and attempt to clean this up.

Thanks for pointing this out!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110509/946da4b6/attachment-0002.html>

More information about the buildroot mailing list