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:	<DF08E278E10FC14F87CE7E802ABFD04BF017BA@EXCHANGE01.air2web.com>
From:	Richard Campbell <richard DOT campbell AT air2web DOT com>
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject:	RE: crypt command
Date:	Wed, 3 Apr 2002 15:25:19 -0500
MIME-Version:	1.0

>If the Cygwin build ends up trying to pull in Mingw header files, the 
>configuration of the package is wrong.  That could be a package problem 
>though.  I expect it's just an indicator of a configuration issue.  The 
>segv would be another.

The mhash package is definitely intended to be built under mingw, which 
seems to be failing.  It includes "ctype.h" under it's standard c libraries
list, which seems to have problems under mingw.

I actually reuntarred and tried building again.

If I comment out all references to ctype.h, the package builds cleanly, 
but fails with what is actually a "Signal 11".

I tried stepping through with gdb, but the area of code that is playing 
around here seems to be some interesting macros.

At this point previously, I hoped it was something I had done to get the 
compile to be clean, but considering that this time around I didn't change
any code (simply removed an include), I believe it's the mhash library's
fault, but I don't know enough to procede.

-Richard Campbell.

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

- Raw text -