From: Shaz <shazalive@gmail.com>
To: linux-embedded <linux-embedded@vger.kernel.org>
Subject: Re: Cross Compiler and loads of issues
Date: Fri, 13 Jun 2008 17:00:34 +0500 [thread overview]
Message-ID: <7b740b700806130500u17bf3adel3b2139e50d7b029f@mail.gmail.com> (raw)
In-Reply-To: <20080613092449.GO27937@knossos.aleph1.co.uk>
It's nice to see we have so many options and related people and pros
to it are available around.
IMO there should be some sort of effort to standardize the tool-chains
and build environments coherently with the kernel. I think its a prime
time to work around all the possibilities and standardize so that a
collaborative effort similar to Linux kernel can be set ahead. I think
thats the objective of this list too. Any plans yet sorted out?
On Fri, Jun 13, 2008 at 2:24 PM, Wookey <wookey@wookware.org> wrote:
>
> On 2008-06-12 22:52 +0500, Shaz wrote:
> > 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.
>
> 'issues' are generally par for the course. It's a difficult problem.
> I've generally found buildroot the least-painful of the above, largely
> because it targets a relatively small section of the problem-space.
>
> For completeness I should also mention that Embedded Debian provides
> yet another option. I will not claim that it will have fewer issues
> than the above. http://www.emdebian.org/emdebian/intro.html
>
> I'm not sure if you are really asking about toolchains or build-systems?
> The former is fairly reliably solved. For a debian-based box just
> install pre-built cross toolchians from emdebian:
> http://www.emdebian.org/tools/crosstools.html
> (from i386, amd64, powerpc; to: nearly all debian-supported
> architectures, gcc3.3, 3.4, 4.1, 4.2, 4.3)
> http://www.emdebian.org/toolchains/search.php?section=devel gives more
> details.
>
> emdebian-tools also provides the debian equivalent of crosstool
> ('emchain' to build your own version of current current toolchain,
> should a suitable pre-built one not exist.
>
> For non-debian boxes other people seem to have listed the options so I
> won't repeat (and it's not my area of expertise).
>
> Wookey (Emdebian 'Chief bullshitter' - bias alert. The toolchains are
> great though, really.)
> --
> Principal hats: Balloonz - Toby Churchill - Aleph One - Debian
> http://wookware.org/
--
Shaz
next prev parent reply other threads:[~2008-06-13 12:00 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
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 [this message]
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=7b740b700806130500u17bf3adel3b2139e50d7b029f@mail.gmail.com \
--to=shazalive@gmail.com \
--cc=linux-embedded@vger.kernel.org \
/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).