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
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 21 Feb 2002 10:41:12 +0100
From: Corinna Vinschen <cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Question about writing reports
Message-ID: <20020221104112.F23094@cygbert.vinschen.de>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3C743EA8 DOT 1D1FD603 AT pobox DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3C743EA8.1D1FD603@pobox.com>
User-Agent: Mutt/1.3.22.1i

On Wed, Feb 20, 2002 at 06:26:17PM -0600, Jonathan Hayward wrote:
> I posted an apparent bug report about gcc/Cygwin 1.3.9 aborting on
> function prototypes that worked flawlessly under gcc/RH. I tried to
> write a descriptive statement and included cygcheck output. It was
> posted about a week ago, and I haven't seen a reply yet. Is there
> further information I can post that will be useful in replying?

Sorry but, what reply do you expect?  The error message is very
likely caused by a datatype not known by Cygwin.  You changed the
Makefile to define __WINDOWS__ and __WIN32__.  That's not the best
way to build a Cygwin binary since the package could use these
defines to include different headers and such.  When compiling for
Cygwin, try the pure unixy way first.  And you're talking about a
header `crypt.h'.  You know that a header with that name already
exists in Cygwin, don't you?

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

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