[Zeek-Dev] Zeek and the myricom package plugin

[Michael Dopheide]

Yeah, I think my problem was just overlap, but I feel we should keep a list
of these kinds of things to look out for in the transition.  For instance,
remembering to remove cron jobs that run as the 'bro' user when that user
no longer exists.  We've also got systems where /usr/local/bro/logs is a
separate filesystem.

-Dop



On Fri, Jul 19, 2019 at 11:07 PM Michał Purzyński <
michalpurzynski1 at gmail.com> wrote:

> I tested it today and was able to build the myricom plugin without any
> problems.
>
> It was a clean system, with the fresh copy of Zeek master and a clone of
> the plugin from Seth repo.
>
> That was without using zkg mind you.
>
>
> > On Jul 19, 2019, at 7:59 PM, Jon Siwek <jsiwek at corelight.com> wrote:
> >
> >> On Fri, Jul 19, 2019 at 1:52 PM Michael Dopheide <dopheide at es.net>
> wrote:
> >>
> >> 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".
> >
> > * The thing which produces the .bif.bro versus .bif.zeek file is
> > `bifcl`.  Seems like you've got the new version since it made a
> > .bif.zeek
> >
> > * The thing which generates a Makefile that expects to copy .bif.bro
> > versus .bif.zeek is cmake/BifCl.cmake.  Seems you may have an old
> > version of this since it created a Makefile that still expects a
> > .bif.bro
> >
> > I didn't test building the myricom plugin, but a simple plugin
> > containing a .bif doesn't seem to generally have this problem when
> > using a fully updated zeek/master: it produced and installed a
> > .bif.zeek file.
> >
> > Maybe verify you've got a fully updated and consistent Zeek build
> > and/or give the full command and build log you're running.  The
> > configuration output from the build log could have a hint that it's
> > picking up an unexpected Bro/Zeek build or install path.
> >
> > If installing via zkg, an outdated "zeek_dist" in ~/.zkg/config is a
> > problem if it's still using a version of the myricom package that uses
> > it, else if there's an old version of "bro-config" (now "zeek-config")
> > in PATH, that could be a problem.
> >
> > - Jon
> > _______________________________________________
> > zeek-dev mailing list
> > zeek-dev at zeek.org
> > http://mailman.icsi.berkeley.edu/mailman/listinfo/zeek-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.icsi.berkeley.edu/pipermail/zeek-dev/attachments/20190720/54353267/attachment.html