Hi Frank , Thanks you for ur modification . Is this fixed on windows version also . How can I set the SMIPATH ( mib directory path ) at runtime for smilint ? . How do I write configuration file for smilint ?, so that I can specify the mibs path in the configuration file .
Can u plz help me out . I am using the windows binary of libsmi .
Thanks Rohit
-----Original Message----- From: Frank Strauß [mailto:strauss@ibr.cs.tu-bs.de] Sent: Monday, May 15, 2006 7:24 PM To: Rohit Palthad Venkataramana (rovenkat); libsmi@ibr.cs.tu-bs.de Subject: Re: [libsmi] Regarding Unsigned64 interpretation by SMILINT
Juergen Schoenwaelder wrote:
On Thu, May 04, 2006 at 01:39:04PM +0530, Rohit Palthad Venkataramana (rovenkat) wrote:
We import it using CISCO-TC MIB .
OK. So you essentially have a definition for Unsigned64 which should be valid as long as it is used by SMIv2 modules but it should be invalid if used by SPPI modules and libsmi always complains. I am not sure how easy it will be to fix this because libsmi treats Unsigned64 internally as a base type and Counter64 actually as a type derived from Unsigned64 (basically following the SMIng model). Frank, do you have an idea how to address this name clash?
For now, I have written a test case for libsmi and checked it into the SVN repository which demonstrates the problem.
I have just modified the parser so that it now accepts (and warns) about such type definitions that match existing SPPI or SMI base type names.
$ SMIPATH=:test/mibs ./tools/smilint test/mibs/LIBSMI-TEST-018-MIB test/mibs/LIBSMI-TEST-018-MIB:41: warning: definition of identifier `Unsigned64' which is already a SMI or SPPI basetype