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 Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 19 Dec 2002 00:16:42 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: compiler complains about its own 'mingw' files Message-ID: <20021219051642.GC30595@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20021219045045 DOT 88309 DOT qmail AT web20808 DOT mail DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021219045045.88309.qmail@web20808.mail.yahoo.com> User-Agent: Mutt/1.5.1i On Wed, Dec 18, 2002 at 08:50:45PM -0800, bubba bubba wrote: >>1) Please provide cygcheck output as mentioned at >> http://cygwin.com/bugs.html . > >OK, see attachment Oh well. Nothing obvious there. You might try uninstalling gcc2, gcc, gcc-mingw, and mingw-runtime. Then reinstall just gcc, gcc-mingw, and mingw-runtime. >>2) Please provide a simple testcase illustrating the >>problem. > >Try compiling zangband-2.7.1 found at www.zangband.org. To compile go >to zangband/src type make -f makefile.std cygwin The theory is that a simple test case makes it easy for me to test. "Simple" in this context means provide a simple C program and the simplest possible gcc command line to replicate the problem. cgf -- 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/