On 09/12/2017 08:12 AM, Martin Jansa wrote:
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 <[email protected]>
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
hmmm.. will double check what I am doing. In the mean time I can respin
the pull request to exclude the daq fix.
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.
ah, so it is.
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.
I found the change
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/recipes-connectivity/libpcap?id=5eed6c644f715783edb0d05926373e719442dd6a
The question is does adding "native" support qualify to be backported to
a stable branch if it fixes other packages....
thanks,
Armin
Why is this snort change needed in pyro?
To fix the issue noted in the commit message.
- Armin
--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
