@mischi: With your commands, the following warnings don't get logged:
ld: warning: object file (/opt/local/libexec/fpc/lib/fpc/3.2.0/units/x86_64-darwin/rtl/sysinit.o) was built for newer macOS version (10.15) than being linked (10.9)
ld: warning: object file (/opt/local/libexec/fpc/lib/fpc/3.2.0/units/x86_64-darwin/rtl/system.o) was built for newer macOS version (10.15) than being linked (10.9)
Then, here are log files from the two attempts. I notice there are a lot of "not found"s in the second file. Don't know how to fix them, though.
TIA,
Mark
The warnings are nothing to worry about. The logs are fine, too. No need to fix anything, since at the end of each search with lots of "not found", the compiler finds an appropriate file. You may not have expected it, but it always looks like this and is totally fine. You have a perfectly working fpc 64bit compiler. The product should be a working command line program. Did you try it?
This is the line, which makes me worry, in particular for a completely new project:
WARNING: include search path does not exist: /Users/markwallace/fpcobj/lib/x86_64-darwin
To the best of my knowledge, this is not set in any default config file. It should be fixed by deleting any lazarus and fpc config file, but much care is needed not to miss the one with this setting. Therefore, i suggest to spend some more time in a more systematic search to find this culprit.
I see two routes how to fix this. The first is to directly search for the config file with this path with grep. The second is to produce a verbose log of building the project with lazarus and check the log file.
1)
I expect the path "/Users/markwallace/fpcobj/lib" has been set in some config files with "-Fu~/fpcobj/lib". To the best of my knowledge, fpcobj is not
used by fpc or lazarus by default. Just for my curiosity: Do you remember, whether you have set this path during any of your installations? Whatever. This is route number 1:
You could try to find the file with grep in your home directory.
grep -r fpcobj .*
or any settings of unit directories for fpc
grep -r '-Fu' .*
You might also do the grep in more general directories, such as /etc, /opt/local/etc
Then delete the lines with fpcobj in these files with a text editor.
2)
Although, the problem is not found yet, at least it is clear, that it is caused somewhere up the tool chain, i suspect project options in lazarus. Therefore, another route is with a new project. Check the project options. To be sure explicitly set the OS target to Darwin, the CPU target to x86_64 and the widget set to cocoa. You might also increase the verbosity (I hope that this is the correct re-translation of my German menus) by setting -vt. In case the output becomes impossible to handle you might use the command line command
lazbuild YOUR_NEW_PROJECT.lpi
and redirect the output to a log file. Again, the log file can be very long and the task is to find the name and path of the config file, where the path from above is set.
Michael.