From: "Bill Traynor" <wmat@naoi.ca>
To: Bill Traynor <wmat@naoi.ca>
Cc: Shaz <shazalive@gmail.com>,
linux-embedded <linux-embedded@vger.kernel.org>
Subject: Re: Cross Compiler and loads of issues
Date: Fri, 13 Jun 2008 09:52:59 -0400 (EDT) [thread overview]
Message-ID: <57fed5a348825cf4adedcd7b4b543254.squirrel@www.geekisp.com> (raw)
In-Reply-To: <402b1f4b315f572ac6459f78fa8b5ee4.squirrel@www.geekisp.com>
>> Hi,
>>
>> I have been following "Re: [PATCH 0/1] Embedded Maintainer(s)" and
>> felt like asking that is there one good way to get a cross compiler
>> work. I tried buildroot, scratchbox and even openMoko with
>> openEmbedded but all of them had lots of issues and don't know which
>> will be the best alternative.
>
> There is no "one good way". I've had decent success building Dan Kegel's
> "crosstool" in the past: http://www.kegel.com/crosstool/
>>
>> I also went through the material provided freely by Free Electron but
>> still I am not successful to build a custom kernel. Next I am trying
>> MontaVista's kit. I just wish I don't get lost.
>
> I'd continue the search for prebuilt toolchains. CodeSourcery has a Lite
> version of it's ARM, Coldfire, MIPS, and Power toolchains.
I should have pointed this out before, but there is a useful Toolchains
wiki page here: http://elinux.org/Toolchains
Feel free to contribute findings to that page.
>
>>
>> Anyways, I liked the idea of Qemu based cross compiler. Is it possible
>> for the inexperienced to get it working and emulate the exact model
>> and devices.
>>
>> --
>>
>> Shaz
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-embedded"
>> in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-embedded"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-06-13 13:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 17:52 Cross Compiler and loads of issues Shaz
2008-06-12 18:19 ` Wolfgang Denk
2008-06-14 9:44 ` Shaz
2008-06-12 18:26 ` Matthias Kaehlcke
2008-06-12 18:39 ` Bill Traynor
2008-06-12 18:49 ` Enrico Weigelt
2008-06-12 19:02 ` Shaz
2008-06-12 19:54 ` George G. Davis
2008-06-13 13:52 ` Bill Traynor [this message]
2008-06-12 18:56 ` Bill Gatliff
2008-06-12 19:30 ` Glenn Henshaw
2008-06-13 4:34 ` Robert Schwebel
2008-06-13 5:14 ` Wang, Baojun
2008-06-13 9:24 ` Wookey
2008-06-13 12:00 ` Shaz
2008-06-13 14:13 ` Bill Traynor
2008-06-13 14:46 ` Jamie Lokier
2008-06-13 15:19 ` Enrico Weigelt
2008-06-14 1:46 ` Jamie Lokier
2008-06-13 15:28 ` Bill Traynor
2008-06-13 17:12 ` Enrico Weigelt
2008-06-14 1:57 ` Jamie Lokier
2008-06-14 6:57 ` Greg Ungerer
2008-06-14 6:43 ` Greg Ungerer
2008-06-13 15:11 ` Shaz
2008-06-13 17:24 ` Firmware Linux (was Re: Cross Compiler and loads of issues) Rob Landley
2008-06-16 4:38 ` Enrico Weigelt
2008-06-25 1:49 ` Rob Landley
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=57fed5a348825cf4adedcd7b4b543254.squirrel@www.geekisp.com \
--to=wmat@naoi.ca \
--cc=linux-embedded@vger.kernel.org \
--cc=shazalive@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;
as well as URLs for NNTP newsgroup(s).