From: Ramana Radhakrishnan <ramana.r@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: paawan oza <paawan1982@yahoo.com>, Hui Zhu <teawater@gmail.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: porting reversible on arm/mips
Date: Fri, 11 Dec 2009 19:37:00 -0000 [thread overview]
Message-ID: <67ea2eb0912111137u687fc104q2f269b0fb245d4bd@mail.gmail.com> (raw)
In-Reply-To: <4B2299B2.3000806@vmware.com>
On Fri, Dec 11, 2009 at 7:12 PM, Michael Snyder <msnyder@vmware.com> wrote:
> Fair enough.
>
> Ramana, do you have a favorite online guide or "how-to"
> for someone who wants to start building an arm cross tool chain?
Depends on what you want to do here -
If you are looking to build cross bare-metal toolchains - I prefer to
use the combined build method as here
http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc with the
--target=arm-eabi option. I use that for most of my development
activity and that works just fine.
I haven't been following the gdb reverse work as closely as I should
but if your work doesn't involve tweaking the kernel and is only in
gdb userland, then there are some ARM devel boards running GNU/Linux
available on the GCC compile farm for use by open source developers.
You could contact Laurent Guerby for access to these boards.
http://gcc.gnu.org/wiki/CompileFarm
If you want to build ARM Linux cross-tools using eglibc, then using a
script based on instructions as in the eglibc repository are what I
use and have set up successfully. Dan Kegel's crosstool appears to be
very good for building with older configurations but I'm not sure how
it copes with the new ports infrastructure in (e)glibc.
cheers
Ramana
>
>
next prev parent reply other threads:[~2009-12-11 19:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 2:42 About the link to wiki in reversible.html Hui Zhu
2009-12-10 8:14 ` porting reversible on arm/mips paawan oza
2009-12-10 23:59 ` Michael Snyder
2009-12-11 2:10 ` paawan oza
2009-12-11 2:15 ` Hui Zhu
2009-12-11 13:03 ` paawan oza
2009-12-11 16:38 ` Sean Chen
2009-12-11 3:12 ` Michael Snyder
2009-12-11 3:48 ` Sean Chen
2009-12-11 8:16 ` Jakob Engblom
2009-12-11 13:24 ` paawan oza
2009-12-11 16:42 ` Sean Chen
2009-12-11 16:35 ` Sean Chen
2009-12-11 13:07 ` paawan oza
2009-12-11 18:50 ` Michael Snyder
2009-12-11 19:04 ` Ramana Radhakrishnan
2009-12-11 19:14 ` Michael Snyder
2009-12-11 19:37 ` Ramana Radhakrishnan [this message]
2009-12-12 3:28 ` paawan oza
2009-12-14 15:42 ` paawan oza
2009-12-14 18:27 ` Michael Snyder
2009-12-10 8:15 ` About the link to wiki in reversible.html Joel Brobecker
2010-03-20 9:28 porting reversible on arm/mips paawan oza
2010-03-22 4:30 ` Sean Chen
2010-03-22 12:31 ` Joseph S. Myers
2010-03-22 14:08 ` paawan oza
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=67ea2eb0912111137u687fc104q2f269b0fb245d4bd@mail.gmail.com \
--to=ramana.r@gmail.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
--cc=paawan1982@yahoo.com \
--cc=teawater@gmail.com \
/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