From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] python: fix sqlite RPATH issue
Date: Thu, 29 Sep 2011 15:23:06 +0100 [thread overview]
Message-ID: <1317306193.12332.88.camel@ted> (raw)
In-Reply-To: <8dd692d309ecfbd969a6e01969e03d203f670dbe.1317254761.git.sgw@linux.intel.com>
On Wed, 2011-09-28 at 17:07 -0700, Saul Wold wrote:
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
> .../python/python/remove_sqlite_rpath.patch | 12 ++++++++++++
> meta/recipes-devtools/python/python_2.6.6.bb | 3 ++-
> 2 files changed, 14 insertions(+), 1 deletions(-)
> create mode 100644 meta/recipes-devtools/python/python/remove_sqlite_rpath.patch
>
> diff --git a/meta/recipes-devtools/python/python/remove_sqlite_rpath.patch b/meta/recipes-devtools/python/python/remove_sqlite_rpath.patch
> new file mode 100644
> index 0000000..350151e
> --- /dev/null
> +++ b/meta/recipes-devtools/python/python/remove_sqlite_rpath.patch
> @@ -0,0 +1,12 @@
> +Index: Python-2.6.6/setup.py
> +===================================================================
> +--- Python-2.6.6.orig/setup.py 2011-09-28 14:22:57.000000000 -0700
> ++++ Python-2.6.6/setup.py 2011-09-28 16:11:25.147279633 -0700
> +@@ -1079,7 +1079,6 @@
> + include_dirs=["Modules/_sqlite",
> + sqlite_incdir],
> + library_dirs=sqlite_libdir,
> +- runtime_library_dirs=sqlite_libdir,
> + extra_link_args=sqlite_extra_link_args,
> + libraries=["sqlite3",]))
> + else:
Looks reasonable to me but no patch header? ;-)
Cheers,
Richard
prev parent reply other threads:[~2011-09-29 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 0:07 [PATCH 0/3] Python RPATH Fix and some updates Saul Wold
2011-09-29 0:07 ` [PATCH 1/3] glew: update to 1.7.0 Saul Wold
2011-09-29 0:07 ` [PATCH 2/3] sysstat: update to 10.0.2 Saul Wold
2011-09-29 0:07 ` [PATCH 3/3] python: fix sqlite RPATH issue Saul Wold
2011-09-29 14:23 ` Richard Purdie [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=1317306193.12332.88.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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.