From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: Init fails with segfault on AVR32
Date: Tue, 12 Feb 2008 11:43:35 +0000 [thread overview]
Message-ID: <1202816615.8288.62.camel@dax.rpnet.com> (raw)
In-Reply-To: <47B180DC.1040107@miromico.ch>
On Tue, 2008-02-12 at 12:19 +0100, Alex wrote:
> While waiting for support from the mailinglist I tried a few more things
> to get my atngw100 system running.
>
> I tried to use init from (statically linked) busybox. This will suffer
> the same problem but gives me a better clue where
> the problem lies.
>
> I found out that in a first step /bin/mount.util-linux is responsible
> for the segfault. And this is due to the shared library
> "ld-uClibc-0.9.28".
>
> If I replace this library with ld-uClibc-0.9.29 from atmel's buildroot.
> The segfault is gone!
>
> There are rumours that some of you have OE running on ATNGW100 hardware.
> So what can I make wrong?
> Can someone send me his local.conf?
> I update OE from time to time in the hope this will save my problems.
>
> I use:
> - bitbake version 1.18.11
> - monotone 0.31
>
> And I update OE using the following commands:
> > mtn --db=/oe/OE.mtn pull monotone.openembedded.org org.openembedded.dev
> > cd /oe/org.openembedded.dev && mtn update
>
> Hope someone can help me. I'm trying for weeks to get this stuff
> running....
I don't have any AVR hardware but narrowing it down to a library like
that is a great step forward. Can you see any differences in the patches
or versions used to build uclibc between buildroot and OE?
Cheers,
Richard
next prev parent reply other threads:[~2008-02-12 11:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 13:08 Init fails with segfault on AVR32 Alex
2008-02-12 11:19 ` Alex
2008-02-12 11:43 ` Richard Purdie [this message]
2008-02-12 12:19 ` Alex
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=1202816615.8288.62.camel@dax.rpnet.com \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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