All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: akuster808 <akuster808@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 000/126] Pyro-next pull request
Date: Tue, 12 Sep 2017 17:12:45 +0200	[thread overview]
Message-ID: <20170912151245.GC4102@jama> (raw)
In-Reply-To: <92fd35f1-193c-bd01-6266-3d85a6237f77@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3012 bytes --]

On Tue, Sep 12, 2017 at 07:55:14AM -0700, akuster808 wrote:
> 
> 
> On 09/11/2017 03:07 PM, Martin Jansa wrote:
> > On Mon, Sep 11, 2017 at 08:21:02AM -0700, Armin Kuster wrote:
> >> Please concider these changes for pyro
> >>
> >> The following changes since commit 5e82995148a2844c6f483ae5ddd1438d87ea9fb7:
> >>
> >>    opencv: disable broken Intel FP16 detection (2017-05-09 16:00:31 +0200)
> >>
> >> are available in the git repository at:
> >>
> >>    git://git.openembedded.org/meta-openembedded-contrib akuster/pyro-next
> >>    http://cgit.openembedded.org/meta-openembedded-contrib/log/?h=akuster/pyro-next
> >>
> >> Kai Kang (3):
> >>    snort: enable static daq
> > This one adds daq-native which depends on libpcap-native, but without
> > this commit in oe-core/pyro:
> > commit 12373003cc3753421321d558813b1de95667c192
> > Author: Kai Kang <kai.kang@windriver.com>
> > Date:   Wed May 24 17:33:58 2017 +0800
> >
> >      libpcap: add native package
> >
> >      Add package libpcap-native required by recipe daq-native in layer
> >      meta-networking. And daq-native is added to fix snort start error.
> >
> > it fails with:
> > ERROR: Nothing PROVIDES 'libpcap-native' (but virtual:native:meta-oe/meta-networking/recipes-connectivity/daq/daq_2.0.6.bb DEPENDS on or otherwise requires it). Close matches:
> I never saw this message during any of my  builds. That commit has been 
> sitting my queue for over a month. How are you building this? Maybe I 
> need to tweak my env.

Building world should probably show it as well, I was seeing it from
openembedded-core/scripts/sstate-diff-machines.sh
script which is calling
bitbake -S none world

> > Is there oe-core/pyro pull request with libpcap-native?
> nope. that support has been in before pyro released and came in as part 
> of the 2.25 update. I do build with what gets queued in oe-core/pyro.
> 
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/recipes-support/libcap/libcap_2.25.bb?h=pyro&id=e5043dbbccd05e27d0a020215c38de2be4829187

This is libcap not libpcap.

OE @ ~/openembedded-core $ git checkout origin/pyro
...
OE @ ~/openembedded-core $ grep native -R ./meta/recipes-connectivity/libpcap
./meta/recipes-connectivity/libpcap/libpcap.inc:DEPENDS = "flex-native bison-native"

OE @ ~/openembedded-core $ git checkout origin/master
Previous HEAD position was 7b3584ace9... Revert "expat: Don't use getrandom() in the -native case"
HEAD is now at 2ebbeb6111... staging: gracefully abort if two recipes conflict in the sysroot
OE @ ~/openembedded-core $ grep native -R ./meta/recipes-connectivity/libpcap
./meta/recipes-connectivity/libpcap/libpcap.inc:DEPENDS = "flex-native bison-native"
./meta/recipes-connectivity/libpcap/libpcap.inc:BBCLASSEXTEND = "native"

So it still isn't in pyro.

> > Why is this snort change needed in pyro?
> To fix the issue noted in the commit message.
> - Armin

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

  reply	other threads:[~2017-09-12 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11 15:21 [PATCH 000/126] Pyro-next pull request Armin Kuster
2017-09-11 22:07 ` Martin Jansa
2017-09-12 14:55   ` akuster808
2017-09-12 15:12     ` Martin Jansa [this message]
2017-09-12 15:26       ` akuster808

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=20170912151245.GC4102@jama \
    --to=martin.jansa@gmail.com \
    --cc=akuster808@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.