[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
more on gcc 2.95 C++ problem
- Date: Wed, 4 Aug 1999 15:47:56 -0500 (CDT)
- From: joel at OARcorp.com (joel at OARcorp.com)
- Subject: more on gcc 2.95 C++ problem
Hi,
I have not investigated this much but have found a hint that may trip
someone else into figuring this one out. :)
If you take the preprocessed output of rtemsEvent.cc on the targets that
fail and compile it by hand, you can reproduce the error. Save this
output in a new file. Remove EVERY line that starts with a "#" and then
it compiles without problems. I can spot nothing wrong with the cpp
output that would cause this but thought this might give someone else a
hint who knew more C++.
The sequence I have that reproduces this is in the attached file. I did
this on the m68k-rtemself/gen68360 configuration but many others have the
same C++ problem.
cd ...librtems++ in a build directory
run the script
I hope this gives someone a hint. :)
I hate to bundle up a bing one like and send it to the egcs bug list
before we narrow the problem down more.
--joel
-------------- next part --------------
/usr2/tools_install/gcc-2.95-binutils-2.9.1-newlib-1.8.1-0899/m68k-rtemself/bin/m68k-rtemself-g++ -B../../../../../gen68360/lib/ -specs bsp_specs -qrtems -mcpu32 -I../../../../../gen68360/lib/include/networking -g -Wall -ansi -fasm -E -o j1.cc ../../../../../../rtems-current/c/src/lib/librtems++/rtemsEvent.cc
grep -v "^#" j1.cc >j2.cc
/usr2/tools_install/gcc-2.95-binutils-2.9.1-newlib-1.8.1-0899/m68k-rtemself/bin/m68k-rtemself-g++ -c j1.cc
/usr2/tools_install/gcc-2.95-binutils-2.9.1-newlib-1.8.1-0899/m68k-rtemself/bin/m68k-rtemself-g++ -c j2.cc