From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: python automake dirs (was meta-toolchain-sdk failure)
Date: Wed, 10 Aug 2011 07:44:54 -0700 [thread overview]
Message-ID: <4E429966.3030607@gmail.com> (raw)
In-Reply-To: <822AACC4-810B-4113-A214-EE283679EA06@kernel.crashing.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> So the root of this seems to stem from the following in automake's
> python.m4:
>
> am_cv_python_pythondir=$PYTHON_PREFIX/lib/python$PYTHON_VERSION/site-packages
>
>
am_cv_python_pyexecdir=$PYTHON_EXEC_PREFIX/lib/python$PYTHON_VERSION/site-packages
>
> So the question at hand is how to fix this?
>
> Do we patch automake to respect libdir setting for these?
>
yes seems sane to me
> something like:
>
> --- python.m4.orig 2011-08-09 11:46:19.511163337 -0500 +++ python.m4
> 2011-08-09 11:49:43.623022930 -0500 @@ -88,12 +88,13 @@
> [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 @@ 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 @@ 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 @@ 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 @@ 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 ;;
>
>
>
> - k _______________________________________________ Openembedded-core
> mailing list Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
- --
>
- -Khem
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk5CmWUACgkQuwUzVZGdMxRKIwCeIMURyalficv+nODveSc0q1uE
ldkAnjBjNrI7Un528uulbm4sowLgiclj
=AyDt
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-08-10 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 13:45 meta-toolchain-sdk failure Kumar Gala
2011-08-09 13:58 ` Richard Purdie
2011-08-09 15:32 ` Kumar Gala
2011-08-09 16:50 ` python automake dirs (was meta-toolchain-sdk failure) Kumar Gala
2011-08-10 14:44 ` Khem Raj [this message]
2011-08-10 16:51 ` Kumar Gala
2011-08-10 17:22 ` Richard Purdie
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=4E429966.3030607@gmail.com \
--to=raj.khem@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.