Andris Pavenis wrote:
I think this renaming is understandable to avoid having executable with the same name (cpp.$exeext) in 2 directories. I have seen related trouble with DJGPP port of gcc-2.95.X (before 2.95.3) and avoided it by leaving $prefix/bin/cpp.exe out of gcc295Xb.zip.
Yes, this seems a reasonable change (I've also run into problems because of the different cpp's before), and as far as I understood Maurice, that's rather easily fixed in GPC, but the serious problems seem unrelated...
Has anybody tried to compile gpc with gcc2953 on a linux machine?
Yes. I tried. I run into some trouble when GPC_FOR_TARGET was not passed from top level make to one in gcc subdirectory as ./xgpc -B./ is wring for Canadian crosses of course. As result make fails in gcc/p/rts. I added definition of GPC_FOR_TARGET in t op level makefile and passing it make in subdirectories.
That's strange since currently GPC doesn't use GPC_FOR_TARGET at all. Make-lang.in, l. 140-141:
RTS_COMPILERS = CC="`echo $(GCC_FOR_TARGET)' ' | $(ADD_RTS_PARENT_DIR)`" \ PC="`echo $(GPC_FOR_TARGET)' ' | $(ADD_RTS_PARENT_DIR)`"
I think we did this exaclty because of the problem you described.
Do you perhaps have an older GPC version which does not have this?
Frank