From: vischne AT ibm DOT net (Victor Schneider)
Subject: RE: Getting lynx.exe to compile _and_ _work_ from cygwin
22 Oct 1997 01:46:05 -0700
Message-ID: <1.5.4.16.19971022025717.269f5a3a.cygnus.gnu-win32@pop1.ibm.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: gnu-win32 AT cygnus DOT com

At 10:17 AM 10/22/97 +0300, you wrote:
>Victor Schneider wrote:
>> One plausible reason why lynx.exe won't work after being configured and
>> compiled under b18 cygwin32 is that the winsocket.dll initialization
>> function isn't called from lynx.  If you define `_WINDOWS' in
>
>Lynx configured and compiled under b18 cygwin runs fine! The initialisation
of winsock is performed by cygwin.dll's start-up code.
>
It doesn't work.  If you've run `./configure' and compiled the result, you
would know that (a) it doesn't read the control keys properly, unless you
use slang and (b) it can't look up named hosts.  I've done it enough times
with enough versions of lynx to know.  So, either you are very careless, or
you are lying.

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".