[oe] gcc-cross-sdk (GCC 4.2.3) limits.h woes

Holger Hans Peter Freyther holger+oe at freyther.de
Wed Aug 19 03:17:21 UTC 2009


On Tuesday 18 August 2009 20:30:12 Chris Conroy wrote:
> Sorry for not providing more detail at first...
>
> With debian renaming on, glibc, for example, gets renamed to 'libc6' and
> packaged as such. Normally, this works because the other packages pick
> up the rename at some point along the way. The comment at the top of
> debian.bbclass states:
>
> # Debian package renaming only occurs when a package is built
> # We therefore have to make sure we build all runtime packages
> # before building the current package to make the packages runtime
> # depends are correct
>
> So, glibc is packaged as part of my toolchain's sdk. Building
> meta-toolchain works just fine. Then, I go to build an image using the
> external-toolchain. It fails because opkg cannot satisfy the dependency
> for 'glibc (>=2.7)'. This is because the ipkg generated by the debian
> rename is named 'libc6_2.7-r9_mipsel.ipk'. During the creation of the
> toolchain, all packages picked up this rename.

Have you seen this:
   http://docs.openembedded.org/usermanual/html/commonuse_prebuilt_toolchain.html#id388796


does it help in any way? To be honest I'm still missing how you try to create 
the image and if you rebuilt glibc or application or such..

	z.





More information about the Openembedded-devel mailing list