From: Martin Jansa <martin.jansa@gmail.com>
To: Yao Xinpan <yaoxp@cn.fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] lvm2.inc: EXTRA_OECONF is been overwrited
Date: Fri, 6 Jun 2014 11:17:00 +0200 [thread overview]
Message-ID: <20140606091700.GW2426@jama> (raw)
In-Reply-To: <1402025177-7694-1-git-send-email-yaoxp@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
On Thu, Jun 05, 2014 at 11:26:17PM -0400, Yao Xinpan wrote:
> EXTRA_OECONF has been assigned before ‘EXTRA_OECONF = "--with-usrlibdir=${libdir}"’.
>
> So, ‘EXTRA_OECONF = "--with-usrlibdir=${libdir}"’ should be changed to
> ‘EXTRA_OECONF += "--with-usrlibdir=${libdir}"’.
>
> Signed-off-by: Yao Xinpan <yaoxp@cn.fujitsu.com>
> ---
> meta-oe/recipes-support/lvm2/lvm2.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-oe/recipes-support/lvm2/lvm2.inc b/meta-oe/recipes-support/lvm2/lvm2.inc
> index c6a9ec0..71f782a 100644
> --- a/meta-oe/recipes-support/lvm2/lvm2.inc
> +++ b/meta-oe/recipes-support/lvm2/lvm2.inc
> @@ -47,4 +47,4 @@ FILES_${PN} += "${libdir}/device-mapper/*.so ${base_libdir}/udev"
> FILES_${PN}-dbg += "${libdir}/device-mapper/.debug"
>
> RDEPENDS_${PN} = "bash"
> -EXTRA_OECONF = "--with-usrlibdir=${libdir}"
> +EXTRA_OECONF += "--with-usrlibdir=${libdir}"
Please send it to openembedded-devel@lists.openembedded.org with right
subject tag (see README file)
> --
> 1.8.4.2
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-06-06 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 3:26 [PATCH] lvm2.inc: EXTRA_OECONF is been overwrited Yao Xinpan
2014-06-06 9:17 ` Martin Jansa [this message]
2014-06-06 9:27 ` 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=20140606091700.GW2426@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yaoxp@cn.fujitsu.com \
/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