From: Saul Wold <sgw@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] iputils: Fix postinst to run on cross rootfs generation
Date: Wed, 22 Aug 2012 20:42:40 -0700 [thread overview]
Message-ID: <5035A6B0.3030007@linux.intel.com> (raw)
In-Reply-To: <1345685506-27178-1-git-send-email-raj.khem@gmail.com>
On 08/22/2012 06:31 PM, Khem Raj wrote:
> rpm shows error messages like /bin/traceroute6 not found
> when building cross rootfs
>
> Yocto # 2894
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/recipes-extended/iputils/iputils_s20101006.bb | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/meta/recipes-extended/iputils/iputils_s20101006.bb b/meta/recipes-extended/iputils/iputils_s20101006.bb
> index 62e2b5e..856bde4 100644
> --- a/meta/recipes-extended/iputils/iputils_s20101006.bb
> +++ b/meta/recipes-extended/iputils/iputils_s20101006.bb
> @@ -59,15 +59,15 @@ ALTERNATIVE_${PN}-ping6 = "ping6"
> ALTERNATIVE_LINK_NAME[ping6] = "${base_bindir}/ping6"
>
> pkg_postinst_${PN}-ping () {
> - chmod 4555 ${base_bindir}/ping
> + chmod 4555 $D${base_bindir}/ping
So that's the magic! I was trying to figure out what the right prefix
was in there. I think we need to do an audit of all pkg_postinst,
because I saw other places where ${xxx} was used or even worse "/etc/..."
Sau!
> }
>
> pkg_postinst_${PN}-ping6 () {
> - chmod 4555 ${base_bindir}/ping6
> + chmod 4555 $D${base_bindir}/ping6
> }
>
> pkg_postinst_${PN}-traceroute6 () {
> - chmod 4555 ${base_bindir}/traceroute6
> + chmod 4555 $D${base_bindir}/traceroute6
> }
>
> PACKAGES += "${PN}-ping ${PN}-ping6 ${PN}-arping ${PN}-tracepath ${PN}-tracepath6 ${PN}-traceroute6"
>
next prev parent reply other threads:[~2012-08-23 3:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 1:31 [PATCH] iputils: Fix postinst to run on cross rootfs generation Khem Raj
2012-08-23 3:42 ` Saul Wold [this message]
2012-08-23 5:24 ` Khem Raj
2012-08-23 9:53 ` 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=5035A6B0.3030007@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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