From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/4] gdb-cross-canadian: use NATIVESDK paths as it happens to be here
Date: Thu, 23 Feb 2012 10:27:53 +0000 [thread overview]
Message-ID: <1329992873.32110.58.camel@ted> (raw)
In-Reply-To: <b17109ebc9396973f7c0dbf6812699e2c0930349.1329147583.git.Martin.Jansa@gmail.com>
On Mon, 2012-02-13 at 16:40 +0100, Martin Jansa wrote:
> * seems like config/config in -L was also wrong
>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> meta/recipes-devtools/gdb/gdb-cross-canadian.inc | 10 ++++++++--
> 1 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-devtools/gdb/gdb-cross-canadian.inc b/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
> index b5746ce..bac63b7 100644
> --- a/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
> +++ b/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
> @@ -10,12 +10,18 @@ RDEPENDS += "python-nativesdk-core python-nativesdk-lang python-nativesdk-re \
>
> EXTRA_OECONF_append = "--with-python=${WORKDIR}/python"
>
> +NATIVESDK_NAME = "oecore-${SDK_ARCH}-${SDK_ARCH}"
> +NATIVESDK_PATH = "/usr/local/${NATIVESDK_NAME}"
> +NATIVESDK_PATHNATIVE = "${NATIVESDK_PATH}/sysroots/${SDK_SYS}"
> +NATIVESDK_LIBDIR = "${NATIVESDK_PATHNATIVE}${libdir_nativesdk}"
> +NATIVESDK_INCLUDEDIR = "${NATIVESDK_PATHNATIVE}${includedir_nativesdk}"
> +
> do_configure_prepend() {
> cat > ${WORKDIR}/python << EOF
> #! /bin/sh
> case "\$2" in
> - --includes) echo "-I${STAGING_DIR}/${HOST_ARCH}-nativesdk${HOST_VENDOR}-${HOST_OS}${exec_prefix}/include/python${PYTHON_BASEVERSION}/" ;;
> - --ldflags) echo "-L${STAGING_DIR}/${HOST_ARCH}-nativesdk${HOST_VENDOR}-${HOST_OS}${libdir}/python${PYTHON_BASEVERSION}/config/config -lpthread -ldl -lutil -lm -lpython${PYTHON_BASEVERSION}" ;;
> + --includes) echo "-I${STAGING_DIR}/${HOST_ARCH}-nativesdk${HOST_VENDOR}-${HOST_OS}${NATIVESDK_INCLUDEDIR}/python${PYTHON_BASEVERSION}/" ;;
> + --ldflags) echo "-L${STAGING_DIR}/${HOST_ARCH}-nativesdk${HOST_VENDOR}-${HOST_OS}${NATIVESDK_LIBDIR}/python${PYTHON_BASEVERSION}/config -lpthread -ldl -lutil -lm -lpython${PYTHON_BASEVERSION}" ;;
> --exec-prefix) echo "/usr" ;;
> *) exit 1 ;;
> esac
I made some experiments with "bitbake gdb-cross-canadian-x86-64 -e" and
it seems to me that:
--includes) echo "-I${STAGING_INCDIR}/python${PYTHON_BASEVERSION}/" ;;
--ldflags) echo "-L${STAGING_LIBDIR}/../python${PYTHON_BASEVERSION}/config -lpthread -ldl -lutil -lm -lpython${PYTHON_BASEVERSION}" ;;
should work ok here?
Cheers,
Richard
next prev parent reply other threads:[~2012-02-23 10:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 15:40 [PATCH 0/4] PR bumps for missing libz.la, resent gdb python support with fix Martin Jansa
2012-02-13 15:40 ` [PATCH 1/4] gdb-cross-canadian: build gdb with python support Martin Jansa
2012-02-13 15:40 ` [PATCH 2/4] gdb-cross-canadian: use NATIVESDK paths as it happens to be here Martin Jansa
2012-02-13 16:11 ` [PATCH] gdb-cross-canadian: bump PR Martin Jansa
2012-02-17 22:36 ` [PATCH 2/4] gdb-cross-canadian: use NATIVESDK paths as it happens to be here Saul Wold
2012-02-18 11:56 ` Martin Jansa
2012-02-18 14:01 ` Richard Purdie
2012-02-23 8:16 ` Martin Jansa
2012-02-23 10:27 ` Richard Purdie [this message]
2012-02-25 0:05 ` Martin Jansa
2012-02-25 1:02 ` Richard Purdie
2012-02-25 13:12 ` Martin Jansa
2012-02-25 15:42 ` Richard Purdie
2012-02-13 15:40 ` [PATCH 3/4] zlib: remove ldconfig call from install-libs Martin Jansa
2012-02-13 15:40 ` [PATCH 4/4] recipes: bump PR to rebuild .la files without libz.la Martin Jansa
2012-02-21 19:00 ` Steve Sakoman
2012-02-21 19:25 ` Steve Sakoman
2012-02-21 21:07 ` Khem Raj
2012-02-21 21:16 ` Steve Sakoman
2012-02-21 21:33 ` Phil Blundell
2012-02-21 21:39 ` Steve Sakoman
2012-02-21 21:45 ` Phil Blundell
2012-02-21 21:44 ` Paul Eggleton
2012-02-21 22:01 ` Steve Sakoman
2012-02-21 17:07 ` [PATCH 0/4] PR bumps for missing libz.la, resent gdb python support with fix Saul Wold
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=1329992873.32110.58.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox