[OE-core] [PATCH 1/3] distutils-common-base.bbclass: Prepend STAGING_LIBDIR to linker library search path.

[Michael Lippautz]

[usually not answering myself, but:]

The culprit is:
 * distutils.bbclass tries to make python recognize staged libs by
setting STAGING_LIBDIR (correct)
 * distutils recognizes STAGING_LIBDIR and tries to load
python<pyver>/config/Makefile (correct?)
 * since this contains the Makefile that is installed on the target
this brings in -L/usr/lib (obivously not correct)

Without patching the distutils package this leaves us with patching
the Makefile for the target, after packaging it for the target. This
could be done using  SYSROOT_PREPROCESS_FUNCS?

Any comments?

-Michael

2011/4/27 Michael Lippautz <michael.lippautz at gmail.com>:
>> This isn't a libtool problem, we've patched that problem out in oe-core
>> (and I think in OE-dev too now). In this case something is adding
>> "-L/usr/lib" to the compiler arguments and that is the reason things are
>> failing. I'd suggesting finding out where that is coming from and fixing
>> it at source.
>>
> Right.
>
> I also noticed this behaviour and started to look after the cause. It
> seems that distutils somehow grabs the target (python configured)
> Makefile instead of the staging one.
>
> Start of the trouble seems to be [1] where LIBDIR should point into
> staging but is reported to be -L/usr/lib from sysconfig.
>
> Maybe someone with more experience on python staging that can follow up.
>
> Regards,
> Michael
>
> [1] https://bitbucket.org/carljm/python-distutils/src/48c42eeaee44/command/build_ext.py#cl-286
>