Thanks!
Using protocols "all" works fine, and I have the same behavior using
protocols "bgp pipe rpki" for bird203, but works on bird202, using the
same environment. Tested on debian 9/ubuntu 18.
[]s
On 01-03-19 13:19, Ondrej Zajicek wrote:
On Fri, Mar 01, 2019 at 12:46:52PM +0100, Piotr Wydrych wrote:
Hi,
On 01.03.2019 09:51, Tiago Felipe Goncalves wrote:
I'm trying to compile bird204 for test purpose, but I'm facing some
errors, anyone have an idea?
First of all, I compiled 2.0.4 with protocols "all" (which equals to "bfd
babel bgp mrt ospf perf pipe radv rip static" on my host) today and it's
working fine in my lab.
Second, I found a correlation that those warnings appear when you exclude
some protocols from the list. E.g., if you exclude static. Different set of
protocols results in different set of warnings :-)
Hi
Yes, these warnings are just complains about parts of grammar that
are not used, because they are defined in core bird, but used by
few protocols, which are all disabled in your setup. These should
be generally harmless.
Then, I found also that if you reduce protocol list too much, bison seems to
enter an infinite loop or is getting crazy by whatever other reason:
Seemsl like we hit some bug in bison, as having useless rules should be ok.
