From: Matthew Percival <matthew@capgo.com>
To: Linux OMAP Open Source <linux-omap-open-source@linux.omap.com>
Subject: Re: Toolchain select
Date: Fri, 06 Jan 2006 09:00:50 +1100 [thread overview]
Message-ID: <1136498450.8801.7.camel@localhost.localdomain> (raw)
In-Reply-To: <43bd2165.6762f2e2.3596.51a6@mx.gmail.com>
G'Day,
> I have already used the crosstool to make my own toolchain, and chose the
> gcc-4.0.1, binutils-2.16.1, glibc-2.3.5. But it seems that it has some
> problem. When I build u-boot it shows that the examples cannot be compiled.
u-boot may not be a good test. Versions of u-boot older than 1.1.4 do
not compile with 4.0 at all; even 1.1.4 seems to have problems, as some
users have reported that it does not compile (most seem to be OK, but
there are a few who cannot). You said that kernel did not compile
either, though, and that should work, so the problem in your case likely
lies with the toolchain.
My toolchain was compile with gcc-4.0.1, binutils-2.15 and glibc 2.3.5:
this combination is known to work. Looking at the crosstool buildlogs,
your combination is not listed, so it is somewhat of an unknown
quantity, though it sounds like the combination you have picked does not
work. I would recommend looking at the crosstool buildlogs yourself, to
see what combinations are known to work, and sticking with them, unless
you want to experiment with different combinations.
-- Matthew
next prev parent reply other threads:[~2006-01-05 22:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 13:38 Toolchain select Li Weichen
2006-01-05 22:00 ` Matthew Percival [this message]
2006-01-06 12:13 ` Li Weichen
2006-01-08 21:48 ` Matthew Percival
2006-01-09 2:10 ` Li Weichen
2006-01-09 3:06 ` Matthew Percival
2006-01-09 3:23 ` Li Weichen
2006-01-09 18:32 ` Khem Raj
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=1136498450.8801.7.camel@localhost.localdomain \
--to=matthew@capgo.com \
--cc=linux-omap-open-source@linux.omap.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