Libsmi July 2002

libsmi@ibr.cs.tu-bs.de

8 participants
7 discussions

problems compiling in windows
by Cristian Salcedo (CEC) 21 Jul '02

21 Jul '02

I tried to compile in win200 with vc++ version 6.0 and I got the following compilation errors ...... can anyone help????? cl -Z7 -Od -c -W3 -DCRTAPI1=_cdecl -DCRTAPI2=_cdecl -nologo -D_X86_=1 -D _WINNT -D_WIN32_WINNT=0x0400 -D_WIN32_IE=0x0300 -DWINVER=0x0400 -I.\..\lib -I.\. .\win -I"C:\Program Files\Microsoft Visual Studio\VC98"\include -Fo.\ .\..\tools\dump-scli.c dump-scli.c .\..\tools\dump-scli.c(560) : warning C4018: '<' : signed/unsigned mismatch .\..\tools\dump-scli.c(790) : warning C4018: '<' : signed/unsigned mismatch .\..\tools\dump-scli.c(1013) : warning C4018: '<' : signed/unsigned mismatch cl -Z7 -Od -c -W3 -DCRTAPI1=_cdecl -DCRTAPI2=_cdecl -nologo -D_X86_=1 -D _WINNT -D_WIN32_WINNT=0x0400 -D_WIN32_IE=0x0300 -DWINVER=0x0400 -I.\..\lib -I.\. .\win -I"C:\Program Files\Microsoft Visual Studio\VC98"\include -Fo.\ .\..\tools\dump-xsd.c dump-xsd.c .\..\tools\dump-xsd.c(715) : warning C4101: 'i' : unreferenced local variable .\..\tools\dump-xsd.c(829) : warning C4018: '<' : signed/unsigned mismatch cl /osmidump.exe .\smidump.obj .\dump-sming.obj .\dump-smi.obj .\dump-imports.obj .\dump-types.obj .\dump-tree.obj .\dump-mosy.obj .\dump-corba.obj .\dump-netsnmp.obj .\dump-jax.obj .\dump-xml.obj .\dump-cm.obj .\dump-metrics.obj .\dump-identifiers.obj .\dump-python.obj .\dump-perl.obj .\dump-scli.obj .\dump-xsd.obj smi.lib Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8168 for 80x86 Copyright (C) Microsoft Corp 1984-1998. All rights reserved. Microsoft (R) Incremental Linker Version 6.00.8168 Copyright (C) Microsoft Corp 1992-1998. All rights reserved. /out:smidump.exe /out:smidump.exe .\smidump.obj .\dump-sming.obj .\dump-smi.obj .\dump-imports.obj .\dump-types.obj .\dump-tree.obj .\dump-mosy.obj .\dump-corba.obj .\dump-netsnmp.obj .\dump-jax.obj .\dump-xml.obj .\dump-cm.obj .\dump-metrics.obj .\dump-identifiers.obj .\dump-python.obj .\dump-perl.obj .\dump-scli.obj .\dump-xsd.obj smi.lib smidump.obj : error LNK2001: unresolved external symbol _initSppi smidump.obj : error LNK2001: unresolved external symbol _initSmiv3 smidump.exe : fatal error LNK1120: 2 unresolved externals NMAKE : fatal error U1077: 'cl' : return code '0x2' Stop.

2 1

Re: [libsmi] problems compiling in windows
by Yigal Hochberg 19 Jul '02

19 Jul '02

