From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 1/1] Python: Upgrade from 2.7.3 to 2.7.9:
Date: Wed, 18 Feb 2015 07:41:01 +0000 [thread overview]
Message-ID: <1424245261.25541.18.camel@linuxfoundation.org> (raw)
In-Reply-To: <7c630178dda359245ed1c5e58b191ed927a2e2a0.1424210642.git.alejandro.hernandez@linux.intel.com>
On Tue, 2015-02-17 at 16:22 -0600, Alejandro Hernandez wrote:
> - Based on Paul Eggletons work to partially upgrade to Python 2.7.6
>
> Modified:
> default-versions.inc: switched to python 2.7.9
> generate-manifest-2.7.py: fixed _sysconfigdata
> python-2.7-manifest.inc: fixed _sysconfigdata
> python.inc: Updated checksums and source, no LICENSE
> change just updated some dates
> python-native_2.7.3 -> python-native_2.7.9 and updated patches
> python_2.7.3 -> python_2.7.9, and added ac_cv_file__dev_ptmx=no
> ac_cv_file__dev_ptc=no in EXTRA_OECONF to solve python
> issue #3754, only needed when cross compiling, also updated patches
> use_sysroot_ncurses_instead_of_host.patch: New patch to use ncursesw
> from sysroot instead of hosts, introduced by fix for python issue #15268
>
> Rebased:
> 01-use-proper-tools-for-cross-build.patch
> 03-fix-tkinter-detection.patch
> 05-enable-ctypes-cross-build.patch
> 06-avoid_usr_lib_termcap_path_in_linking.patch
> avoid_warning_about_tkinter.patch
> builddir.patch
> fix_for_using_different_libdir.patch
> host_include_contamination.patch
> multilib.patch
> nohostlibs.patch
> search_db_h_in_inc_dirs_and_avoid_warning.patch
>
> Deleted (fixed on upstream):
> 06-ctypes-libffi-fix-configure.patch
> CVE-2013-4073_py27.patch
> gcc-4.8-fix-configure-Wformat.patch
> json-flaw-fix.patch
> posix_close.patch
> pypirc-secure.patch
> python-2.7.3-CVE-2012-2135.patch
> python-2.7.3-CVE-2013-1752-smtplib-fix.patch
> python-2.7.3-CVE-2014-1912.patch
> python-2.7.3-CVE-2014-7185.patch
> python-2.7.3-berkeley-db-5.3.patch
> python-fix-build-error-with-Readline-6.3.patch
> remove-BOM-insection-code.patch
> remove_sqlite_rpath.patch
> python2.7.3-nossl3.patch
>
> [YOCTO #7059]
The autobuilder highlkighted some issues which look to be from this
patch:
http://errors.yoctoproject.org/Errors/Search/?items=10&query=1894499d6d00badb0e03fb644ac61258b00e061b
Specifically the perf and python-smartpm failures.
Cheers,
Richard
next prev parent reply other threads:[~2015-02-18 7:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 22:22 [PATCH v2 0/1] Python: Upgrade from 2.7.3 to 2.7.9 Alejandro Hernandez
2015-02-17 22:22 ` [PATCH v2 1/1] Python: Upgrade from 2.7.3 to 2.7.9: Alejandro Hernandez
2015-02-18 7:41 ` Richard Purdie [this message]
2015-02-27 13:47 ` [PATCH v2 0/1] Python: Upgrade from 2.7.3 to 2.7.9 Peter Urbanec
2015-02-27 16:07 ` Burton, Ross
2015-03-02 10:29 ` Peter Urbanec
2015-03-02 11:15 ` Burton, Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1424245261.25541.18.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alejandro.hernandez@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox