almost perfectly as weems to happen with linux, i post my problem, late at night, go to bed and lay down. while going to sleep more possibilities are revealed to me by the big penguin in the sky....

"maybe g++ is different to cpp ... ? and maybe there is seperate source tarball release for g++ ...? "

well what do you know... there, right besides the gcc-core tar.gz is a gcc-g++ tar.gz, ... oh the joy


-----------------------------------

ok, see ive got my kernel compiled with 2.95.3 arm-linux-gcc and installed it to my z,

the app (bestcrypt) that im trying to compile requires same version binary as what built the kernel,

so i did up gcc 2.95.3 (in /usr/local) to be default over standard 3.4.5 (in /opt) (pdaxrom beta1)

but ... 2.95.3 comes with cpp and no g++

my makefile has CPP=g++

and if i just run it it uses the g++ from 3.4.5 and the gcc from 2.85.3, ending up with error containing:

... uses FPA instructions, whereas bctool does not ...
... uses hardware FP, whereas bctool uses software FP ...
... failed to merge ... target specific data of file bctool.o ...

and dies.

so i thought i try symlinking /usr/local/cpp > /usr/local/g++ instead of changing all the makefile's to CPP=cpp, but it turns out cpp cat handle the option -c which is passed to it by the makefiles:

cpp: "-c" is not a valid option to the preprocessor

even though -c is mentioned in --help : "-c Compile and assemble, but do not link"
but i dont think that means much : http://gcc.gnu.org/ml/gcc-bugs/2001-07/msg00703.html

so i figure my options now are to either make up a arm-linux-gcc 3.4.5 or prefereably something else someone may suggest hopefully unsure.gif

the funny thing is on the the bestcrypt website (jetico) it recommend gcc 2.91 ? would that have g++ being earlier ?? and even if so, id still need an older arm-linux-gcc ...

perhaps someone can point out a newer arm-linux-gcc allready built that would run on collie...

umph...