From: "Robert Wörle" <robert@linuxdevelopment.de>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: Stuck with AVR32 segfaults in init
Date: Wed, 12 Mar 2008 07:13:56 +0100 [thread overview]
Message-ID: <47D774A4.3040207@linuxdevelopment.de> (raw)
In-Reply-To: <1205277784.16531.18.camel@dax.rpnet.com>
>
> If you take an OE binary and run it within a working filesystem from
> whereever, what happens? If it segfaults there you may be able to debug
> it. If it doesn't, try copying libs from OE into that system until it
> breaks? That should at least tell you where the problem is.
Dear all
I was starting a oe build the day koen announced the merge and it went
with some obstacles and finished the major libs nicely but i cant tell
what i had to do to get past the uclibc parts.
I did then get a 0.9.28 based libs and apps which i now merge with a
atmel bsp kernel and uClibc.
So i can now run all oe libs ( beside uClibc) with that and it feels
wonderful. I am currently running the ngw100 with a 5.7 lcd attached and
can get up a Xfbdev + gtk+ + x11vnc within the nand and nor ( totale of
16 mb) Hurray the power if footprinting of oe !!
But i am also stuck now redoing this and rebuilding a new oe toolchain
for avr32 . I cant get pass the external-toolchain ERROR mentioned in
some earlier mails.
I tried both oe uclibc 0.9.28 and 0.9.29
So i now have one tool chain up and running and i can go on to develop
my target application but nobody is allowed to touch my laptop with that
toolchain or he dies !!
Maybe we need some of the guru`s here to help us poor avr32 small users
to get the basic oe toolchain up and running and stable at least for the
ucLibc part.
Robert
>
next prev parent reply other threads:[~2008-03-12 6:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 22:46 Stuck with AVR32 segfaults in init Geoffrey Wossum
2008-03-11 23:23 ` Richard Purdie
2008-03-12 6:13 ` Robert Wörle [this message]
2008-03-12 7:31 ` Khem Raj
2008-03-12 8:02 ` Robert Wörle
2008-03-12 9:08 ` Richard Purdie
2008-03-12 19:52 ` Stelios Koroneos
2008-03-12 16:00 ` Geoffrey Wossum
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=47D774A4.3040207@linuxdevelopment.de \
--to=robert@linuxdevelopment.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.