Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: init becomes a zombie process on ARM device
Date: Sat, 19 Dec 2009 23:50:38 +0100	[thread overview]
Message-ID: <200912192350.39349.marcin@juszkiewicz.com.pl> (raw)
In-Reply-To: <4B2D3E19.6010402@mayer-electronics.de>

Dnia sobota, 19 grudnia 2009 o 21:56:57 Florian Mayer (Mayer Electronics) 
napisał(a):
> I found out why the system behaves such strange (thanks to Florian Boor 
> for pulling me in the right direction). In my constellation thumb 
> interworking does not work. glibc is arm compiled, the rest is thumb 
> format. To test it I added
> 
> ARM_INSTRUCTION_SET="arm"
> THUMB_INTERWORK="no"
> 
> to my machine configuration. But that did not help!
> 
> Both variables are overwritten in 
> openembedded/conf/dist/include/angstrom.inc. So I commented it out in 
> that file and voila, the result boots correctly. Is there a more elegant 
> way to solve this? Perhaps allow to configure this in the machine conf?

Start using OE to build your kernel and let your kernel recipe use linux.inc 
file. This will automatically enable Thumb support for your ARM cpu and 
Angstrom will start working without those hacks. 


Regards, 
-- 
JID:      hrw@jabber.org
Website:  http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz





  reply	other threads:[~2009-12-19 22:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18 12:10 init becomes a zombie process on ARM device Florian Mayer (Mayer Electronics)
2009-12-19 20:56 ` Florian Mayer (Mayer Electronics)
2009-12-19 22:50   ` Marcin Juszkiewicz [this message]
2009-12-20 14:21     ` Florian Mayer (Mayer Electronics)
2009-12-20 16:27     ` Xfbdev crashes Florian Mayer (Mayer Electronics)

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=200912192350.39349.marcin@juszkiewicz.com.pl \
    --to=marcin@juszkiewicz.com.pl \
    --cc=openembedded-devel@lists.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