[Zeek-Dev] Zeek and the myricom package plugin

[Michael Dopheide]

More testing revealed another gotcha against master...

CMake is expecting to be able to copy myricom.bif.bro to it's destination,
but only myricom.bif.zeek exists.

make
...
[ 11%] [BIFCL] Processing src/myricom.bif
Error copying file "myricom.bif.bro" to
"/home/zeek/.zkg/testing/zeek-myricom/clones/zeek-myricom/build/lib/bif/myricom.bif.bro".

Not sure if that's just a problem on my end or more fundamental to the name
change with plugins.

-Dop

On Tue, Jul 16, 2019 at 3:12 PM Jon Siwek <jsiwek at corelight.com> wrote:

> On Tue, Jul 16, 2019 at 10:55 AM Seth Hall <seth at corelight.com> wrote:
>
> > Are there suggestions about how I should merge this branch into master
> > and not break people installing this on current releases?
>
> Best would be to actually test against 2.6 and master to see if anything
> breaks.
>
> At a minimum, actually I see these probably need to change to be
> compatible:
>
> * get-bro-env: if "zeek-path-dev" doesn't exist fallback to "bro-path-dev"
>
> * broctl/myricom.py: may need a try block to see if the ZeekControl
> stuff exists, else still use BroControl
>
> - Jon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.icsi.berkeley.edu/pipermail/zeek-dev/attachments/20190719/e7872963/attachment.html