FPC 3.3.1 release date and MacOS Silicon installer

[Enos68]

Hi,

the current install package on the Sourceforge.net site is not able to compile anything on MacOS silicon machine. The linker fails with an error message: -macosx_min_version renamed to -macos_min_version. Latest FPC install package is 3.2.2 on Sourceforge.net.

Even if I am downloading any other FPC versions eg.: 3.3.1 the source cannot be compiled, of course as the linker bringing up the failure for that too.

I have tried the fpcupdeluxe application, but it fails with different errors on macos at least. So cannot get a working set of app.

I could manage to get to a point, where the 3.3.1 version was manually setup at the original location of the 3.2.2 version, but it created another issue, by not having compatible ppu-s for the compiler.

As the 3.2.2 FPC is already 4 years old, what is the planned date of releasing the 3.3.1 in an official downloadable package?

Thanks

[TRon]

Hi Enos68 and welcome to the forums,

the current install package on the Sourceforge.net site is not able to compile anything on MacOS silicon machine. The linker fails with an error message: -macosx_min_version renamed to -macos_min_version. Latest FPC install package is 3.2.2 on Sourceforge.net.

There is a MacOS dedicated subforum here were such issues (and their workarounds) have passed.

As the 3.2.2 FPC is already 4 years old, what is the planned date of releasing the 3.3.1 in an official downloadable package?

3.3.1 will never be released as it is literally an (double) odd release number and only even numbers get released (which will be 3.2.4 and a release candidate for that version is already published. Not that this release candidate fixes any of the current macos related issues though). 3.3.1 is trunk and will remain that way indefinitely until another new release is made.

For instance, the fixes release for 3.2.2 will be numbered 3.2.3 (and can be checked out and build from source).

Quickest way to go about is to pick the most unique parts of the error message and do a forum search for those parts in order to get yourself informed about the thread or threads that have this issue mentioned/solved or have mentioned a workaround.

Also there is a dedicated wiki page here for Macos installation where most issues are mentioned.

[Enos68]

Hi Tron,

thanks for the feedback. I have checked the forum before and I have found a thread were it was discussed, but could not solve the problem for me. I also check the Wiki page you proposed.

[TRon]

Hi Enos,

Firstly, I have to correct myself. Depending on the exact error sequence/results the issue /is/ actually fixed in trunk, see #40415.

