RE: [libsmi] libsmi release 0.2.17
Hi Frank,
It seems that the code implementing the caching (in data.c) is Unix oriented and do not compile under windows. After removing thie code everything compiled successfully.
Mark Kaplun Tel: +1-972-3-7370751 Mobile: +1-972-55-636751 e-mail: mark@xor-t.com
-----Original Message----- From: Frank Strauss [mailto:strauss@ibr.cs.tu-bs.de] Sent: Friday, August 24, 2001 12:51 PM To: libsmi Mailinglist Subject: [libsmi] libsmi release 0.2.17
Hi!
After a long silent period there's now a new libsmi release on the FTP server. It...
o fixes a lot of memory leaks (though not yet all),
o updates and adds some MIB checks,
o fixes and updates some output drivers,
o adds a simple MIB file caching scheme (experimental!),
o includes the (expired!) Internet-Draft on the currently implemented XML output format of smidump and the according DTD,
o introduces a scheme to allow a single application to use multiple sets of MIB data.
Furthermore, CVS users will recognize that a number of files are gone and an autogen.sh script has been added to ease the build process from the CVS repository.
See the ChangeLog file for more details. As usual the current release can be found at
http://www.ibr.cs.tu-bs.de/projects/libsmi/ ftp://ftp.ibr.cs.tu-bs.de/pub/local/libsmi/
Enjoy,
-frank -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information. -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.
Hi!
Mark> It seems that the code implementing the caching (in data.c) is Unix Mark> oriented and do not compile under windows. Mark> After removing thie code everything compiled successfully.
Could you provide more detailed information why it failed, maybe a make output dump? AFAIK, at least one other W32 user did not have these problems.
-frank -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.
Hi Frank,
The cygwin build on and for w32 platform is ok.
There are a few problems building for w32 platform with MS compiler in win dir.
1. The win/makefile needs to be updated (I will mail you a patch for this).
2. The code using fork() and waitpid() cannot be used in MS environment. I had to ifdef it out.
Frank Strauss strauss@ibr.cs.tu-bs.de wrote:
Hi!
Mark> It seems that the code implementing the caching (in data.c) is Unix Mark> oriented and do not compile under windows. Mark> After removing thie code everything compiled successfully.
Could you provide more detailed information why it failed, maybe a make output dump? AFAIK, at least one other W32 user did not have these problems.
-frank
!! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.
Hi!
Thanks, Yigal, for the clarification. Your patches are welcome. ;-)
For those that don't know: I do not use Windows systems at all. All libsmi w32 support is based on contributions, most from Yigal.
-frank -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.
Hi Frank,
I would your input on two items:
1. win/makefile - I mailed you the list of lib files (please confirm). 2. Is it functionally ok to compile out the for/wait() in loadModule()
Thanks,
Frank Strauss strauss@ibr.cs.tu-bs.de wrote:
Hi!
Thanks, Yigal, for the clarification. Your patches are welcome. ;-)
For those that don't know: I do not use Windows systems at all. All libsmi w32 support is based on contributions, most from Yigal.
-frank
Hi!
Yigal> I would your input on two items:
Yigal> 1. win/makefile - I mailed you the list of lib files (please confirm).
I've applied the change you proposed in that other email. I cannot definetly confirm it, since I don't speak Windows. But it looks correct as far as I can tell.
Yigal> 2. Is it functionally ok to compile out the for/wait() in loadModule()
Yes. As stated in my recent mail, I've now #ifdef'ed a broader block in loadModule() and other places related to the caching mechanism. This simply makes the caching scheme unsported as if UNIX users would not use the `cache' configuration file command.
-frank -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.
Hi Frank,
Frank Strauss strauss@ibr.cs.tu-bs.de wrote:
Yigal> 1. win/makefile - I mailed you the list of lib files (please confirm).
I've applied the change you proposed in that other email. I cannot definetly confirm it, since I don't speak Windows. But it looks correct as far as I can tell.
The change in win/makefile is not w32 specific. It is an update of the object files which required to build the library for libsmi.
Note that win/GNUmakefile requires no changes. It picks the files automatically by the $(wildcard ) function.
Yigal> 2. Is it functionally ok to compile out the for/wait() in loadModule()
Yes. As stated in my recent mail, I've now #ifdef'ed a broader block in loadModule() and other places related to the caching mechanism. This simply makes the caching scheme unsported as if UNIX users would not use the `cache' configuration file command.
-frank
Thanks,
participants (3)
-
Frank Strauss -
Mark Kaplun -
Yigal Hochberg