From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] automake: Update for python.m4 to respect libdir
Date: Fri, 12 Aug 2011 10:51:31 -0700 [thread overview]
Message-ID: <4E456823.1090004@linux.intel.com> (raw)
In-Reply-To: <1313043994-28945-1-git-send-email-galak@kernel.crashing.org>
On 08/10/2011 11:26 PM, Kumar Gala wrote:
> As we tweak libdir we need python libs that utilize configure to respect
> it setting. By updating the python.m4 template, when we regen automake
> files they will than respect the setting of libdir which is standard for
> any autotools based recipe.
>
> Signed-off-by: Kumar Gala<galak@kernel.crashing.org>
> ---
> meta/recipes-devtools/automake/automake.inc | 2 +-
> .../automake/automake/python-libdir.patch | 60 ++++++++++++++++++++
> meta/recipes-devtools/automake/automake_1.11.1.bb | 3 +-
> 3 files changed, 63 insertions(+), 2 deletions(-)
> create mode 100644 meta/recipes-devtools/automake/automake/python-libdir.patch
>
> diff --git a/meta/recipes-devtools/automake/automake.inc b/meta/recipes-devtools/automake/automake.inc
> index 96d797f..f217e14 100644
> --- a/meta/recipes-devtools/automake/automake.inc
> +++ b/meta/recipes-devtools/automake/automake.inc
> @@ -4,7 +4,7 @@ Standards. Automake requires the use of Autoconf."
> LICENSE = "GPLv2"
> HOMEPAGE = "http://www.gnu.org/software/automake/"
> SECTION = "devel"
> -PR = "r3"
> +PR = "r4"
>
> SRC_URI = "${GNU_MIRROR}/automake/automake-${PV}.tar.bz2 "
>
> diff --git a/meta/recipes-devtools/automake/automake/python-libdir.patch b/meta/recipes-devtools/automake/automake/python-libdir.patch
> new file mode 100644
> index 0000000..63dafca
> --- /dev/null
> +++ b/meta/recipes-devtools/automake/automake/python-libdir.patch
> @@ -0,0 +1,60 @@
> +Upstream-Status: Inappropriate [embedded specific]
> +
> +Signed-off-by: Kumar Gala<galak@kernel.crashing.org>
> +
> +Index: automake-1.11.1/m4/python.m4
> +===================================================================
> +--- automake-1.11.1.orig/m4/python.m4
> ++++ automake-1.11.1/m4/python.m4
> +@@ -88,12 +88,13 @@ python2.1 python2.0])
> + [am_cv_python_version=`$PYTHON -c "import sys; sys.stdout.write(sys.version[[:3]])"`])
> + AC_SUBST([PYTHON_VERSION], [$am_cv_python_version])
> +
> +- dnl Use the values of $prefix and $exec_prefix for the corresponding
> +- dnl values of PYTHON_PREFIX and PYTHON_EXEC_PREFIX. These are made
> ++ dnl Use the values of $prefix, $libdir and $exec_prefix for the corresponding
> ++ dnl values of PYTHON_PREFIX PYTHON_LIB_PREFIX, and PYTHON_EXEC_PREFIX. These are made
> + dnl distinct variables so they can be overridden if need be. However,
> + dnl general consensus is that you shouldn't need this ability.
> +
> + AC_SUBST([PYTHON_PREFIX], ['${prefix}'])
> ++ AC_SUBST([PYTHON_LIB_PREFIX], ['${libdir}'])
> + AC_SUBST([PYTHON_EXEC_PREFIX], ['${exec_prefix}'])
> +
> + dnl At times (like when building shared libraries) you may want
> +@@ -122,7 +123,7 @@ python2.1 python2.0])
> + am_py_prefix=$prefix
> + fi
> + am_cv_python_pythondir=`$PYTHON -c "import sys; from distutils import sysconfig; sys.stdout.write(sysconfig.get_python_lib(0,0,prefix='$am_py_prefix'))" 2>/dev/null ||
> +- echo "$PYTHON_PREFIX/lib/python$PYTHON_VERSION/site-packages"`
> ++ echo "$PYTHON_LIB_PREFIX/python$PYTHON_VERSION/site-packages"`
> + case $am_cv_python_pythondir in
> + $am_py_prefix*)
> + am__strip_prefix=`echo "$am_py_prefix" | sed 's|.|.|g'`
> +@@ -132,7 +133,7 @@ python2.1 python2.0])
> + case $am_py_prefix in
> + /usr|/System*) ;;
> + *)
> +- am_cv_python_pythondir=$PYTHON_PREFIX/lib/python$PYTHON_VERSION/site-packages
> ++ am_cv_python_pythondir=$PYTHON_LIB_PREFIX/python$PYTHON_VERSION/site-packages
> + ;;
> + esac
> + ;;
> +@@ -160,7 +161,7 @@ python2.1 python2.0])
> + am_py_exec_prefix=$exec_prefix
> + fi
> + am_cv_python_pyexecdir=`$PYTHON -c "import sys; from distutils import sysconfig; sys.stdout.write(sysconfig.get_python_lib(1,0,prefix='$am_py_exec_prefix'))" 2>/dev/null ||
> +- echo "$PYTHON_EXEC_PREFIX/lib/python$PYTHON_VERSION/site-packages"`
> ++ echo "$PYTHON_LIB_PREFIX/python$PYTHON_VERSION/site-packages"`
> + case $am_cv_python_pyexecdir in
> + $am_py_exec_prefix*)
> + am__strip_prefix=`echo "$am_py_exec_prefix" | sed 's|.|.|g'`
> +@@ -170,7 +171,7 @@ python2.1 python2.0])
> + case $am_py_exec_prefix in
> + /usr|/System*) ;;
> + *)
> +- am_cv_python_pyexecdir=$PYTHON_EXEC_PREFIX/lib/python$PYTHON_VERSION/site-packages
> ++ am_cv_python_pyexecdir=$PYTHON_LIB_PREFIX/python$PYTHON_VERSION/site-packages
> + ;;
> + esac
> + ;;
> diff --git a/meta/recipes-devtools/automake/automake_1.11.1.bb b/meta/recipes-devtools/automake/automake_1.11.1.bb
> index c66155f..fee9597 100644
> --- a/meta/recipes-devtools/automake/automake_1.11.1.bb
> +++ b/meta/recipes-devtools/automake/automake_1.11.1.bb
> @@ -33,7 +33,8 @@ PATHFIXPATCH = "file://path_prog_fixes.patch;patch=1"
> PATHFIXPATCH_virtclass-native = ""
>
> SRC_URI += "${PATHFIXPATCH} \
> - file://prefer-cpio-over-pax-for-ustar-archives.patch"
> + file://prefer-cpio-over-pax-for-ustar-archives.patch \
> + file://python-libdir.patch"
>
> SRC_URI[md5sum] = "c2972c4d9b3e29c03d5f2af86249876f"
> SRC_URI[sha256sum] = "5b159d3c0e0a1f87de71b68bcb9f1a1c49e9e71749c9b723f17e2e1e0295c7ae"
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2011-08-12 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 6:26 [PATCH 1/2] automake: Update for python.m4 to respect libdir Kumar Gala
2011-08-11 6:26 ` [PATCH 2/2] xcb-proto: update based on changes to python.m4 in automake Kumar Gala
2011-08-12 17:51 ` Saul Wold [this message]
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=4E456823.1090004@linux.intel.com \
--to=sgw@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