Lazarus Cannot find "fpcres" (BUT CAN FROM TERMINAL)[SOLVED] lazarus / 33-macOS - Mac OS X ---------------------------------------------------------------------- kevin.black · 2019-01-14 00:19 Again, Apologies for what might seem trivial, but is a blocker for me: As you can see from my reply below, the problem was initially a crazy mis-match of 32 and 64 bit parts. I have finally sorted that. The issue NOW is that I get the fpcres error: Error: (9021) resource compiler "fpcres" not found, switching to external mode Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i Hint: (11030) Start of reading config file /etc/fpc.cfgHint: (11031) End of reading config file /etc/fpc.cfgFree Pascal Compiler version 3.0.4 [2017/11/26] for x86_64Copyright (c) 1993-2017 by Florian Klaempfl and others(1002) Target OS: Darwin for x86_64(3104) Compiling pDYLIBTestAPP.lpr(3104) Compiling udylibtestapp.pas/Users/kevin/Dropbox/Lazarus/DYLIB Test/udylibtestapp.pas(28,28) Hint: (5024) Parameter "Sender" not used/Users/kevin/Dropbox/Lazarus/DYLIB Test/udylibtestapp.pas(27,28) Hint: (5024) Parameter "Sender" not used/Users/kevin/Dropbox/Lazarus/DYLIB Test/udylibtestapp.pas(26,28) Hint: (5024) Parameter "Sender" not used(9001) Assembling (pipe) /Users/kevin/Dropbox/Lazarus/DYLIB Test/lib/x86_64-darwin/udylibtestapp.s(9001) Assembling (pipe) /Users/kevin/Dropbox/Lazarus/DYLIB Test/lib/x86_64-darwin/pDYLIBTestAPP.spDYLIBTestAPP.lpr(25) Error: (9021) resource compiler "fpcres" not found, switching to external modepDYLIBTestAPP.lpr(25) Fatal: (10026) There were 1 errors compiling module, stoppingFatal: (1018) Compilation aborted I've searched and searched etc and nothing. The fpcres binary is in /usr/local/bin (CONFIRMED) I can run fpcres from a Terminal windows from Anywhere on my VM (CONFIRMED) Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i Lindeman:DYLIB Test kevin$ fpcresfpcres - resource file converter, version 2.0 [2017/11/26], FPC 3.0.4Host platform: Darwin - x86_64Copyright (c) 2008 by Giulio Bernardi. The version seems correct, ie. Darwin - x86_x64 This would seem that there is no PATH issue? YET when I do a build I get the NOT FOUND error. So can anyone suggest WHY I'm getting the CANNOT FIND error and how to fix it PLEASE? Thanks Kevin ---------------------------------------------------------------------- kevin.black · 2019-01-14 22:22 The code is as above, BUT BUT BUT I think the issue to some extent was that there was a miss mash of 32bit/64bit compile options. It is (to a newbie at least) very confusing since, as near as I can figure out there are two places where you need to tell the system your are 64 bitting (sp). Tools>Options>Files you need the compiler to be ppcX64That option wasn't available in my install so I was using ppc386I 'Think' that was the cause of my issues in the original questionYou also need to (in Project>Options>Config and Target> set it to x86-x64None of the other options in that group work OK did that and finally the errors Stopped: ld: symbol(s) not found for architecture i386 An error occurred while linking Big clue with the i386, but that part of the message wasn't visible unless you copied ALL message data (another trap for young players) NOW however I am getting an error cannot find fpcres. I can confirm that fpcres is where it should be in /usr/local/bin. So again, how to I set the path so that fpcres can be found and my simple little application build? here is the complete message details: Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i Hint: (11030) Start of reading config file /etc/fpc.cfgHint: (11031) End of reading config file /etc/fpc.cfgFree Pascal Compiler version 3.0.4 [2017/11/26] for x86_64Copyright (c) 1993-2017 by Florian Klaempfl and others(1002) Target OS: Darwin for x86_64(3104) Compiling pDYLIBTestAPP.lpr(3104) Compiling udylibtestapp.pas/Users/kevin/Dropbox/Lazarus/DYLIB Test/udylibtestapp.pas(28,28) Hint: (5024) Parameter "Sender" not used/Users/kevin/Dropbox/Lazarus/DYLIB Test/udylibtestapp.pas(27,28) Hint: (5024) Parameter "Sender" not used/Users/kevin/Dropbox/Lazarus/DYLIB Test/udylibtestapp.pas(26,28) Hint: (5024) Parameter "Sender" not used(9001) Assembling (pipe) /Users/kevin/Dropbox/Lazarus/DYLIB Test/lib/x86_64-darwin/udylibtestapp.s(9001) Assembling (pipe) /Users/kevin/Dropbox/Lazarus/DYLIB Test/lib/x86_64-darwin/pDYLIBTestAPP.spDYLIBTestAPP.lpr(25) Error: (9021) resource compiler "fpcres" not found, switching to external modepDYLIBTestAPP.lpr(25) Fatal: (10026) There were 1 errors compiling module, stoppingFatal: (1018) Compilation aborted  So the real issue here MUST be that, since I can just type in "fpcres" at any terminal window and it is found and executed, there MUST be some sort of Link/hard coded path to fpcres that is incorrect. This is driving me bonkers, and I cannot proceed pas this point since I cannot compile / build anything. UPDATE: I reinstalled everything and same error, ie. cannot find fpcres. Now I tried to install a package and of course that blew up with the same error. Essentially the WHOLE Lazarus thing is now broke and I can go no further. Again, thanks in advanx...... ---------------------------------------------------------------------- Akira1364 · 2019-01-15 08:56 What does your "fpc.cfg" file look like? Try adding the following line to it, if it's not already there: Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i -FD/usr/local/bin The "-FD" flag specifies directories where FPC should look for external tool binaries (such as FPCRES.) ---------------------------------------------------------------------- kevin.black · 2019-01-15 10:56 @Akira1364, Thanks that’s a good point, I didn’t know what the -FD meant. I have, I think, just resolved at least that =issue. I had the folder for the 64 bit compiler pointing to /usr/.../.../ppcx64 (cannot remember exactly where out was pointing) and not to /usr/bin/ppcx64 (IIRC). Changing it to the correct? Folder now allows the DYLIB to compile. So clearly this issue is resolved.