public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Li Weichen" <iaadoa@gmail.com>
To: u-boot-users@lists.sourceforge.net,
	linux-arm-toolchain@lists.arm.linux.org.uk,
	linux-arm@lists.arm.linux.org.uk,
	linux-omap-open-source@linux.omap.com
Subject: Toolchain select
Date: Thu, 5 Jan 2006 21:38:36 +0800	[thread overview]
Message-ID: <43bd2165.6762f2e2.3596.51a6@mx.gmail.com> (raw)

Hi all,

I encountered several toolchain problems while cross-compiling such as
u-boot, kernel.  I find it mostly problem about the version.  I don't know
which one is proper and stable for embedded system developing.  Could you
please help me?

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.

Regards,

Li Weichen
2006-1-5



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

             reply	other threads:[~2006-01-05 13:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-05 13:38 Li Weichen [this message]
2006-01-05 22:00 ` Toolchain select Matthew Percival
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=43bd2165.6762f2e2.3596.51a6@mx.gmail.com \
    --to=iaadoa@gmail.com \
    --cc=linux-arm-toolchain@lists.arm.linux.org.uk \
    --cc=linux-arm@lists.arm.linux.org.uk \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=u-boot-users@lists.sourceforge.net \
    /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