Re: Two additional errors of GCC 2.96

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

 



The Gcc 2.96 is provided by WindRiver with it's tool Tornado, which is GUI tool for vxworks. I don't how the version number 2.96 come from. It's just the result of "gcc -v". I have contact with Wind River. I am not very familiar with gcc. Is it easy to change my gcc to 3.3.4? Does it perform just like the one provided by WindRiver?
Thanks a lot!

name:   jiayu 
email:   jiayu@xxxxxxxxxx

**************************************************************
This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
**************************************************************

----- Original Message -----
From: Eljay Love-Jensen <eljay@xxxxxxxxx>
Date: Saturday, August 21, 2004 7:52 pm
Subject: Re: Two additional errors of GCC 2.96

> Jiayu,
> 
> I recommend upgrading to the most current version of GCC.  Either 
> GCC 3.4.1 
> (latest and greatest), or GCC 3.3.4 (yesterday's tried and true).
> 
> There is no "GCC 2.96".  It's an unofficial, maverick release of 
> GCC by Red 
> Hat.  It's not supported on this forum (although we do give some 
> general 
> advice).
> 
> Your code snippets are incomplete.
> 
> Is your enum supposed to be missing the terminating semicolon (and 
> thus 
> typedefing to VOS_UINT16)?  If so,  have you tried separating out 
> g_uwLogicalBoardNo variable from the typedef?
> 
> Is your VOS_NULL_WORD define supposed to come AFTER it is being used?
> 
> Is your typedef of VOS_UINT16 supposed to come AFTER it is being used?
> 
> For your "compiler can't assign by structure"...
> 
> Is there a good reason to override the platform recommended 
> packing, which 
> can cause errors such as "Internal compiler error in 
> 'move_by_pieces'"?
> HTH,
> --Eljay
> 
> 
begin:vcard
n:Jia;Yu
fn:Jia Yu
version:2.1
email;internet:jiayu@xxxxxxxxxx
end:vcard


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux