From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot and sh4
Date: Fri, 4 Jun 2010 09:36:35 +0200 [thread overview]
Message-ID: <20100604093635.3c27d0d1@surf> (raw)
In-Reply-To: <618052.82706.qm@web23107.mail.ird.yahoo.com>
Hello Philippe,
Thanks for this documentation and your efforts to build a working
demonstration of Buildroot on sh4 with Qemu!
On Thu, 3 Jun 2010 22:08:17 +0000 (GMT)
Philippe Reynes <tremyfr@yahoo.fr> wrote:
> ??? GCC compiler Version => 4.4.x
> ??? Additionnal gcc options => --with-multilib-list=m4,m4-nofpu
Does this actually work ?
To produce a multilib toolchain, you need to build the C library as
many times as you have items in this "with-multilib-list". However, as
far as I understand Buildroot's code to generate toolchains, it only
builds uClibc once. Did you actually check that this multilib thing was
working ?
> I hope this little doc will be usefull, and I'll be pleased to get feedback,
I think it'd be great if we added a target/device/qemu directory, with
target/device/qemu/sh4-rd2 as a sub-directory, containing your kernel
configuration + a small README file saying how to run Qemu. Then, your
Buildroot config file could be added to the configs/ directory. This
ways, others could easily run this.
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:[~2010-06-04 7:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 22:08 [Buildroot] buildroot and sh4 Philippe Reynes
2010-06-04 7:36 ` Thomas Petazzoni [this message]
2010-06-04 8:39 ` Pierre Ficheux
2010-06-04 9:17 ` Thomas Petazzoni
2010-06-04 10:37 ` Peter Korsgaard
2010-06-04 22:12 ` Philippe Reynes
2010-06-07 9:14 ` Phil Edworthy
2010-07-03 10:52 ` Philippe Reynes
2010-07-27 22:16 ` Philippe Reynes
2010-11-07 18:28 ` Thomas Petazzoni
2010-11-10 14:11 ` Phil Edworthy
2010-11-14 22:09 ` trem
2010-11-15 22:26 ` Thomas Petazzoni
2010-11-28 20:07 ` trem
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=20100604093635.3c27d0d1@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