Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <3E494DC6.7080705@hekimian.com> Date: Tue, 11 Feb 2003 14:23:50 -0500 X-Sybari-Trust: 6600f6d8 f29b823d fc094493 00000139 From: Joe Buehler Reply-To: jbuehler AT hekimian DOT com Organization: Spirent Communications, Inc. User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3a) Gecko/20021212 X-Accept-Language: en-us, en MIME-Version: 1.0 CC: Cygwin Developers Subject: Re: gcc failure when building current CVS References: <3E494C02 DOT 8040808 AT hekimian DOT com> In-Reply-To: <3E494C02.8040808@hekimian.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Joe Buehler wrote: > /usr/local/src/cygwin-src/build-output/gcc That strange path is just a front-end script that massages -O options to force building with -g (easiest way I have found to do that...). > -nostdinc++ -iwithprefixbefore include -mno-cygwin Taking out -mno-cygwin makes the problem go away. So what am I doing wrong? -- Joe Buehler