From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: jozsefke@freemail.hu, cygwin@cygwin.com
Subject: Re: Compiling SocksCap under Cygwin
Date: Mon, 22 Apr 2002 07:32:00 -0000 [thread overview]
Message-ID: <4.3.1.2.20020422101402.02a87ac8@pop.ma.ultranet.com> (raw)
In-Reply-To: <5.1.0.14.0.20020422132231.00a547d0@freemail.hu>
At 07:36 AM 4/22/2002, jozsefke@freemail.hu wrote:
>I have verified on a Debian Linux, that the IFF_POINTOPOINT is defined in the '/usr/lib/net/if.h' header file. On this machine the
>compilation of SocksCap was successful. Why isn't defined this macro in Cygwin?
Because nobody has contributed it. Are you interested in doing so?
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
838 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
prev parent reply other threads:[~2002-04-22 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 5:09 jozsefke
2002-04-22 7:32 ` Larry Hall (RFK Partners, Inc) [this message]
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=4.3.1.2.20020422101402.02a87ac8@pop.ma.ultranet.com \
--to=lhall@rfk.com \
--cc=cygwin@cygwin.com \
--cc=jozsefke@freemail.hu \
/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).