X-Spam-Check-By: sourceware.org
X-ORBL: [68.125.128.180]
Message-ID: <44069402.5010903@myrealbox.com>
Date: Wed, 01 Mar 2006 22:43:14 -0800
From: Tim Prince <tprince AT myrealbox DOT com>
Reply-To: tprince AT computer DOT org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050921
MIME-Version: 1.0
To: Basavaraj Hiremath <hbasava AT yahoo DOT com>
CC: cygwin AT cygwin DOT com
Subject: Re: compiler option
References: <20060302004154 DOT 89418 DOT qmail AT web36115 DOT mail DOT mud DOT yahoo DOT com>
In-Reply-To: <20060302004154.89418.qmail@web36115.mail.mud.yahoo.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Basavaraj Hiremath wrote:
> Hi,
> I am compiling a file(strerror.c) with following
> option
> -bash-2.05b$ arm-wince-pe-gcc -mcpu=xscale -c -ansi
> -D__stdcall= -D_OFF_T_ -DHA
> VE_CONFIG_H -I/usr/local/wince/cross-tools/include 
> -I. -I./../include  -W -Wal
> l -Wtraditional -pedantic  ./strerror.c -o
> pic/strerror.o
> 
> 
> It's giving following compilation error
> /strerror.c:626: error: expected identifier or '('
> before string constant
> /strerror.c:628: error: expected identifier or '('
> before '{' token
> 
> 
> 
> file strerror.c has following function
> 
> char *
> strerror (errnoval)  -> line 626
>   int errnoval;
> {                    --> line 628
>   const char *msg;
>   static char buf[32];
> -----------
> -----
> }
> 
> 
> Could somebody tell me, what is the compiler option to
> go pass thru this kind of implementation?
> 
I don't know that gcc has an option to accept such non-standard code.  I 
don't see how this is on topic for cygwin, particularly since cross 
compilers aren't part of the distribution.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/