From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH] V4 wireshark: fix build depends
Date: Wed, 6 Aug 2014 09:08:58 -0400 [thread overview]
Message-ID: <20140806130856.GA14621@mentor.com> (raw)
In-Reply-To: <20140806091035.GE14848@jama>
[-- Attachment #1: Type: text/plain, Size: 2565 bytes --]
[Re: [oe] [meta-networking][PATCH] V4 wireshark: fix build depends] On 14.08.06 (Wed 11:10) Martin Jansa wrote:
> On Wed, Aug 06, 2014 at 03:41:30PM +0800, Rongqing Li wrote:
> >
> >
> > On 07/26/2014 03:33 AM, Armin Kuster wrote:
> > > This should address issues found in test-dependencies 2014-07-25
> > >
> > > wireshark/wireshark/latest lost dependency on libcap libnl libnl-genl libnl-nf libnl-route portaudio-v19 sbc
> > >
> > > Signed-off-by: Armin Kuster <akuster@mvista.com>
> > > ---
> > > meta-networking/recipes-support/wireshark/wireshark_1.12.0-rc2.bb | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/meta-networking/recipes-support/wireshark/wireshark_1.12.0-rc2.bb b/meta-networking/recipes-support/wireshark/wireshark_1.12.0-rc2.bb
> > > index 5d6df40..b965fdf 100644
> > > --- a/meta-networking/recipes-support/wireshark/wireshark_1.12.0-rc2.bb
> > > +++ b/meta-networking/recipes-support/wireshark/wireshark_1.12.0-rc2.bb
> > > @@ -3,7 +3,7 @@ HOMEPAGE = "http://www.wireshark.org"
> > > SECTION = "network"
> > > LICENSE = "GPL-2.0"
> > >
> > > -DEPENDS = "perl-native libpcap pcre expat glib-2.0 libsmi"
> > > +DEPENDS = "perl-native libcap libpcap pcre expat glib-2.0 libsmi libnl portaudio-v19 sbc"
> > >
> > > inherit autotools pkgconfig
> > >
> >
> > 1. I can not download wireshark-1.12.0-rc2.tar.bz2, seems it has been
> > removed
> >
> > wget
> > http://wiresharkdownloads.riverbed.com/wireshark/src/wireshark-1.12.0-rc2.tar.bz2
> > --2014-08-06 15:00:13--
> > http://wiresharkdownloads.riverbed.com/wireshark/src/wireshark-1.12.0-rc2.tar.bz2
> > Resolving wiresharkdownloads.riverbed.com
> > (wiresharkdownloads.riverbed.com)... 69.4.231.52
> > Connecting to wiresharkdownloads.riverbed.com
> > (wiresharkdownloads.riverbed.com)|69.4.231.52|:80... connected.
> > HTTP request sent, awaiting response... 404 Not Found
> > 2014-08-06 15:00:14 ERROR 404: Not Found.
>
> rc3 and final 1.12.0 were released already, someone willing to send a
> patch?
Sure, I'll send it out now.
-J.
>
> > 2. which layers do I found the libsmi/portaudio recipes?
> >
> >
> > --
> > Best Reagrds,
> > Roy | RongQing Li
> > --
> > _______________________________________________
> > 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
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 501 bytes --]
next prev parent reply other threads:[~2014-08-06 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 19:33 [meta-networking][PATCH] V4 wireshark: fix build depends Armin Kuster
2014-07-30 7:26 ` Martin Jansa
2014-08-06 7:41 ` Rongqing Li
2014-08-06 9:10 ` Martin Jansa
2014-08-06 13:08 ` Joe MacDonald [this message]
[not found] ` <20140806081740.GA14848@jama>
2014-08-06 9:29 ` Rongqing Li
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=20140806130856.GA14621@mentor.com \
--to=joe_macdonald@mentor.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.