Secondly, it helps to literally have the error message, it seem to be "-macosx_version_min has been renamed to -macos_version_min" not "-macosx_min_version renamed to -macos_min_version". Searching for the latter only reveals this thread (which isn't particularly helpful).

One of the workarounds seem to have been mentioned here but it is probably best/better to use trunk. Note that there are several issues related to macos and might perhaps been able to throw you off-guard. Also note that while this particular issues seem to have been solved the actual message complaining about version name being changed can still be present (but reports suggest that it does not harm the compilation itself or the results from such compilation).

[Martin_fr]

The next release will be FPC 3.2.4  (which is not based on 3.3.1 / and as far as I know does not contain the fixes you need / but I don't know for sure which versions have those fixes).

The exact date for 3.2.4 is not yet known. It's been in preparation for a long time. It is **hoped** to be soon.

My understanding (I am not authoritative on the FPC release schedule), is that after that release decisions on the next release will be made (or a discussion on them started internally within the team).
That next (after 3.2.4) release is then likely 3.4.0 which will be based on 3.3.1.

After 3.4.0 the current 3.3.1 will be renamed to 3.5.1 afaik. (the double odd number is always the "work in progress" indicator)

[Enos68]

I have tried to download the trunk version, which is 3.3.1 and on GITHUB this problem seems to be solved, but I cannot find the way, how to compile the compiler from source on Silicon Mac. Is there a guide for it, how to compile it and install the be able to use with Lazarus?

[dbannon]

Hm, Enos68, that sounds like the classic chicken and the egg argument !

Firstly, are you sure the message you get is an actual error that prevents the build proceeding ?  There 'was' a message like this that was just a warning, it allowed the build to finish. But very possible this is a new feature introduced by Apple.

If the latter, only thing I can suggest is to build 3.3.1 on an earlier system. If you have access to a Silicon box running an earlier OS, build it there and then copy it all across.  I strongly recommend you do NOT install 3.3.1 over the top of 3.2.2, build it and then install into a directory in your own home directory and set PATH accordingly. That will also make bundling it up to move between machines easier too. Please keep your 3.2.2 install intact.

If you don't have such an older system, harder problem !   I have an Intel based Monterrey box, I could probably cross compile it for you from there, will take a bit of messing around but I reckon we could manage it it between us.

Davo

[Enos68]

Hi,

that is the only linker error message, so that must be the reason. This is confirmed in many ways as well as the GITHUB commit description and code snippet is showing the update in the code changed.

https://gitlab.com/freepascal.org/fpc/source/-/commit/fd83bb10d4b3c1bc30cf3a72cd419882b63b561a

My actual problem is not that the source is not compiled, but that the make script is not working just as simple as it used to. I am not an expert of compiling things from terminal, so I am looking for an explanation of how can I get the source compiled.

Anyway, thanks for the suggestion to try it in a virtual box with an older XCode tool. I check that. I guess, if that might work, I would still need to find out how can I get the compiled FPC version to replace an installed 3.2.2.

Any idea about it? Thanks!

[Thaddy]

The make script simply works. There have been minor changes but:
make clean all install PREFIX=/usr PP=/path/to/3.2.2/ppcx64
will simply work.

[Enos68]

Ok, I could get it run. Compile was done, linking was done, but at install I have got this.

sudo base.build-stamp.aarch64-darwin
/Library/Developer/CommandLineTools/usr/bin/make installbase FPC=/Users/endre/fpc/compiler/ppca64 ZIPDESTDIR=/Users/endre/fpc FPCMAKE=/Users/endre/fpc/utils/fpcm/bin/aarch64-darwin/fpcmake
/usr/bin/install -m 755 -d /usr/lib/fpc/3.3.1
sudo: base.build-stamp.aarch64-darwin: command not found
/usr/bin/install -m 755 -d /usr/local/lib/fpc/3.3.1
install: mkdir /usr/local/lib/fpc/3.3.1: Permission denied
make: *** [installbase] Error 71
install: mkdir /usr/lib/fpc: Operation not permitted

Even run the make script with sudo, or just the this failed line as above, did not work.

[dbannon]

.....
Anyway, thanks for the suggestion to try it in a virtual box with an older XCode tool. I check that. I guess, if that might work, I would still need to find out how can I get the compiled FPC version to replace an installed 3.2.2.

Any idea about it? Thanks!

OK, a VM could be a good solution. First, do NOT replace the original 3.2.2.  You can have as many compiled versions of FPC as you like, you can use the (operating system) PATH setting, Lazarus settings and. perhaps, the fpc.cfg file to determine which one is being used.

So, in the VM, build it first, then, when it comes to installing, install into a clean directory in your home directory. It does not have to be in any particular spot.  Then, tar up that directory, copy to your real machine and untar into the (eg) same location, inside your own home directory.

If you are using a fpc.cfg (probably in your home directory as .fpc.cfg) from fpc3.2.2 you will have to make a few tweaks. But your trunk install will have made a new fpc.cfg for you and it has a substantially better use of replaceable parameters, back up the old one and replace it with the trunk version.

If you are only using FPC, its from the command line, set PATH to look in "$YOUR_FPC_Dir/bin" before anywhere else.

If you are using lazarus, you can point its compiler (Tools->Options->Environment->Files Compiler Executable and FC Source Directory to the appropriate place.

(No Davo, on the Mac, the Options has been moved to some "more Mac friendly menu", I am sure you will find it.)

Yep, it does involve some fiddling around but it sounds to me that you can handle it and you will feel heaps better knowing you, yourself, are in charge of your system !  Its Unix after all.

Davo