public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: building net-snmp: (was: Updated: net-snmp-5.8-1)
Date: Tue, 28 Apr 2020 09:58:51 -0600	[thread overview]
Message-ID: <176f156b-b42b-6573-0f19-840caa5445b4@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAD8GWstxAAQ_A0WzkLC71=CV_A_2xoG4YcQVY-25uV5stm+Zww@mail.gmail.com>

On 2020-04-28 09:38, Lee via Cygwin wrote:
>> 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?

The current /usr/include/netdb.h definitions from cygwin-devel match the
prototypes under endnetent(3p) and netdb.h(0p) from man-pages-posix.
If you don't have cygwin-devel installed it shouldn't be an issue, and the
supplied implementation of the missing interfaces should match the POSIX specs:

	https://pubs.opengroup.org/onlinepubs/009695399/basedefs/netdb.h.html

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 15:38 Lee
2020-04-28 15:58 ` Brian Inglis [this message]
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=176f156b-b42b-6573-0f19-840caa5445b4@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).