From 2f7c588c5a8148eec37405186c34bdd1425ea30b Mon Sep 17 00:00:00 2001 From: Robert Yang Date: Wed, 8 May 2013 16:29:48 +0800 Subject: python: remove the default optimization 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 --- meta/recipes-devtools/python/python_2.7.3.bb | 2 -- 1 file changed, 2 deletions(-) (limited to 'meta/recipes-devtools/python/python_2.7.3.bb') diff --git a/meta/recipes-devtools/python/python_2.7.3.bb b/meta/recipes-devtools/python/python_2.7.3.bb index aace95e729..f76f2185fe 100644 --- a/meta/recipes-devtools/python/python_2.7.3.bb +++ b/meta/recipes-devtools/python/python_2.7.3.bb @@ -7,11 +7,9 @@ DISTRO_SRC_URI_linuxstdbase = "" SRC_URI += "\ file://01-use-proper-tools-for-cross-build.patch \ file://03-fix-tkinter-detection.patch \ - file://04-default-is-optimized.patch \ file://05-enable-ctypes-cross-build.patch \ file://06-ctypes-libffi-fix-configure.patch \ file://06-avoid_usr_lib_termcap_path_in_linking.patch \ - file://99-ignore-optimization-flag.patch \ ${DISTRO_SRC_URI} \ file://multilib.patch \ file://cgi_py.patch \ -- cgit v1.2.3-54-g00ecf