[Bro] Bro and OpenBSD 4.0 issues
christian at whoop.org
Wed Dec 6 12:53:46 PST 2006
On Wed, 2006-12-06 at 09:09 -0500, Jean-Philippe Luiggi wrote:
> > /usr/include/netinet/if_ether.h:140: error: field `ea_hdr' has incomplete type
> > /usr/include/netinet/if_ether.h:158: error: field `ac_if' has incomplete type
> > /usr/include/netinet/if_ether.h:161: error: syntax error before "LIST_HEAD"
> > /usr/include/netinet/if_ether.h:166: error: syntax error before "LIST_ENTRY"
> > /usr/include/netinet/if_ether.h:222: error: syntax error before "LIST_ENTRY"
> I didn't get these problems with Current's release, so i built a "simple"
> GENERIC installation in order being in the same setup as Tim.
this is only in config.log, did you check there? What does your
configure check for netinet/if_ether report?
> > - ns_msg is (correctly, I believe) not found, and thus nonblocking DNS
> > is disabled. As far as we're concerned, our configuration checks work
> > fine here and we simply can't support nonblocking DNS on OpenBSD at the
> > moment. Patches are very welcome.
> Same things, no problem with nonblocking DNS for me.
> I know about a workaround (using the extra libbind given from a package) and
> using a "configure --with-dns-lib" and "configure
> --with-dns-include" in order to give the ability to OpenBSD to use them.
So can you tell us which header files define ns_msg in your setup? We
currently rely on that definition being in arpa/nameser.h.
If your libbind installation reliably solves the problem, we might make
this a FAQ and possibly add output to the configure script that tells
OpenBSD people what they need to do.
> > Regarding your build errors, it seems from the output you have posted in
> > your follow-up email that you also have encountered the parse.cc
> > problem, since the build stops there. See my mail from yesterday for
> > possible workarounds.
> And again i didn't notice this.
Did your configure run pick up bison or yacc?
(Actually, as usual it'd be helpful if you could post the shell output
you get when running configure, as well as the resulting config.log.)
More information about the Bro