Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <39897236.7E6E844D@cygnus.com> Date: Thu, 03 Aug 2000 15:23:02 +0200 From: Corinna Vinschen Reply-To: cygwin X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.14-SMP i686) X-Accept-Language: de, en MIME-Version: 1.0 To: Jason Tishler CC: cygwin AT sources DOT redhat DOT com Subject: Re: Building Mutt with S-Lang References: <20000803091031 DOT E1036 AT DP> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jason Tishler wrote: > > Has anyone been successful building a Cygwin version of Mutt with S-Lang? > > It very was easy to build Mutt 1.2.4 with ncurses 5.0. > > When upgrading from Mutt 1.2.4 to 1.2.5, I decided to try to build > Mutt with S-Lang 1.4.1. The Cygwin version of Mutt is looking for a > UNIX-ish S-Lang but the Cygwin version of S-Lang is PC-ish. There are > both compiler (ie, missing/incorrect #defines) and linker issues (ie, > unresolved symbols). > > Any suggestions would be appreciated. Even the old adage, "Don't do > that!" Don't do that. Or, in other words: gcc defines the symbol WIN32 by default which is often used in ports to determine that it's just being compiled on a native Windows system (with VC++ or whatever). If you're using the current latest version of cygwin's gcc, try `-mno-win32'. All versions of gcc should allow -UWIN32 or -U_WIN32. Simply try it. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT sources DOT redhat DOT com Red Hat, Inc. mailto:vinschen AT cygnus DOT com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com