X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=BAYES_00,RCVD_NUMERIC_HELO,SPF_HELO_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Oleksandr Gavenko Subject: Re: __STRICT_ANSI__ with -std=c99 Date: Mon, 22 Mar 2010 16:28:38 +0200 Lines: 13 Message-ID: References: <4BA770DA DOT 7040901 AT aol DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 In-Reply-To: <4BA770DA.7040901@aol.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On 2010.03.22 15:30, Tim Prince wrote: > On 3/22/2010 6:03 AM, Oleksandr Gavenko wrote: >> >> Current workaround is undefine __STRICT_ANSI__: >> >> $ gcc -std=c99 -U__STRICT_ANSI__ -c -o grid.o grid.c >> >> >> Where is proper place to report issue? > If you want c99 plus gcc extensions without warnings, how about > -std=gnu99? It seems this may become the default soon. > -std=gnu99 work. It seems better then -U__STRICT_ANSI__. -- 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