Click to See Complete Forum and Search --> : compile newbie OR gcc and me


andre
08-04-2003, 09:03 PM
........
c++ -I../stlport -Wall -W -Wno-sign-compare -Wno-unused -Wno-uninitialized -ftemplate-depth-32 -O2 complex.cpp -c -o obj/GCC/Release/complex.o
In file included from ../stlport/complex:40,
from complex.cpp:21:
../stlport/wrap_std/complex:16:39: ../g++-include/complex: No such file or directory
......
then follows hundreds of complex.cpp:36: parse error before...... and complex.cpp:95: `__z1_r' was not declared in this scope, for example

I'm trying to install tripwire and I have all the asked for tools
"gcc version 2.95.2 or better"

so I'm trying to track down the error above "no such file or directory. Can anyone break down that line for me? is it not finding the complex:16:39 ? (what is that :16:39 part anywhay?) or is it missing "g++-include/complex" ???

tips anyone?

serz
08-04-2003, 10:08 PM
What distro and version are you using? It seems that you have an old version of gcc, and you need at least the 2.95 version.

andre
08-04-2003, 10:50 PM
RedHat 9
gcc (GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
g++ (GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
c++ (GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5)

I'm realy not sure how to troubleshoot these compilations (newbie)

but the first error i spoted :
../stlport/wrap_std/complex:16:39: ../g++-include/complex: No such file or directory

"g++-include " doesn't look right does it, but it hapense with tripwire release 2.3.0-50 and 2.3.1-2

fatTrav
08-06-2003, 11:37 AM
if you are compiling a program to install...
since you are using rh9, i'd suggest trying out the program checkinstall. what it does is when you issue the make command to compile (and then via the make install command) and install a src package program it will instead make an rpm for your machine based on a few params you give checkinstall. then you get to install things via the easier rpm way with all the benefits of the src and rpm methods. google or freshmeat for that app and give it a shot. it might not answer your question, but it may provide a way around future gcc problems/issues.
else, if you are not...then disregard this post.