Here is what I would do in your shoes. I would take the failing compilation command, i.e.,
Ok, If I was you I would:
g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I../src -D_SYS_REG_H -I/opt/local/include \ -g -O2 -frounding-math -W -Wall -MT C_Polyhedron.lo -MD -MP \ -MF .deps/C_Polyhedron.Tpo -c C_Polyhedron.cc -fPIC -DPIC -o .libs/C_Polyhedron.o
I would replace -c with -E and erase -g, -O2, ... and anything after C_Polyhedron.cc, redirecting the output to a file.
Then I get:
g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I../src -D_SYS_REG_H -I/opt/local/include -frounding-math -W -Wall -MT C_Polyhedron.lo -MD -MP -MF .deps/C_Polyhedron.Tpo -E C_Polyhedron.cc | grep CS
static const flags_t CS_PENDING = 1U << 7; return test_any(CS_PENDING); reset(CS_PENDING); set(CS_PENDING); static const flags_t CS_PENDING = 1U << 7; return test_any(CS_PENDING); reset(CS_PENDING); set(CS_PENDING);
Then I would try to identify the header that is defining the macro CS.
statit const ...
appears in:
# 70 "Grid_Status.idefs.hh"
and
# 85 "Ph_Status.idefs.hh"
So then I as you would do the following:
...
Thanks, alan
Reading all your files is exactly what I had in mind :-)
Yea, it's just that every time I show people my plans for mind control they start to laugh and then they call me stupid and it's really starting to get on my nerves. That's all. :-)