[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [openrisc] eCos & gcc bug

To: openrisc@opencores.org
Subject: Re: [openrisc] eCos & gcc bug
From: Scott Furman <sfurman@rosum.com>
Date: Thu, 17 Apr 2003 22:37:32 -0700
In-Reply-To: <20030417100417.GF29636@vortex.si.ring>
References: <20030417100417.GF29636@vortex.si.ring>
Reply-To: openrisc@opencores.org
Sender: owner-openrisc@opencores.org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312

phoenix wrote:

>while trying to compile ecos for or1k reference platform i've stumbled
>accreoss this gcc bug. did anyone else see this or has any ideas ?
>  
>
I've never seen this bug because I've never included the date/time 
functions in my build.  As a workaround, I suggest that you remove the 
"ISO C date/time functions" package from  your eCos build using 
configtool.  (If your application doesn't make use of them, then these 
date/time functions are superfluous since they are not used by eCos itself.)

Also, I suggest you pick up the very latest OpenRISC eCos code from the 
ecos-patches mailing list.  It has a few small, but important bug fixes.

-Scott


--
To unsubscribe from openrisc mailing list please visit http://www.opencores.org/mailinglists.shtml

References:
- [openrisc] eCos & gcc bug
  - From: phoenix <phoenix@opencores.org>

Prev by Date: RE: [openrisc] Re: OpenRISC eCos package
Next by Date: Re: [openrisc] fopen() not defined??
Prev by thread: [openrisc] eCos & gcc bug
Next by thread: Re: [openrisc] eCos & gcc bug
Index(es):
- Date
- Thread