Folks, Please do not create plugins which contain the following global declaration: "void vat_api_hookup (vat_main_t * vam)".
The result of naming the api hookup function that particular thing will be a stream of multiple-registration complaints, to say nothing of questionable results in terms of actually registering the intended binary API message handlers: 0: vl_msg_api_config:664: BUG: multiple registrations of 'vl_api_create_loopback_instance_reply_t_handler' 0: vl_msg_api_config:664: BUG: multiple registrations of 'vl_api_sw_interface_details_t_handler' 0: vl_msg_api_config:664: BUG: multiple registrations of 'vl_api_sw_interface_set_flags_reply_t_handler' 0: vl_msg_api_config:664: BUG: multiple registrations of 'vl_api_control_ping_reply_t_handler' 0: vl_msg_api_config:664: BUG: multiple registrations of 'vl_api_cli_reply_t_handler' 0: vl_msg_api_config:664: BUG: multiple registrations of 'vl_api_cli_inband_reply_t_handler' 0: vl_msg_api_config:664: BUG: multiple registrations of 'vl_api_sw_interface_add_del_address_reply_t_handler' 0: vl_msg_api_config:664: BUG: multiple registrations of 'vl_api_sw_interface_set_table_reply_t_handler' 0: vl_msg_api_config:664: BUG: multiple registrations of 'vl_api_sw_interface_set_mpls_enable_reply_t_handler' 0: vl_msg_api_config:664: BUG: multiple registrations of 'vl_api_sw_interface_set_vpath_reply_t_handler' 0: vl_msg_api_config:664: BUG: multiple registrations of 'vl_api_sw_interface_set_vxlan_bypass_reply_t_handler' 0: vl_msg_api_config:664: BUG: multiple registrations of 'vl_api_sw_interface_set_l2_xconnect_reply_t_handler' <snip> Instead, please create "static void my_api_hookup (vat_main_t *vam)" or some such. See https://gerrit.fd.io/r/#/c/5707. Thanks... Dave
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
