From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] sh: Fix Buildroot sh targets to match gnuconfig targets
Date: Tue, 10 May 2011 09:48:05 +0200 [thread overview]
Message-ID: <20110510094805.5d044298@surf> (raw)
In-Reply-To: <OF668F5E2A.89729554-ONC125788C.00277D08-8025788C.002987DD@eu.necel.com>
Hello,
On Tue, 10 May 2011 08:34:19 +0100
PHIL.EDWORTHY at renesas.com wrote:
> > Not your fault, but we should probably try to use BR2_ENDIAN here, in
> > order to have the big/little endian list of architectures in a common
> > location and not duplicated here in JFFS2. But that's a separate
> > matter, and should be fixed in a separate patch.
>
> Yes, I thought that as well. I took the view that a simple update for the
> moment was best.
Sure.
> When I created this patch I tried to build some SH toolchains using BR.
> This failed for both SH2A and SH4A and I probably can't find the time to
> fix these at the moment. I only use the pre-built CodeSourcery toolchains.
>
> So to answer your question about elf2flt, I don't know. However, I noticed
> the targets were wrong so I thought it would make sense to correct it as its
> related. Unfortunately, I know nothing about elf2flt...
Ok :-)
Thanks again,
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-10 7:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 13:12 [Buildroot] [PATCH] sh: Fix Buildroot sh targets to match gnuconfig targets Phil Edworthy
2011-05-10 6:47 ` Thomas Petazzoni
2011-05-10 7:34 ` PHIL.EDWORTHY at renesas.com
2011-05-10 7:48 ` Thomas Petazzoni [this message]
2011-05-10 8:01 ` Yann E. MORIN
2011-05-10 8:20 ` Thomas Petazzoni
2011-05-10 8:35 ` Yann E. MORIN
2011-07-18 21:26 ` 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=20110510094805.5d044298@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 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.