Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
X-Envelope-Sender-Is: ehouts AT efficient DOT com (at relayer ns0.sbs.siemens.com)
Message-ID: <36C2EB69D2F9D411A9AB00D0B7200334A2478E@eniwest.inside.efficient.com>
From: Ean Houts <ehouts AT efficient DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: openssh-3.0.1p1-2:zlib error
Date: Wed, 28 Nov 2001 12:27:51 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"

Not sure if this is really a bug, but it was definately unclear to
me...anyway, I'm trying to compile openssh, which requires zlib. 

I'm running on NT4.0, with the latest cygwin, gcc, etc. installed.

I installed the latest zlib from one of the cygwin mirrors, but still got
the  '*** zlib missing - please install first or check config.log ***' error
when trying to run configure.  I triple checked everything for zlib and it
was fine, so I downloaded the source, compiled it, ran test ok and used that
dll - same prob.  I even specified the --with-zlib= option to specify an
explicit path, with the same result. 

So, I faked out the part of configure that checks for it, and got as far as
the regex check...that was missing too.  So, I installed that, and suddenly
openssh was able to find zlib!  Everything proceeded fine from there, but
the zlib missing error was definately misleading.

thanks,
Ean

--
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/