error with gcc3.3.2

Aseem Rastogi aseem@india.tejasnetworks.com
Sat Sep 10 08:31:00 GMT 2005


try compiling with -E (and removing -c -o flags) flag to see only the 
preprocessed output. i think problem might be that there are two places 
from where iostream, ostream etc. classes are being included.


Chandra Sekhar M wrote:

>
> Hi
>
> When i tries to compile my code with gcc3.3.2, i am facing the 
> following problem ...
>
>
> /opt/sfw/gcc-3/bin/c++ -c -O2 -fschedule-insns2 -mtune=ultrasparc 
> -D_POSIX_PTHREAD_SEMANTICS -DSEA_SOLARIS -DOSVERSION=5.9 
> -DOWTOOLKIT_WARNING_DISABLED -DUSE_NON_CONST -fPIC -Wall -w 
> -ffor-scope -DSEA_PRODUCT_NAME=\""SEA"\" -DSEA_PRODUCT_NUMBER=\""CRL 
> 119 007"\" -DSEA_PRODUCT_REVISION=\"R17A\" 
> -DWIZARD_PRODUCT_REVISION=\""R15A"\" -DPRODUCT_NAME=\""RPGemu"\" 
> -DPRODUCT_NUMBER=\""CAA 209 2006"\" -DPRODUCT_REVISION=\""R7A"\" 
> -DBUILD_HOST_INFO=\""SunOS 5.9"\" -DINLINE -DBIG_ENDIAN -Wall 
> -Wno-non-virtual-dtor -fno-PIC -Wno-error 
> -I/vobs/tsp/sea/seaCore/osCore/include 
> -I/vobs/tsp/sea/seaCore/simCore/CLSIDs/include 
> -I/vobs/tsp/sea/seaCore/simCore/interfaces/src 
> -I/vobs/tsp/sea/seaCore/simCore/include 
> -I/vobs/tsp/sea/seaAxeCommon/clsids/include 
> -I/vobs/tsp/sea/seaAxeCommon/interfaces 
> -I/vobs/tsp/sea/seaAxeCommon/include 
> -I/vobs/tsp/sea/common/mph_client/c_lib 
> -I/vobs/tsp/sea/seaAxeCommon/sis -I/vobs/tsp/sea/seaAxeCommon/sist 
> -I/vobs/tsp/sea/common/compinfo 
> -I/vobs/tsp/sea/common/tools/tcltkincr/SOLARIS -I. 
> -I/proj/cse/tools/tools.h++_7.0.1_g++/rogue 
> -I/vobs/tsp/sea/seaApz/RPemu/tenux/solaris2/include 
> -I/vobs/tsp/sea/seaApz/RPemu/include -I. 
> -I/vobs/tsp/sea/seaApz/RPemu/mem -o 
> /vobs/tsp/sea/seaApz/RPemu/objectfiles/run/ApplicationBoard.o 
> ApplicationBoard.cc
> In file included from 
> /proj/cse/tools/tools.h++_7.0.1_g++/rogue/rw/defs.h:572,
>                 from 
> /proj/cse/tools/tools.h++_7.0.1_g++/rogue/rw/tooldefs.h:179,
>                 from 
> /proj/cse/tools/tools.h++_7.0.1_g++/rogue/rw/collect.h:207,
>                 from ApplicationBoard.hh:39,
>                 from ApplicationBoard.cc:35:
> /proj/cse/tools/tools.h++_7.0.1_g++/rogue/rw/generic.h:83: error: ISO C++
>   forbids declaration of `genericerror' with no type
> In file included from 
> /proj/cse/tools/tools.h++_7.0.1_g++/rogue/rw/rstream.h:105,
>                 from 
> /proj/cse/tools/tools.h++_7.0.1_g++/rogue/rw/vstream.h:160,
>                 from 
> /proj/cse/tools/tools.h++_7.0.1_g++/rogue/rw/stringid.h:103,
>                 from 
> /proj/cse/tools/tools.h++_7.0.1_g++/rogue/rw/collect.h:219,
>                 from ApplicationBoard.hh:39,
>                 from ApplicationBoard.cc:35:
> /opt/sfw/gcc-3/include/c++/3.3.2/backward/iostream.h:35: error: 
> `ostream' is
>   already declared in this scope
> /opt/sfw/gcc-3/include/c++/3.3.2/backward/iostream.h:35: error: using
>   declaration `ostream' introduced ambiguous type `ostream'
> /opt/sfw/gcc-3/include/c++/3.3.2/backward/iostream.h:36: error: 
> `istream' is
>   already declared in this scope
> /opt/sfw/gcc-3/include/c++/3.3.2/backward/iostream.h:36: error: using
>   declaration `istream' introduced ambiguous type `istream'
> /opt/sfw/gcc-3/include/c++/3.3.2/backward/iostream.h:37: error: `ios' is
>   already declared in this scope
> /opt/sfw/gcc-3/include/c++/3.3.2/backward/iostream.h:37: error: using
>   declaration `ios' introduced ambiguous type `ios'
>
> The Same thing when i compiling with  gcc2.8.1 its compiling well.
> please guide me what to do? What exactly the problem.
>
> Regards,
> Chandra Sekhar Marada
> Tata Consultancy Services
> Hyderabad
> INDIA
>
> Notice: The information contained in this e-mail message and/or 
> attachments to it may contain confidential or privileged 
> information.   If you are not the intended recipient, any 
> dissemination, use, review, distribution, printing or copying of the 
> information contained in this e-mail message and/or attachments to it 
> are strictly prohibited.   If you have received this communication in 
> error, please notify us by reply e-mail or telephone and immediately 
> and permanently delete the message and any attachments.  Thank you
>


-- 
The end is always good. If it's not good, it's not the end.





More information about the Gcc-help mailing list