Wireshark-dev: Re: [Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-ppc

From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Tue, 21 Apr 2009 13:04:46 -0700

On Apr 21, 2009, at 10:35 AM, buildbot-no-reply@xxxxxxxxxxxxx wrote:

The Buildbot has detected a new failure of OSX-10.5-ppc on Wireshark (development).
Full details are available at:
http://buildbot.wireshark.org/trunk/builders/OSX-10.5-ppc/builds/957

Buildbot URL: http://buildbot.wireshark.org/trunk/

Buildslave for this Build: osx-10.5-ppc

Build Reason:
Build Source Stamp: HEAD
Blamelist: etxrab,guy

BUILD FAILED: failed compile

The warnings are:

ranap.cnf:1490: warning: 'dissect_ranap_ForwardingIndication' defined but not used ranap.cnf:764: warning: 'dissect_ranap_LastVisitedUTRANCell_Item' defined but not used ranap.cnf:293: warning: 'dissect_ranap_Source_ToTarget_TransparentContainer' defined but not used ranap.cnf:303: warning: 'dissect_ranap_SourceeNodeB_ToTargeteNodeB_TransparentContainer' defined but not used ranap.cnf:483: warning: 'dissect_ranap_SRVCC_Operation_Possible' defined but not used ranap.cnf:493: warning: 'dissect_ranap_Target_ToSource_TransparentContainer' defined but not used ranap.cnf:503: warning: 'dissect_ranap_TargeteNodeB_ToSourceeNodeB_TransparentContainer' defined but not used

What causes unused dissector routines to be generated by asn2wrs? I have the impression that there's stuff you can put into the .cnf file to suppress them, but is there a way for asn2wrs to recognize that something won't be used?