From: Stanislav Brabec <utx@penguin.cz>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] lsof_4.83.bb: Make recipe buildable again.
Date: Sun, 18 Jul 2010 16:19:06 +0200 [thread overview]
Message-ID: <1279462746.9402.8.camel@utx.lan> (raw)
In-Reply-To: <20100716093325.GA1772@excalibur.local>
Stefan Schmidt wrote:
> Hello.
>
> On Fri, 2010-07-16 at 09:37, Graham Gower wrote:
> > Breakage introduced by 74e32f114272668dfa4c88805741cf55ef965989.
> > Other recipes which call base_do_unpack directly do not share this issue.
> >
> > Signed-off-by: Graham Gower <graham.gower@gmail.com>
>
> Acked-by: Stefan Schmidt <stefan@datenfreihafen.org>
>
> I just run into the same issue and this fixes it for me. Will check this in.
Does not work here. This change fixes it:
diff --git a/recipes/lsof/lsof_4.83.bb b/recipes/lsof/lsof_4.83.bb
index 0a5d557..8982a2c 100644
--- a/recipes/lsof/lsof_4.83.bb
+++ b/recipes/lsof/lsof_4.83.bb
@@ -3,7 +3,7 @@ Its name stands for LiSt Open Files, and it does just that."
SECTION = "devel"
LICENSE = "BSD"
-PR = "r0"
+PR = "r1"
SRC_URI = "ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_${PV}.tar.bz2;name=lsof483tarbz2"
SRC_URI[lsof483tarbz2.md5sum] = "8f731a6251b8c0143d585df0d5ca779e"
@@ -16,7 +16,7 @@ S = "${WORKDIR}/lsof_${PV}_src"
do_unpackpost() {
tar x --no-same-owner -f ${LOCALSRC} -C ${WORKDIR}
}
-addtask do_unpackpost before do_patch after do_unpack
+addtask unpackpost before do_patch after do_unpack
export LSOF_OS = "${TARGET_OS}"
LSOF_OS_linux-uclibc = "linux"
--
________________________________________________________________________
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus
next prev parent reply other threads:[~2010-07-18 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 0:07 [PATCH] lsof_4.83.bb: Make recipe buildable again Graham Gower
2010-07-16 9:33 ` Stefan Schmidt
2010-07-18 14:19 ` Stanislav Brabec [this message]
2010-07-18 17:53 ` Stefan Schmidt
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=1279462746.9402.8.camel@utx.lan \
--to=utx@penguin.cz \
--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.