Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] External toolchain
Date: Thu, 26 Mar 2009 00:36:26 +0100	[thread overview]
Message-ID: <20090325233625.GA20034@buzzloop.caiaq.de> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE1909014E2516@mi8nycmail19.Mi8.com>

On Wed, Mar 25, 2009 at 06:14:05PM -0400, H Hartley Sweeten wrote:
> This might not be the correct list to ask this on but I'll try anyway..
> 
> I have been using Buildroot with an external toolchain provided by
> Cirrus Logic for an ARM ep93xx based board. This toolchain has worked
> fine ever since I started using it.

Just curious - why don't you let buildroot build the toolchain for you?

[...]

> Now I have a problem I can't figure out.
> 
> I can get Buildroot to use the Code Sourcery toolchain and it compiles
> the 2.6.29 kernel fine. But, when I try to boot the kernel it just hangs
> after the "Uncompressing Linux.... done, booting the kernel." step.
> 
> I went back to kernel 2.6.28.8 and tried it with the Code Sourcery
> toolchain, same results. But, if I switch back to the Cirrus 4.1.1
> toolchain the kernel boots fine.

We had similar problems discussed on that list just recently. Not sure
whether you're facing exactly the same thing here, but it might be a
pointer.

The problem on other ARM based boards was configurations of gcc using
cpu-specific extensions by default which makes the kernel build system
used them to build the kernel - which eventually results in unbootable
images.

See this thread:

  http://lists.busybox.net/pipermail/buildroot/2009-March/026580.html

Hope that helps :) And if it does, it might be worth including some
proven to work configs in the buildroot repository.

Daniel

  reply	other threads:[~2009-03-25 23:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 22:14 [Buildroot] External toolchain H Hartley Sweeten
2009-03-25 23:36 ` Daniel Mack [this message]
2009-03-25 23:45   ` H Hartley Sweeten
  -- strict thread matches above, loose matches on Subject: below --
2009-12-01 13:59 [Buildroot] external toolchain Jonathan dumaresq
2009-12-01 14:33 ` Thomas Petazzoni
2009-12-01 14:38   ` Jonathan dumaresq
2009-12-01 14:49 ` Peter Korsgaard
2009-12-01 15:32   ` Jonathan dumaresq
2009-12-01 15:34     ` Peter Korsgaard
2009-12-01 20:16   ` Jonathan dumaresq
2009-12-01 20:32     ` Peter Korsgaard
2009-12-01 20:53       ` Jonathan dumaresq
2011-04-10  1:39 [Buildroot] External Toolchain Charles Krinke
2012-08-17 12:47 [Buildroot] external toolchain Zoran Djordjevic
2012-08-17 13:19 ` Yann E. MORIN
2012-08-17 18:05   ` Zoran Djordjevic
2012-08-18  7:33 Zoran Djordjevic
2012-08-18  9:47 ` Yann E. MORIN
2012-08-19 18:46 Zoran Djordjevic

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=20090325233625.GA20034@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=buildroot@busybox.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