> Am 18.11.2018 um 11:36 schrieb Jens Rehsack <[email protected]>:
> 
> That's something I can try to investigate.
> 
>> Am 14.11.2018 um 11:47 schrieb Burton, Ross <[email protected] 
>> <mailto:[email protected]>>:
>> 
>> Getting reports that this breaks cross builds, for example python3-dbus.
>> 
>> tmp-glibc/work/cortexa7hf-neon-vfpv4-oe-linux-gnueabi/python3-dbus/1.2.6-r0/recipe-sysroot-native/usr/lib/libpython3.7m.so
>>  <http://libpython3.7m.so/>: file not recognized: File format not recognized
>> With 3.5.6 the python3-dbus do_configure lokks like 
>> "-L/home/dev/medusa/build/yocto/build/tmp-glibc/work/cortexa7hf-neon-vfpv4-oe-linux-gnueabi/python3-dbus/1.2.6-r0/recipe-sysroot/usr/lib
>>  -lpython3.5m"
>> With the patch 3.7.1 from the ml, it looks like 
>> "L/home/dev/medusa-test/build/yocto/build/tmp-glibc/work/cortexa7hf-neon-vfpv4-oe-linux-gnueabi/python3-dbus/1.2.6-r0/recipe-sysroot-native/usr/lib
>>  -lpython3.7m"
>> 
>> Looks like the cross/sysconfig/etc code regressed and it's picking up the 
>> native sysroot libraries for a cross build.

Indeed.
It's because of 
https://github.com/python/cpython/commit/409482251b06fe75c4ee56e85ffbb4b23d934159
 
<https://github.com/python/cpython/commit/409482251b06fe75c4ee56e85ffbb4b23d934159>
 and work based on that.

In Python 3.5 above patch was applied to target version only, python3-native 
used the old method for getting vars relying on Makefile and config.h parsing.
The Makefile and config.h were chosen based on STAGING_INCDIR and 
STAGING_LIBDIR - but the method in Python 3.7 is using "import 
_sysconfigdata_{abi}_{platform}_{multiarch}" which might need a dedicated 
wrapper to "tune" some include path variables.

I could hack something like 
meta/recipes-devtools/perl/perl/perl-configpm-switch.patch - but maybe someone 
who is better in Python could do that smoother ;)
Please drop me a note ...

Cheers
--
Jens Rehsack - [email protected]

Attachment: signature.asc
Description: Message signed with OpenPGP

-- 
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to