Hi, I'm trying to compile bird204 for test purpose, but I'm facing some errors, anyone have an idea? BIRD was configured with the following options: Source directory: . Object directory: obj Iproute2 directory: /etc/iproute2 System configuration: ./sysdep/cf/linux.h Debugging: no POSIX threads: yes Routing protocols: bgp pipe rpki Kernel MPLS support: no Client: yes root@lab-rs:~/bird# make MKDIR -p obj/client obj/conf obj/doc obj/filter obj/lib obj/nest obj/test obj/proto/bgp obj/proto/pipe obj/proto/rpki obj/sysdep/linux obj/sysdep/unix obj/doc m4 -s -P conf/gen_parser.m4 conf/confbase.Y conf/flowspec.Y obj/.dir-stamp filter/config.Y nest/config.Y proto/bgp/config.Y proto/pipe/config.Y proto/rpki/config.Y sysdep/linux/netlink.Y sysdep/unix/config.Y sysdep/unix/krt.Y >obj/conf/cf-parse.y bison -Dparse.lac=full -Dparse.error=verbose -dv -pcf_ -b obj/conf/cf-parse obj/conf/cf-parse.y conf/gen_parser.m4: warning: 11 nonterminals useless in grammar [-Wother] conf/gen_parser.m4: warning: 34 rules useless in grammar [-Wother] conf/confbase.Y:90.13-29: warning: nonterminal useless in grammar: label_stack_start [-Wother] %type <mls> label_stack_start label_stack ^^^^^^^^^^^^^^^^^ conf/confbase.Y:90.31-41: warning: nonterminal useless in grammar: label_stack [-Wother] %type <mls> label_stack_start label_stack ^^^^^^^^^^^ conf/confbase.Y:86.22-25: warning: nonterminal useless in grammar: time [-Wother] %type <time> expr_us time ^^^^ nest/config.Y:94.162-164: warning: nonterminal useless in grammar: tos [-Wother] %nonassoc PREFIX_DUMMY ^^^ nest/config.Y:440.1-13: warning: nonterminal useless in grammar: password_list [-Wother] []s
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 :-) 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: $ ./configure --with-protocols="bgp" && make obj/conf/cf-parse.tab.c $ top (in another terminal) VIRT RES SHR S %CPU %MEM TIME+ COMMAND 9420 4064 2268 R 99.7 0.0 1:07.58 bison Minimal protocol set I found working w/o any bison warnings was "bgp ospf static". Piotr -- Piotr 'GhosT' Wydrych ...... Senior II Lead Sw. Eng., SDN ....... Akamai ........................................................................ A: Because it messes up the order in which people normally read text. .. Q: Why is top-posting such a bad thing? ................................
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. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
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.
participants (3)
-
Ondrej Zajicek -
Piotr Wydrych -
Tiago Felipe Goncalves