Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick <kpa_info@yahoo.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Error when adding media-ctl as package
Date: Wed, 09 Jan 2013 17:08:32 +0100	[thread overview]
Message-ID: <50ED9600.1000700@yahoo.fr> (raw)
In-Reply-To: <50ED3A00.3060907@yahoo.fr>

On 01/09/2013 10:36 AM, Patrick wrote:
> On 01/09/2013 09:51 AM, Thomas Petazzoni wrote:
>> Dear Patrick,
>>
>> However, if your toolchain is too old, it may not contain sufficiently
>> up-to-date kernel headers. The simplest option is to try to update your
>> toolchain to a slightly more recent one, so that media.h is provided
>> directly with your toolchain, and we have nothing to do.
>>
>> Thomas
>>
> Ok I updated to a more recent toolchain and it works.
>

After changing the toolchain I have a really annoying side effect: my 
kernel do not boot anymore !

My previous toolchain was Sourcery G++ Lite 2009q1-203 GCC 4.3.3, my new 
toolchain is Sourcery CodeBench ARM 2012.03. I run Linux 3.0 on a Ti 
DM3730 processor.

With both toolchain I do not change the kernel configuration. With the 
old toolchain the kernel boot nicelly, with the new toolchain the kernel 
do not boot after u-boot message "Starting kernel ...". I use the same 
version of u-boot in both case with the same rootfs...

Any idea why changing the toolchain could result in this issue ?

Thanks in advance for any help

Patrick

  parent reply	other threads:[~2013-01-09 16:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 13:27 [Buildroot] Error when adding media-ctl as package Patrick
2013-01-08 20:18 ` Arnout Vandecappelle
2013-01-09  8:06   ` Patrick
2013-01-09  8:27     ` Thomas Petazzoni
2013-01-09  8:45       ` Patrick
2013-01-09  8:51         ` Thomas Petazzoni
2013-01-09  9:36           ` Patrick
2013-01-09  9:52             ` Thomas Petazzoni
2013-01-09 11:17               ` Patrick
2013-01-09 16:08             ` Patrick [this message]
2013-01-09 16:23               ` Thomas Petazzoni
2013-01-09 16:38                 ` Patrick

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=50ED9600.1000700@yahoo.fr \
    --to=kpa_info@yahoo.fr \
    --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