From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] daq: update to 2.0.2
Date: Fri, 28 Mar 2014 12:14:55 +0100 [thread overview]
Message-ID: <20140328111455.GA3714@jama> (raw)
In-Reply-To: <607b033dd0ee43e6963425d897b1f5b1@BY2PR03MB254.namprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2687 bytes --]
On Fri, Mar 28, 2014 at 10:18:09AM +0000, B40290@freescale.com wrote:
> Hello,
> I can not reproduce the issue.
Have you tried to build it with minimal deps (empty sysroot)?
> Can you give me your host environments?
It's described here:
http://www.openembedded.org/wiki/Bitbake_World_Status
> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Martin Jansa
> Sent: Friday, March 28, 2014 6:10 PM
> To: openembedded-devel@lists.openembedded.org
> Subject: Re: [oe] [meta-oe][PATCH] daq: update to 2.0.2
>
> On Fri, Mar 28, 2014 at 02:03:05PM +0800, b40290@freescale.com wrote:
> > From: Chunrong Guo <B40290@freescale.com>
> >
> > Signed-off-by: Chunrong Guo <B40290@freescale.com>
>
> There is patch like this already, but it still doesn't fix the build issue.
>
> > ---
> > meta-oe/recipes-connectivity/daq/{daq_2.0.1.bb => daq_2.0.2.bb} | 4
> > ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-) rename
> > meta-oe/recipes-connectivity/daq/{daq_2.0.1.bb => daq_2.0.2.bb} (73%)
> >
> > diff --git a/meta-oe/recipes-connectivity/daq/daq_2.0.1.bb
> > b/meta-oe/recipes-connectivity/daq/daq_2.0.2.bb
> > similarity index 73%
> > rename from meta-oe/recipes-connectivity/daq/daq_2.0.1.bb
> > rename to meta-oe/recipes-connectivity/daq/daq_2.0.2.bb
> > index c12ccde..2675e2a 100644
> > --- a/meta-oe/recipes-connectivity/daq/daq_2.0.1.bb
> > +++ b/meta-oe/recipes-connectivity/daq/daq_2.0.2.bb
> > @@ -10,7 +10,7 @@ DEPENDS = "libpcap libpcre "
> > SRC_URI = "http://fossies.org/linux/misc/daq-${PV}.tar.gz \
> > file://disable-run-test-program-while-cross-compiling.patch "
> >
> > -SRC_URI[md5sum] = "044aa3663d44580d005293eeb8ccf175"
> > -SRC_URI[sha256sum] = "ebba87c2ec76ac65d2980934423b0597909caead3a86ce5d1ba1ea6ce518ec6d"
> > +SRC_URI[md5sum] = "865bf9b750a2a2ca632591a3c70b0ea0"
> > +SRC_URI[sha256sum] = "d65d1e67c4994e02c3142c49a648642e780b7e3d942b4a51f605309beac269a8"
> >
> > inherit autotools
> > --
> > 1.8.3.2
> >
> >
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
> --
> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2014-03-28 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 6:03 [meta-oe][PATCH] daq: update to 2.0.2 b40290
2014-03-28 10:09 ` Martin Jansa
2014-03-28 10:18 ` B40290
2014-03-28 11:14 ` Martin Jansa [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=20140328111455.GA3714@jama \
--to=martin.jansa@gmail.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.