public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Lee <ler762@gmail.com>
To: cygwin@cygwin.com
Subject: building net-snmp: (was: Updated: net-snmp-5.8-1)
Date: Tue, 28 Apr 2020 11:38:50 -0400	[thread overview]
Message-ID: <CAD8GWstxAAQ_A0WzkLC71=CV_A_2xoG4YcQVY-25uV5stm+Zww@mail.gmail.com> (raw)

> If you want to make a point or ask a question the Cygwin mailing list is
> the appropriate place.

You don't need this anymore
  02-path-separator.patch
if you build net-snmp with
  export ENV_SEPARATOR=":"

And maybe now they'll accept a patch so that building on cygwin
doesn't require an evar.  I think  "gcc -mno-cygwin ..."  might still
have been supported when I tried to get it changed and the best they'd
do was an evar when building.


Is 06-winstub.patch necessary?  Necessary if all you're using is the
command line tools?
The changelog has this
commit fda421625d20d8f8201479fa7f33c257fdc72015
Author: Bart Van Assche <bvanassche@acm.org>
Date:   Sun Nov 27 11:25:40 2016 -0800

    Cygwin: getnetent() / getnetbyaddr() build fix

    Recent versions of Cygwin have prototypes but no implementation for
    these functions. Hence avoid that the Cygwin prototypes conflict
    with the implementation.

In other words, if I'm using just the snmp{get,set} command line
tools, should I be applying this patch?

Thanks,
Lee



On 4/27/20, David Rothenberger wrote:
> DESCRIPTION:
> ============
> Simple Network Management Protocol (SNMP) is a widely used protocol
> for monitoring the health and welfare of network equipment
> (eg. routers), computer equipment and even devices like
> UPSs. Net-SNMP is a suite of applications used to implement SNMP v1,
> SNMP v2c and SNMP v3 using both IPv4 and IPv6. The suite includes:
>
>   * Command-line applications to:
>     * retrieve information from an SNMP-capable device, either using
>       single requests (snmpget, snmpgetnext), or multiple requests
>       (snmpwalk, snmptable, snmpdelta).
>     * manipulate configuration information on an SNMP-capable device
>       (snmpset).
>     * retrieve a fixed collection of information from an
>       SNMP-capable device (snmpdf, snmpnetstat, snmpstatus).
>     * convert between numerical and textual forms of MIB OIDs, and
>       display MIB content and structure (snmptranslate).
>   * A graphical MIB browser (tkmib), using Tk/perl.
>   * A daemon application for receiving SNMP notifications
>      (snmptrapd). Selected notifications can be logged (to syslog,
>      the NT Event Log, or a plain text file), forwarded to another
>      SNMP management system, or passed to an external application.
>   * An extensible agent for responding to SNMP queries for
>     management information (snmpd). This includes built-in support
>     for a wide range of MIB information modules, and can be extended
>     using dynamically loaded modules, external scripts and commands,
>     and both the SNMP multiplexing (SMUX) and Agent Extensibility
>     (AgentX) protocols.
>   * A library for developing new SNMP applications, with both C and
>     perl APIs.
>
> CYGWIN NOTES:
> =============
>  * The snmpd daemon does not provide much useful information.
>    Installing it as a service under Cygwin is left as an exercise
>    for the user.
>
> QUESTIONS:
> ==========
> If you want to make a point or ask a question the Cygwin mailing list is
> the appropriate place.
>
>
> --
> David Rothenberger
>
> Remember:  Silly is a state of Mind, Stupid is a way of Life.
>                 -- Dave Butler
> --
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
>

             reply	other threads:[~2020-04-28 15:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 15:38 Lee [this message]
2020-04-28 15:58 ` Brian Inglis
2020-04-28 16:24 ` David Rothenberger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAD8GWstxAAQ_A0WzkLC71=CV_A_2xoG4YcQVY-25uV5stm+Zww@mail.gmail.com' \
    --to=ler762@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).