[oe-users] Openembedded-users Digest, Vol 3, Issue 2

[James L Henrickson]

Thank you very much for your help, Koen.  I successfully generated an 
image that contains bind.  Having gotten over that hurdle, I am now free 
to move on to adding more packages to my image.  Thanks again for your help.

Jim


>Date: Sat, 16 Dec 2006 10:14:08 +0100
>From: Koen Kooi <koen at dominion.kabel.utwente.nl>
>Subject: Re: [oe-users] x86 uclibc
>To: Using OE <openembedded-users at openembedded.org>
>Message-ID: <4583B8E0.6000606 at dominion.kabel.utwente.nl>
>Content-Type: text/plain; charset=UTF-8
>
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>James L Henrickson schreef:
>  
>
>>Hi,
>>
>>I am a newbie to OpenEmbedded and I'm trying to get my feet wet with x86 
>>builds before trying other target platforms.  I was able to build a 
>>"normal" x86 target but even though I specified "bitbake bind", my 
>>resulting target did not include named.  Is there a trick to getting 
>>named/bind included in my target image?
>>    
>>
>
>'bitbake <something>' will just build <something>, it won't add it to the target image. If
>you want it in your target image you can choose from the following:
>
>1) add it to the RDEPENDS of the target images
>2) add it to DISTRO_EXTRA_RDEPENDS in your target distro configuration file
>
>
>  
>
>>I tried multiple times to build a "uclibc" x86 target, but it seems gcc 
>>isn't getting built.  I messed around with the local configuration file, 
>>but I can't seem to find anything that works.  If someone can 
>>successfully do this, can they forward me a copy of their configuration 
>>file?
>>    
>>
>
>uclibc 0.9.28 is now over a year old (http://www.codepoet.org/cake/img_1629.jpg) and the
>people that use uclibc are waiting for .29 to get released to fix it in OE.
>
>regards,
>
>Koen
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.5 (Darwin)
>
>iD8DBQFFg7jgMkyGM64RGpERAmF6AJ0eQ3FgEgS70PB7xOwqKgGCTW0aNQCgh8QT
>DIt09AcHoFLLFycYWlHm1wI=
>=hDxy
>-----END PGP SIGNATURE-----
>
>
>
>  
>