Hi Cristian, You are missing a file in win/makefile. The GNUmakefile picks up all files automatically (almost). You can get GNU make for w32 (gmake.exe) and use win/GNUmakefile like this: gmake Or: gmake -f GNUmakefile Also see win/README.win for more details. Regards, Cristian Salcedo (CEC) <cristian.salcedo(a)cec.ericsson.se> wrote: > > This message is in MIME format. Since your mail reader does not understand > this format, some or all of this message may not be legible. > > ------_=_NextPart_001_01C22F4A.5C3D5E2A > Content-Type: text/plain; > charset="iso-8859-1" > > > > I tried to compile in win200 with vc++ version 6.0 > > and I got the following compilation errors ...... can anyone help????? > > cl -Z7 -Od -c -W3 -DCRTAPI1=_cdecl -DCRTAPI2=_cdecl -nologo -D_X86_=1 -D > _WINNT -D_WIN32_WINNT=0x0400 -D_WIN32_IE=0x0300 -DWINVER=0x0400 -I.\..\lib -I.\. > .\win -I"C:\Program Files\Microsoft Visual Studio\VC98"\include -Fo.\ .\..\tools\dump-scli.c > dump-scli.c > .\..\tools\dump-scli.c(560) : warning C4018: '<' : signed/unsigned mismatch > .\..\tools\dump-scli.c(790) : warning C4018: '<' : signed/unsigned mismatch > .\..\tools\dump-scli.c(1013) : warning C4018: '<' : signed/unsigned mismatch > > cl -Z7 -Od -c -W3 -DCRTAPI1=_cdecl -DCRTAPI2=_cdecl -nologo -D_X86_=1 -D > _WINNT -D_WIN32_WINNT=0x0400 -D_WIN32_IE=0x0300 -DWINVER=0x0400 -I.\..\lib -I.\. > .\win -I"C:\Program Files\Microsoft Visual Studio\VC98"\include -Fo.\ .\..\tools\dump-xsd.c > dump-xsd.c > .\..\tools\dump-xsd.c(715) : warning C4101: 'i' : unreferenced local variable > .\..\tools\dump-xsd.c(829) : warning C4018: '<' : signed/unsigned mismatch cl > > /osmidump.exe > .\smidump.obj > .\dump-sming.obj > .\dump-smi.obj > .\dump-imports.obj > .\dump-types.obj > .\dump-tree.obj > .\dump-mosy.obj > .\dump-corba.obj > .\dump-netsnmp.obj > .\dump-jax.obj > .\dump-xml.obj > .\dump-cm.obj > .\dump-metrics.obj > .\dump-identifiers.obj > .\dump-python.obj > .\dump-perl.obj > .\dump-scli.obj > .\dump-xsd.obj smi.lib > Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8168 for 80x86 > Copyright (C) Microsoft Corp 1984-1998. All rights reserved. > > Microsoft (R) Incremental Linker Version 6.00.8168 > Copyright (C) Microsoft Corp 1992-1998. All rights reserved. > > /out:smidump.exe > /out:smidump.exe > .\smidump.obj > .\dump-sming.obj > .\dump-smi.obj > .\dump-imports.obj > .\dump-types.obj > .\dump-tree.obj > .\dump-mosy.obj > .\dump-corba.obj > .\dump-netsnmp.obj > .\dump-jax.obj > .\dump-xml.obj > .\dump-cm.obj > .\dump-metrics.obj > .\dump-identifiers.obj > .\dump-python.obj > .\dump-perl.obj > .\dump-scli.obj > .\dump-xsd.obj > smi.lib > smidump.obj : error LNK2001: unresolved external symbol _initSppi > smidump.obj : error LNK2001: unresolved external symbol _initSmiv3 > smidump.exe : fatal error LNK1120: 2 unresolved externals > NMAKE : fatal error U1077: 'cl' : return code '0x2' > Stop. > -- - Yigal

1 0

smidump and agent capabilities
by Robert Steinberger 12 Jul '02

12 Jul '02

All, Are there any plans, or is there any perceived need, for the ability to dump a view of the MIB with the agent capabilities applied? Thanks, Rob Steinberger.

2 1

Support for SNMPv3
by Shubhangi Jadhav 09 Jul '02

09 Jul '02

Hi, I would like to know whether libsmi supports SNMPv3 Thanks, Shubhangi

3 4

Can modules be unloaded.
by Yogeshwara G 04 Jul '02

04 Jul '02

Hi! I would like to know is there any way to unload and/or reload a loaded module? Thanks, Yogesh

2 1

SMI_INDEX_EXTEND vs. SMI_INDEX_SPARSE
by Moritz Bunkus 02 Jul '02

02 Jul '02

Hi. There is no difference between these two. SMI_INDEX_EXTEND is a left-over, nothing more - I forgot to remove it from smi.h.in. It is not used anywhere anymore. Don't worry about it :) -- ==> Ciao, Mosu

2 1

SMI_INDEX_EXTEND vs. SMI_INDEX_SPARSE
by Juergen Schoenwaelder 02 Jul '02

02 Jul '02

The recent SPPI support introduces SMI_INDEX_EXTEND. What is the difference between SMI_INDEX_EXTEND and SMI_INDEX_SPARSE? /js -- Juergen Schoenwaelder <http://www.informatik.uni-osnabrueck.de/schoenw/>

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Libsmi July 2002