Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 5 Jun 2002 11:16:02 -0400 From: Christopher Faylor To: cygwin@cygwin.com Cc: gnupg-devel@gnupg.org Subject: Re: Patches for gnupg 1.0.7 / cygwin 1.3.10 Message-ID: <20020605151602.GH15167@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com, gnupg-devel@gnupg.org References: <3CFCE281.3030806@scytek.de> <3CFE118D.2010900@scytek.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CFE118D.2010900@scytek.de> User-Agent: Mutt/1.3.23.1i On Wed, Jun 05, 2002 at 03:26:37PM +0200, Volker Quetschke wrote: >>>cases with __CYGWIN__ for the file handling to use its own (standard >>>posix) file handling. Cygwin does have a /dev/random, therefore I >>>changed from rndw32 to rndlinux. >> >>This seems to be a new feature - did you review the architecture of >>this device? > >I got the hint from the cygwin list and I tried to use it with the >build of gnupg. There were two include files missing for rndunix but >it compiled with rndlinux. And a cygwin build gpg works with rndlinux. /dev/random isn't a new feature. It was introduced more than two years ago. cgf -- 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/