Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3C75010C.2F4FB902@pobox.com> Date: Thu, 21 Feb 2002 08:15:41 -0600 From: Jonathan Hayward Organization: Eolas Technologies X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i686) X-Accept-Language: en MIME-Version: 1.0 To: cygwin AT cygwin DOT com CC: mike AT eolas DOT com Subject: Re: Question about writing reports Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > 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? > Thank you for all these. I'll try to see what I can do without __WINDOWS__, trying to avoid "crypt.h" conflicts, etc. Much appreciated! -- Jonathan Hayward jshayward AT pobox DOT com http://JonathansCorner.com (A four dimensional maze, stories, essays, artwork, and other things...) -- 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/