linux/poky.git/meta/recipes-devtools/python/python-native, branch 1.2_M4.rc1

python-native: distutils: don't use libdir, remove dead code path

2012-03-13T11:45:13+00:00

* Coming from OE-classic it was surprising that python-native now requires 'libdir' to be exported. Otherwise autoconf would fail to detect python libraries. This happend using a customized environment setup script to use OE's compiler and libs without bitbake. * Use STAGING_LIBDIR instead of libdir. * While at it, remove redundant 'and' statments. (From OE-Core rev: 2edc929c47ac90eabad74e3726912fb3a57aaecd) Signed-off-by: Andreas Oberritter Signed-off-by: Richard Purdie

python, python-native: always set platform to linux2

2012-03-13T11:45:13+00:00

* Fixes many problems with linux2 vs. linux3. At least: - Detected version was from build-host instead of target-host. - linuxaudiodev and ossaudiodev were disabled for linux3. - Files were missing in /usr/lib/python2.7/plat-linux3. * Imported from upstream HG rev c816479f6aaf * Bugtracker URL: http://bugs.python.org/issue12326 (From OE-Core rev: accb2b728ab10cae20be59253a56ac6410b8de10) Signed-off-by: Andreas Oberritter Signed-off-by: Richard Purdie

python-native: correct prefix handling for oe-core sysroot layout

2012-01-05T11:24:47+00:00

Don't try to guess a path based on ${HOST_SYS} since this is not where the files in the sysroot are likely to be. Instead, just use the "plat_specific" approach of taking STAGING_INCDIR and knocking off the trailing "/include" for all cases. This is still evidently suboptimal but does at least seem to give the correct results. (From OE-Core rev: 3b01b884dac0b31af8f5f2ebd60e5939e0111873) Signed-off-by: Phil Blundell Signed-off-by: Richard Purdie

Add Upstream-Status to patches

2012-01-03T12:14:31+00:00

(From OE-Core rev: 169e55d802883df763dbff4a4737e05e96358fa3) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

python-native: Fix gcc compiler detecting logic

2011-11-29T11:22:05+00:00

We have a patch unixccompiler.patch where we try to throw away everything except first element of CC string but this does not work if gcc is prepended with something e.g. CC="ccache gcc" then the logic fails and it ends up in some modules failing on you silently (_sqlite3) in my case. The fix here is to drop basename so we keep the whole string as it is and then the detection function searches for gcc string in the whole CC. This works in both cases one the original intent of the patch and the second described above. One place where it will fail is if someone has non-gcc compiler installed in some subdir which has gcc in it e.g. /usr/gcc/fakecc but for OE this should never happen. Ideally the the detection logic should have tried to execute gcc and then parsed --version output or something. (From OE-Core rev: 9b13b9024d24953dedb35f62d3d8b06a29036992) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

python, python-native: upgrade from 2.6.6 to 2.7.2

2011-10-31T22:03:20+00:00

Rebased these patches to the newer code modified: python-native/nohostlibs.patch modified: python/01-use-proper-tools-for-cross-build.patch modified: python/06-avoid_usr_lib_termcap_path_in_linking.patch modified: python/06-ctypes-libffi-fix-configure.patch modified: python/multilib.patch Deleted these patches are the are now upstream deleted: python/02-remove-test-for-cross.patch deleted: python/security_issue_2254_fix.patch Added this patch to python-native new file: python-native/multilib.patch Updated site config file for python modified: ../../site/common-linux : add ac_cv_have_long_long_format for python avoid this error in python: Include/pyport.h:243:13: error: #error "This platform's pyconfig.h needs to define PY_FORMAT_LONG_LONG" Updated default python version modified: ../../conf/distro/include/default-versions.inc (From OE-Core rev: b284e9a512860b8a8380be80f96cebce6b92ff80) Signed-off-by: Nitin A Kamble Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

python-native: Fix a compiler finding issue

2011-08-08T12:41:19+00:00

The CC variable sometimes add option information after compiler name, but python can't get the real compiler name if those information added. Fix this issue by dropping the option information when finding compiler name. (From OE-Core rev: 461df79fbb655e4c6894d9a9e9ce52656b96303d) Signed-off-by: Mei Lei Signed-off-by: Richard Purdie

python-native: fix for non /usr/lib libdir case

2011-07-12T14:00:47+00:00

the get_python_lib() use hard code "lib". when other recipe building use python-native, the STAGING_LIBDIR is non /usr/lib, so the hard code "lib" will break the build This patch replace the hardcoded "lib" with value from libdir to fix this issue. (From OE-Core rev: ab4ae436126f20b404375c9ae77cf66cfe31ea34) Signed-off-by: Yu Ke Signed-off-by: Richard Purdie

gcc: remove unused patches and move patches in proper dir

2011-05-18T13:32:47+00:00

gcc: update upstream-status for patches python: update upstream-status for patches libtool: update upstream-status of patches m4: update upstream status for patches eglibc: remove unused patches eglibc: update upstream status of patches glibc: update upstream-status of patches & remove unused patches (From OE-Core rev: d10df0e5a363fe8b305ffac7e8ac231da8e07552) Signed-off-by: Nitin A Kamble Signed-off-by: Richard Purdie

python, python-native upgrade from 2.6.5 to 2.6.6

2010-11-15T05:08:26+00:00

Removed these patch: python-native-2.6.5/00-fix-bindir-libdir-for-cross.patch python/00-fix-bindir-libdir-for-cross.patch The upstream code has changed, and it does not need the above 2 patches (fixes) anymore. Patches rebased to the newer code: python/01-use-proper-tools-for-cross-build.patch python/04-default-is-optimized.patch python/06-avoid_usr_lib_termcap_path_in_linking.patch python/99-ignore-optimization-flag.patch Signed-off-by: Nitin A Kamble