Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem booting 2.6.20.4 on AT91RM9200EK
Date: Thu, 19 Apr 2007 06:41:06 +0200	[thread overview]
Message-ID: <003e01c7823d$954a7810$01c4af0a@Glamdring> (raw)
In-Reply-To: 4626C339.6020603@geeo.net

> Ulf Samuelsson wrote:
>> Trying out linux-2.6.20.4 on an AT91RM9200EK
>> built by a buildroot downloaded 20070405 (with fixes).
>>
>>
>> Using gcc-3.4.6/binutils 2.16.1 initially built by buildroot
>> but now used as an external toolchain.
>>
>>
>> Getting the following error messages.
>>
>> /sbin/ init: can't load library 'libgcc_s.so.1'
>> Kernel panic - not syncing: Attempted to kill init!
>>
>>
>> Any clues?
>>
>> Found "toolchain_build_arm_small/gcc-3.4.6-final/gcc/libgcc_s.so.1"
>> which I guess is what I am looking for.
>> What is the approriate way to get that into the root file system?
>>
>>
>> [...]
> 
> I've had this problem in the past when I have defined 
> "BR2_GCC_SHARED_LIBGCC" via "Build/install a shared libgcc" in your 
> Toolchain Options. Unless you otherwise need it, you might try disabling 
> and rebuilding.
> 
> Jeremy
> 

Apparently this problem occurs if you remove the "root" directory"
without rebuilding the toolchain.
I 

Probably a ton of errors which results from this

Best Regards
Ulf Samuelsson

      reply	other threads:[~2007-04-19  4:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-18 22:18 [Buildroot] Problem booting 2.6.20.4 on AT91RM9200EK Ulf Samuelsson
2007-04-19  1:17 ` Jeremy R. Geeo
2007-04-19  4:41   ` Ulf Samuelsson [this message]

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='003e01c7823d$954a7810$01c4af0a@Glamdring' \
    --to=ulf@atmel.com \
    --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