As you suggested I set the complier option to -va enabled, but I have been unable to locate the log file (excuse my ignorance).
My bad. I should have been more explicit when I wrote that.
It is not a file but output from the compiler when you compile/build a project.
Assuming that you use Lazarus, they appear in the message window (the same windows where it say if compilation succeeded or failed).
That there are more message listed in that window might not be so obvious as by default Lazarus filters out a lot of those messages.
For the complete list you can either copy them or save them by clicking on the right mouse button in that message window, then selecting either save or copy, selecting the menu item "copy all/original message to the clipboard" or "save all/original message to file".
Then either save the file or paste the clipboard contents to a text editor so that you are able to read them for further review.
Hopefully that makes it more clear ?
I still get the error when I select Projects->Project Options-> Test, but a simple program with a couple of basic components behaves as expected..
The latter is the most important the former however ....
... I never quite understood the functionality of that test button. The process that is executed when you press that button confuses all sort of things, complaining about things that are obvious, digging up very old temporary files, informing about ppu file-dates that do not match that of the compiler (who cares, especially when looking at the wrong directories ?) to finally end up in a failed empty project build attempt. And I am sure I forgot to mention a lot of other stuff that happens when you press that button.
Perhaps it is beneficial to get acquainted with what that button actually does or is trying to tell when it presents all the information but honestly I personally could not care less especially because it is clear that the process that is performed gets confused by my (custom) compiler setup.