On Wed, 2012-04-18 at 13:30 +0200, Andreas Oberritter wrote: > now, after having repacked all binary tarballs that had mipsel or > mipsel-nf in their name and contents, and after having changed all > occurrences of mipsel and mipsel-nf in my local recipes (where > appropriate), and after having rebuilt everything from scratch again, it > came to my attention that "mipsel" in PACKAGE_EXTRA_ARCHS breaks opkg, > because no mipsel packages are being generated. That's what I told > before, right?
How is this breaking opkg? We often have architectures listed in there for which there are no packages generated (all, noarch and any spring to mind)? Cheers, Richard _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
