linux/poky.git/meta/recipes-devtools/python/python-native/04-default-is-optimized.patch, branch yocto-2.2.1

python: remove the default optimization

2013-05-10T10:43:12+00:00

We had hard coded python-native and python's default optimization to 1, which made the "assert" statement didn't work, and removed the "-O/-OO" (optimization options), the target python had a "-N" option to disable the default optimization, but the native python didn't. I think that we can set the environment variable PYTHONOPTIMIZE or use "python -O" if we need to optimize, but I'm not sure whether we need to set it by default, it would confuse the user or cause/hide unexpected problems if the "assert" doesn't work. [YOCTO #4427] (From OE-Core rev: 165ed464bbb9bf985dde9d8c15d000809901fff6) Signed-off-by: Robert Yang 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