From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] distutils-common-base.bbclass: Prepend STAGING_LIBDIR to linker library search path.
Date: Thu, 31 Mar 2011 15:26:39 +0100 [thread overview]
Message-ID: <1301581599.24596.106.camel@rex> (raw)
In-Reply-To: <ca0ffb747b87caed609b2edf08f963751dbc8873.1301567822.git.Martin.Jansa@gmail.com>
On Thu, 2011-03-31 at 12:40 +0200, Martin Jansa wrote:
> * This was done generically in bitbake.conf this should be done on
> demand and distutils based recipes seem to need it. So we define it
> here.
> * imported from OE 629ae87eadeec1068c3778e14488b549029adffb
>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> meta/classes/distutils-common-base.bbclass | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/meta/classes/distutils-common-base.bbclass b/meta/classes/distutils-common-base.bbclass
> index f66a5cd..b6caf24 100644
> --- a/meta/classes/distutils-common-base.bbclass
> +++ b/meta/classes/distutils-common-base.bbclass
> @@ -4,6 +4,8 @@ EXTRA_OEMAKE = ""
>
> export STAGING_INCDIR
> export STAGING_LIBDIR
> +# libtool 2.4 does not export with LDFLAGS but distutils need it
> +LDFLAGS_prepend = "-L${STAGING_LIBDIR} "
This should not be needed, the linker itself should automatically look
in that path at link time. What problem are you seeing?
Cheers,
Richard
next prev parent reply other threads:[~2011-03-31 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 10:40 [PATCH 0/3] SRCREVs and fixed building python modules Martin Jansa
2011-03-31 10:40 ` [PATCH 1/3] distutils-common-base.bbclass: Prepend STAGING_LIBDIR to linker library search path Martin Jansa
2011-03-31 14:26 ` Richard Purdie [this message]
[not found] ` <20110404183138.GA30816@jama.jama.net>
2011-04-18 5:54 ` Martin Jansa
2011-04-18 6:57 ` Richard Purdie
2011-04-22 17:48 ` Khem Raj
2011-04-27 7:43 ` Michael Lippautz
2011-04-27 8:47 ` Michael Lippautz
2011-03-31 10:40 ` [PATCH 2/3] gconf-dbus: add SRCREV to recipe Martin Jansa
2011-03-31 10:40 ` [PATCH 3/3] xf86-video-omapfb: " Martin Jansa
2011-03-31 10:47 ` Koen Kooi
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=1301581599.24596.106.camel@rex \
--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.