[oe] klcc-cross packaging issues

[Andrea Adami]

Hi,

I'm getting lost with this klibc recipe mixing buildhost and target...

I'd appreciate some advices about proper packaging for klcc-cross
(split from klibc recipe).

In order to remove the legacy do_stage from the recipe it sorted out
the perl-crosscompiler-wrapper (klcc) cannot be installed by the same
klibc recipe which packages target stuff.

So, klcc has now its own -cross recipe and is installed as
${D}${TOOLCHAIN_PATH}/bin/${TARGET_PREFIX}klcc but somehow is not
packaged (NOTE: the following files were installed but not shipped in
any package: TMPDIR/sysroots/i686-linux/usr/armv5te/bin/arm-angstrom-linux-gnueabi-klcc)

The issue raises now: the klcc-cross ipk is not created because it's
empty (nothing to install for target here).
Though, the staging-klcc-cross ipk seems sane, being that it contains
the crosscompiler and a correct fixme path.

Anyway, all's fine until here, one can build e.g. kexec-tools-klibc
from scratch or from packaged-staging and the build will succeed..

Still, the NOTE suggests there is a packaging issue.
So, what to do with this 'dummy' ipk? Recipes needing to build against
klibc are inheriting klibc.bbclass which adds dependency on klcc-cross
(which DEPENDS on klibc).


Thanks in advance

Andrea


P.S. Second doubt, somehow unrelated, is the presence of
${base_bindir}/klcc in the klibc recipe. Should this file be removed
in e.g. do_install_append? Is this intended to do builds on target
(not cross?)