Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <00b601c3028d$65a9d8a0$3f33fea9@HAPPYCOMPUTER>
From: "Gareth Pearce" <gpea0679 AT mail DOT usyd DOT edu DOT au>
To: <cygwin AT cygwin DOT com>
Subject: crypt...
Date: Mon, 14 Apr 2003 23:38:39 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

I was wondering if (other than for someone to actually do it) there was some
explicit reason for crypt to be seperate to cygwin?  Sort of makes
satisfying SUSv2 unistd.h impossible...  I see its optional in SUSv3 ...
Sure its simple to work arround, but it would be nice if it 'just worked'.

Regards,
Gareth



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