X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Mark Geisert Subject: Re: building a cygwin aware GHC Date: Wed, 19 Oct 2011 23:30:24 +0000 (UTC) Lines: 13 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Nathan Thern writes: > The problem with GHC is that the windows version is compiled with > MinGW, and cygwin is considered to be nothing other than a MinGW > alternative. IOW, the source code is riddled with assumptions that if > you are building GHC with cygwin then what you want in the end is a > cygwin-unaware windows-compliant executable. Rather than using "the windows version" is there a Linux or Unix version you could start with? That path might be easier to get running under Cygwin. ..mark -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple