linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
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 15:46:58 +0100	[thread overview]
Message-ID: <20080613144658.GA21071@shareable.org> (raw)
In-Reply-To: <0af6abe442d0b93a10a96b27153f04e9.squirrel@www.geekisp.com>

Bill Traynor wrote:
> Maybe I'm being dense, but what's specifically wrong with the current
> toolchain universe?

Back in ye olde days, you could download GCC and Binutils from
gnu.org, configure for whatever is your architecture, and most times
it just worked.

For some reason, that stopped a while ago, and you had to go to
different places to get working basic tools.  And often, the place to
go wasn't clear.  Different people advertised their "ARM toolchain",
"m68k toolchain" etc.  and they were slightly different sets of
patches on top of mainline tools.  Central authorities you might
believe in existed, but they were always a few patches behind what you
actually needed.

When I last needed a toolchain, Google led to confusing results, and I
had to try more than one.  I still use mutiple GCC versions (from
different people) to compile different programs for the same
architecture: each one fails some things in a different way, including
run-time failures in the precompiled toolchains.

Just Google for "uclinux toolchain" and the top hits lead to very old
releases, with bugs that have long been fixed elsewhere.  "uclinux arm
toolchain" is no better.

Perhaps current versions (e.g. from Codesourcery?) are more dependable
for embedded architectures, but I don't have the time to thoroughly
test them, and my last experience warns me to be careful.

It seems people release tools, release patches, publish on an obscure
web page, then forget about the page.  More authoritative-sounding
uclinux web pages tend to be out of date.  Google isn't finding good
current authorities in this area, which suggests the space is rather
fragmented with people pulling in different directions and not working
together enough to create stable, common places for these things.

Contrast with kernel.org: everyone knows where to get a good working
Linux kernel for the mainstream architectures, and the quality work
tends to be quite good at reaching mainline there nowadays.

-- Jamie

  reply	other threads:[~2008-06-13 14:46 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
2008-06-13 14:13     ` Bill Traynor
2008-06-13 14:46       ` Jamie Lokier [this message]
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=20080613144658.GA21071@shareable.org \
    --to=jamie@shareable.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=shazalive@gmail.com \
    --cc=wmat@naoi.ca \
    /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).