Forum > macOS / Mac OS X
Installation of Lazarus/Free Pascal
TRon:
@alanyoung:
That fancy cleaning tools do not work as expected is known... it was not really the question :)
I wanted to try and obtain more information on which steps you did to install.
But never-mind that as it simply takes up too much time. Please consider removing again and reinstall with using FPCUpDeluxe. If you do then make sure to install into a directory where you have enough access rights.
There is a wiki-page on how to install lazarus on macos from source, including how to configure/setup, common errors and a link to faq regarding issues.
The errors you presented I have never seen before (I can honestly say that I have done a lot of stupid things with configuring and installing) but for sure there is something gone horribly wrong with either the installation or the configuration (or both) with your current FPC and Lazarus. At first glance and if I would have to guess then it looks like you have a fpc.cfg that includes paths to your Lazarus units.
alanyoung:
I completely rebuilt my MacBook (including reformatting the hard drive). OS is Ventura 13.6.4
I then download the following:
fpc-3.2.2.intelarm64-macosx.dmg
fpc-src-3.2.2-20210709-macosx.dmg
Lazarus-3.2-macosx-x86_64.pkg
I installed them in the same order. No errors were reported. When Lazarus is opened for the first there is confirmation that all is OK. The sample program complies without any issue. Attempting to add a component such as a TLabel and recompiling gives an error as the TLabel is Not added to the unit.pas file. In addition if (as before) I select Project->Project Options->Test I still get the error that there is a .ppu file older than the compiler. Selecting the option 'Ignore 'i then get the errors listed before about duplicate files.
Given all the above, I wonder just what the solution is to get a functioning error-free installation of Lazarus pascal on macOS?
TRon:
--- Quote from: alanyoung on March 06, 2024, 02:16:49 pm ---Given all the above, I wonder just what the solution is to get a functioning error-free installation of Lazarus pascal on macOS?
--- End quote ---
As written in a previous post by me: FPCUpDeluxe. That should be able to provide you with the quickest solution.
The other route is diving into this issue but in case you are then expecting help from my hand you would have to be my eyes and ears because a) I do not have the hardware to test on and b) know nothing about macos. (besides being longwinded that would be a tiresome/long-dreaded path). The issue is that I am not familiar with the errors that you presented nor am I able to find anything remotely alike. Also the MacOS known issues and faq about installation related issues (both from the wiki) do not mention anything that seem to resemble your situation.
I intended to try and see what is inside those pesky dmg and pkg files but that already seem to be a difficult task to do on/for Linux.
You can hopefully help yourself a little as well by trying to compile something simple (if possible) with the compiler option -va enabled and analyze or post the (complete) log that it produces. It produces a log that tells whatever the compiler is trying to do during compilation.
alanyoung:
After several cycles of removing Lazarus/pascal and reinstalling as previously described, I now have an installation the appears to 'work'. 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..
As you suggested I set the complier option to -va enabled, but I have been unable to locate the log file (excuse my ignorance).
TRon:
--- Quote from: alanyoung on March 08, 2024, 06:54:51 pm ---As you suggested I set the complier option to -va enabled, but I have been unable to locate the log file (excuse my ignorance).
--- End quote ---
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 ?
--- Quote from: alanyoung on March 08, 2024, 06:54:51 pm ---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..
--- End quote ---
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.
Navigation
[0] Message Index
[*] Previous page