HI,
The message below is not correct. That is, it is not a warning situtuation and the term "object identifier" is not at all appropriate.
I suggest the folloing text, if you still want to emit this bogus warning.
So, for bar OBJECT-TYPE .... ::= { gar foo(3) } and soo OBJECT-TYPE .... ::= { gar foo(4) }
Emit the following messages: ./XXX-MIB:165: warning: local label "foo" used for OID value of "soo" has been previously used with a different sub-identifier value ./XXX-MIB:40: info: previous definition of `snmpDot3MauMgt'
But again, the above is NOT illegal and it is fine to have the following OID values: ::= { gar foo(1) foo(2) bar(3) bar(4) } ... ::= { gar bar(1) guw(2) foo(3) foo(4) } ... ::= { gar foo(2) } ... ::= { gar bar(2) } etc
On Tue, 30 Nov 2004, [ISO-8859-1] Frank Strau� wrote:
Thanks to all who contributed to this issue. I've just comitted a new revision to the libsmi SVN repository that handles OID and identifiers in the "NameAndNumberForm" more acurately, and also emits warnings such as...
./XXX-MIB:165: warning: object identifier for label `snmpDot3MauMgt' does not match previous label usage ./XXX-MIB:40: info: previous definition of `snmpDot3MauMgt'
./XXX-MIB:165: warning: label `snmpDot3MauMgtXXX' does not match previous label `snmpDot3MauMgt' for same object identifier ./XXX-MIB:40: info: previous definition of `snmpDot3MauMgt'