From: Rongqing Li <rongqing.li@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH][meta-networking] bridge-utils: PN -> BPN to fix multilib ALTERNATIVE error
Date: Tue, 25 Feb 2014 10:59:54 +0800 [thread overview]
Message-ID: <530C072A.4090208@windriver.com> (raw)
In-Reply-To: <1393290614-21483-1-git-send-email-rongqing.li@windriver.com>
Please drop this one
-Roy
On 02/25/2014 09:10 AM, rongqing.li@windriver.com wrote:
> From: Roy Li <rongqing.li@windriver.com>
>
> update-alternatives.bbclass does not create the brctl symbolic links for
> multilib, since the wrong use of PN generates
> /usr/sbin/brctl.lib32-bridge-utils, not /usr/sbin/brctl.bridge-utils
>
> Signed-off-by: Roy Li <rongqing.li@windriver.com>
> ---
> recipes-support/bridge-utils/bridge-utils.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-support/bridge-utils/bridge-utils.inc b/recipes-support/bridge-utils/bridge-utils.inc
> index bcdc04a..b4ca3f1 100644
> --- a/recipes-support/bridge-utils/bridge-utils.inc
> +++ b/recipes-support/bridge-utils/bridge-utils.inc
> @@ -20,7 +20,7 @@ ALTERNATIVE_LINK_NAME[brctl] = "${sbindir}/brctl"
> EXTRA_OECONF = "--with-linux-headers=${STAGING_INCDIR}"
>
> do_install_append () {
> - mv ${D}${sbindir}/brctl ${D}${sbindir}/brctl.${PN}
> + mv ${D}${sbindir}/brctl ${D}${sbindir}/brctl.${BPN}
> install -d ${D}/${datadir}/bridge-utils
> install -d ${D}/${sysconfdir}/network/if-pre-up.d
> install -d ${D}/${sysconfdir}/network/if-post-down.d
>
--
Best Reagrds,
Roy | RongQing Li
prev parent reply other threads:[~2014-02-25 2:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 1:10 [PATCH][meta-networking] bridge-utils: PN -> BPN to fix multilib ALTERNATIVE error rongqing.li
2014-02-25 2:59 ` Rongqing Li [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=530C072A.4090208@windriver.com \
--to=rongqing.li@windriver.com \
--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.