From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <koen@openembedded.org>
Subject: Re: [STABLE][PATCH] gdbm: use LDFLAGS (fixes QA error)
Date: Tue, 14 Apr 2009 17:42:43 -0400 [thread overview]
Message-ID: <20090414214243.GF28306@denix.org> (raw)
In-Reply-To: <1239694534-23578-1-git-send-email-k.kooi@student.utwente.nl>
On Tue, Apr 14, 2009 at 09:35:34AM +0200, Koen Kooi wrote:
> From: Koen Kooi <koen@openembedded.org>
Is it a proper use of TARGET_CC_ARCH? As name suggests, it wasn't meant to
deliver LDFLAGS to CC, only to specify the architecture. But as I can see,
many recipes reuse this variable to stick additional flags for CC... So, I
guess it's a common practice.
Acked-by: Denys Dmytriyenko <denis@denix.org>
> Signed-off-by: Koen Kooi <koen@openembedded.org>
> ---
> recipes/gdbm/gdbm_1.8.3.bb | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/recipes/gdbm/gdbm_1.8.3.bb b/recipes/gdbm/gdbm_1.8.3.bb
> index f3beb47..883022e 100644
> --- a/recipes/gdbm/gdbm_1.8.3.bb
> +++ b/recipes/gdbm/gdbm_1.8.3.bb
> @@ -4,7 +4,7 @@ SECTION = "libs"
> PRIORITY = "optional"
> LICENSE = "GPL"
>
> -PR = "r2"
> +PR = "r3"
>
> SRC_URI = "${GNU_MIRROR}/gdbm/gdbm-${PV}.tar.gz \
> file://makefile.patch;patch=1 \
> @@ -12,6 +12,8 @@ SRC_URI = "${GNU_MIRROR}/gdbm/gdbm-${PV}.tar.gz \
>
> inherit autotools
>
> +TARGET_CC_ARCH += "${LDFLAGS}"
> +
> do_stage () {
> oe_libinstall -so -a libgdbm ${STAGING_LIBDIR}
> install -m 0644 ${S}/gdbm.h ${STAGING_INCDIR}/
> --
> 1.5.6.5
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2009-04-14 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 7:35 [STABLE][PATCH] gdbm: use LDFLAGS (fixes QA error) Koen Kooi
2009-04-14 21:42 ` Denys Dmytriyenko [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=20090414214243.GF28306@denix.org \
--to=denis@denix.org \
--cc=koen@openembedded.org \
--cc=openembedded-devel@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.