Hey Davo,
Gus, like I said, in verbose mode, you should see (a whole lot of stuff including) the compiler parsing the config file and then searching, in what it thinks is the right place for eg units. If you have replaceable parameters in the cfg file you will see it looking in the place it derived by putting that parameter into the config line in question. Here is an example (64bit linux of course)
dbannon@dell:~/Pascal/CLI$ fpc -va tsetdemo.pas > dump.txt
dbannon@dell:~/Pascal/CLI$ ls -l dump.txt
-rw-r--r-- 1 dbannon dbannon 462519 Jul 16 10:30 dump.txt
dbannon@dell:~/Pascal/CLI$
Some interesting lines from dump.txt , note number on left is a line number added by my view utility, you may not see that -
42 [0.004] Configfile search: /home/dbannon/.fpc.cfg
43 [0.004] Reading options from file /home/dbannon/.fpc.cfg
44 [0.004] Hint: Start of reading config file /home/dbannon/.fpc.cfg
342 [0.027] Using unit path: /home/dbannon/fpc-3.2.4/lib/fpc/3.2.4/units/x86_64-linux/rtl/
743 [0.035] Unitsearch: /home/dbannon/fpc-3.2.4/lib/fpc/3.2.4/units/x86_64-linux/httpd22/system.ppu
752 [0.035] Unitsearch: /home/dbannon/fpc-3.2.4/lib/fpc/3.2.4/units/x86_64-linux/rtl/system.ppu
753 [0.035] Searching file /home/dbannon/fpc-3.2.4/lib/fpc/3.2.4/units/x86_64-linux/rtl/system.ppu... found
OH CRAP!!!
I was doing:
fpc -va dummy.pas | grep -i 'fpctarget'
It never occurred to me, to look for the resolved paths DOH !!!!!!!!!! :hard-facepalm: :hard-table-headbut:
Now I have to redo all my effing tests!!!
Many thanks for the hint, will test and come back to apologise for wasting so many people's time due to my own very high stoooooooopidity !!!!!!!!!
Jesus Gus!!! Get a bloody grip !!!

Cheers,
Gus