g++ 3.3.5 (1:3.3.5-13) debian package.
In order to clean up my installation machine I'm thinking of burning an unstable DVD and dist-upgrading the thing.
Is "unstable" really unstable, or really just full of bugs?
I seem to have more bugs/issues with a sarge/unstable mix then perhaps I would have with a 100% unstable machine...
what do you think?
I can't go back to sarge since I needed libs and packages not available in sarge.. I can't remember what offhand...
.b.
IOhannes m zmoelnig wrote:
B. Bogart wrote:
Hi all,
I'm trying to recompile Gem with v4l2 stuff, but the compile bails with this:
g++ -c -fPIC -g -O2 -freg-struct-return -O3 -fno-builtin -falign-loops=16 -funroll-loops -ffast-math -mmmx -I/usr/X11R6/include -I/usr/include/ffmpeg -I/usr/include/quicktime -I/usr/include/avifile-0.7 -I/usr/include/freetype2 -I.. -I/usr/include/FTGL -I/usr/include/freetype2 GemGLUtil.cpp -o GemGLUtil.o In file included from GemGLUtil.cpp:18: GemGLUtil.h:25: error: declaration of C function `int getGLdefine(t_symbol*)' conflicts with GemGLUtil.h:24: error: previous declaration `int getGLdefine(char*)' here GemGLUtil.h:26: error: declaration of C function `int getGLdefine(t_atom*)' conflicts with GemGLUtil.h:25: error: previous declaration `int getGLdefine(t_symbol*)' here GemBase.cpp:138: error: parse error at end of input make[1]: *** [GemBase.o] Error 1 make[1]: *** Waiting for unfinished jobs....
hmm, very interesting. which version of g++ are you using? (but it tested it with g++2.95 and g++-4.0.3 and it works fine)
the technique used is function overloading, and this is just perfect C++. why does your compiler think it is ordinary C??
mf.asd.r IOhannes