RE: Installing Net-SNMP on Bash on Ubuntu on Windows

Christian Salem <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <YTOPR0101MB14183432964FE8F2BAE31FA5A8E10@YTOPR0101MB1418.CANPRD01.PROD.OUTLOOK.COM>
Thank you Bill for your response! Sorry I couldn’t reply earlier.

As for the issue I was facing, I couldn’t fix it and I will probably move to Linux. However, I am trying to install net-snmp on Windows 10 as a last resort following the instructions here<http://net-snmp.sourceforge.net/wiki/index.php/Using_the_command_line_and_nmake_(VC%2B%2B_2010_Express)>. I was able to install the requirements but when I run build.bat and enter all the options, the build starts and I get the following message:

…
Select option to set / toggle: f

Building...

Creating *.out log files.

Deleting old log files...
Running Configure...
Cleaning...
Building main package...
Build error (see make.out) at build.pl line 232, <> line 9.

Do you have any idea why this is happening? I tried to solve it but couldn’t.

Sorry if I should have posted this as another question rather than replying to you.

Thank you!
Christian




From: Bill Fenner [mailto:[email protected]]
Sent: January 22, 2018 9:17 AM
To: Christian Salem <[email protected]>
Cc: [email protected]
Subject: Re: Installing Net-SNMP on Bash on Ubuntu on Windows

On Fri, Jan 19, 2018 at 5:16 PM, Christian Salem <[email protected]<mailto:[email protected]>> wrote:
Hi all,

I am new to net-snmp and would greatly appreciate any help you guys can provide.
I’m working on Bash on Ubuntu on Windows, trying to install net-snmp in a Linux environment. I followed the instructions here<https://www.maketecheasier.com/net-snmp-part-1/>.

Those instructions are pretty weird: why do they have you build and install net-snmp from scratch, and then overwrite the snmpd with the upstream version?

I installed all the required dependencies for net-snmp but when I try to run the make command, I get the following output at the end before it stops:

“
…
make[1]: Entering directory '/mnt/c/Users/c_salem/Desktop/netsnmpinstall/net-snmp-5.7.3/mibs'
make[1]: Leaving directory '/mnt/c/Users/c_salem/Desktop/netsnmpinstall/net-snmp-5.7.3/mibs'
make[1]: Entering directory '/mnt/c/Users/c_salem/Desktop/netsnmpinstall/net-snmp-5.7.3/perl'
make[2]: Entering directory '/mnt/c/Users/c_salem/Desktop/netsnmpinstall/net-snmp-5.7.3/perl/default_store'
Manifying 1 pod document
Can't write-open ../blib/man3/NetSNMP::default_store.3pm: Invalid argument at /usr/share/perl/5.22/ExtUtils/Command/MM.pm line 147.

You're building on a Windows filesystem, and Windows files can not have colons in them.  You may be able to do better if you use the Linux filesystem (a path that does not start with /mnt).

Finally I run apt-get install snmpd, then  /etc/init.d/snmpd start but I get the following error:

This will install something that is incompatible with the thing you just built and installed, so is not advisable.  This is a problem with the instructions you are following.

I imagine that there are two possible paths forward:

1. Build on the Linux filesystem, so that you can have filenames with colons.  (That is why both your "make" and your "make install" failed).
2. Keep trying to use the Windows filesystem, but don't build the perl stuff.  This involves passing the right "--disable-foo" options to ./configure; you could try "./configure --help" and see if you can figure out which options are correct.  (And there's no guarantee that there isn't something else going on in the Windows filesystem that will mess up the build.)

  Bill

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.