Then when I check the supposed cross-compiler it only supports linux target , which I did not ask for and does not support win64 target which I specified.-iTO doesn't list all targets, check with -i instead. Every single ppcXXX supports all OSes on that architecture. Remember this is only the compiler, rtl and packages are on the same requirement level but separated.
I have found one issue, the Makefile is installing the 64 bit build ( Fed 26 on x86_64) files into /usr/lib not /usr/lib64 as with the distro 3.0.2 , so this does not match the paths in /etc/fpc/cfg.The distro packaged one is different then. If you build from source, it will always installs to /usr/lib. FPC directory structure is designed smart enough to install multiple cross compiler toolchain (including host one).
3.0.2 can build my hello.pas , 3.1.1 can not , complaining about unit system .Call fpc with proper -T and -P (or only -T if you execute ppcXXX).
Do you know whether the "x64" covers all 64 CPU for the fpc compiler ? I'm guessing it does, but not sure.Yes, it does (back to my first answer).
My problem is now with lazarus which seems to be implicitly calling. fpc 3.0.2 with the correct options but there is no account of $fpcversionDid you symlink the ppcXXX to /usr/bin (ls -l to double check)? Essentially that's the way you change compiler version, fpc will call corresponding ppcXXX for given -P in directory where it resides.
...
do you know how I can configure the project options to include fpc version and reach the right libs?
when I hit the test btn in project options dlg I get this:Can you still build thr project? If yes, then that test button handler code might need fixes. AFAIK, those messages don't come from the compiler.