For various reasons I sometimes like to run Bro out of the directory
I used to build it, rather than installing it. With a fresh git pull,
when doing this I get:
% build/src/bro
internal error: can't load magic file /usr/local/bro/share/bro/magic:
could not find any valid magic f
I don't think that is intended behavior, but rather an unintended consequence
of some of the work on the file analysis framework and shipping with our own
magic DB. Perhaps Jon can elaborate more on what it would take to fix this?
On Jul 29, 2013, at 10:09 PM, "Vern Paxson" wrote:
> For variou
> Try "source build/bro-path-dev.sh".
Cool, that does it. The only problem is surely I'm going to fail to
remember that bit of voodoo, and bug you with similar questions in the
future at least three more times :-P.
Vern
___
bro-dev mail
On Mon, Jul 29, 2013 at 20:08 -0700, you wrote:
> I'm wondering whether filing the ticket is a lost cause (i.e., the
> current philosophy is it's okay if things only work post "make
> install") ... ?
Quite the opposite: I'm sure most of us run it right out of the source
tree more often than not
