Preparing FPC 3.2.4, point out road blocks now

[marcov]

Аccidentally discovered that FPC 3.2.2(and 3.3.1)-win64 lacks compiled units for the GMP package. Are there any reasons for this?

Headers are generally only enabled for targets that they were confirmed to fully work.

[avk]

Thank you.

[BeniBela]

This bug affects 3.2.3: https://gitlab.com/freepascal.org/fpc/source/-/issues/35651

[trev]

Mountain Lion 10.8.5 (Intel) fails to build FPC 3.2 Fixes. The cause is the codesign command:

   /usr/bin/codesign --remove-signature ppc3.tmp 
  ppc3.tmp: unsupported type or version of signature
  make[2]: *** [cycle] Error 1
  make[1]: *** [compiler_cycle] Error 2
  make: *** [build-stamp.x86_64-darwin] Error 2

I could not remove the signature either, but I could re-sign it with:

  /usr/bin/codesign --force --sign - ppc3.tmp

although the Makefile only wants to remove a signature and not re-sign the executables. It turns out that the codesign utility for Mountain Lion lacks the --remove-signature option.

Code: Text  [Select][+][-]

1. trev@dynamic37 [/Users/trev/fpc_fixes32/compiler] $ codesign
2. Usage: codesign -s identity [-fv*] [-o flags] [-r reqs] [-i ident] path ... # sign
3.        codesign -v [-v*] [-R testreq] path|pid ... # verify
4.        codesign -d [options] path ... # display contents
5.        codesign -h pid ... # display hosting paths

[Updated]
 The same issue also applies to OS X Maevricks, OS X Yosemite, OS X El Capitan and macOS Sierra.

[Updated2]
My workaround was to create a fake codesign and ensure it was found first in the path.

Jonas suggested that you can provide a custom codesign command via the CODESIGN=xxx make parameter. You could use CODESIGN=/usr/bin/true to work around it.

[BeniBela]

Big road blocks for ARM:

https://gitlab.com/freepascal.org/fpc/source/-/issues/39490

https://gitlab.com/freepascal.org/fpc/source/-/issues/39492

[Zvoni]

Any news on this issue?: https://gitlab.com/freepascal.org/fpc/source/-/issues/35248

[dbannon]

https://forum.lazarus.freepascal.org/index.php/topic,58888.msg439013.html (accommodate forthcoming changes to glibc)

and, probably wishful thinking -

https://gitlab.com/freepascal.org/fpc/source/-/issues/39451  (hardening on PPC64le)

.... sorry !

Davo

[PascalDragon]

Any news on this issue?: https://gitlab.com/freepascal.org/fpc/source/-/issues/35248

Not even fixed in main, so definitely won't be fixed in 3.2.4.

[jonnybravo]

Where can I see what's in main?  I am interested in what could be coming our way!

[Bi0T1N]

Where can I see what's in main?  I am interested in what could be coming our way!

You can see new features here and bug fixes/changes here. However, this is not updated for every single change so you might also need to check the commit history.

[jonnybravo]

Thank you, that's great!! 

[BSaidus]

Hi, people,
A question that any one want to be asked
When can we see the 3.2.4 fpc release ??
Thanks for patience.

[Thaddy]

Note that, contrary to what was mentioned above, not all new features of main/trunk -  if any - will be in the point/bugfix release 3.2.4 although some things may have been back-ported.
3.2.4 is basically a release based on 3.2.2-fixes a.k.a. 3.2.3. Main/trunk has release target 3.4.0 ( it is suggested maybe even jumping to 4.0.0 because of the many important new compiler features ) and is expected to be released somewhere in the future, without a current release date. Think a year or more. I would be very surprised if  a major release based on main/trunk is released in 2023....
Just so that you are not confused or disappointed when some new features that are in main/trunk are missing in 3.2.4.

[DaveR_uk]

Currently we are in the process of preparing the 3.2.4 release, mainly by merging stuff from main into fixes. If there are any problems with 3.2.2 prevent you from using 3.2.2, it is now the time to point this out , i.e. if you are stuck with 3.0.4 for some reasons.

That was just over 15 months ago.  Is an FPC 3.2.x bug-fix production release likely any time soon please? Or is FPC going to eventually jump direct to a  major new release?  TWhe recent Lazarus 3.2 is understandably still built against FPC 3.2.2 as the latest stable production release.   An update on possible timescales would be much appreciated.

Where did I get 15 months from ???

[ccrause]

Currently we are in the process of preparing the 3.2.4 release, mainly by merging stuff from main into fixes. If there are any problems with 3.2.2 prevent you from using 3.2.2, it is now the time to point this out , i.e. if you are stuck with 3.0.4 for some reasons.

That was just over 15 months ago.  Is an FPC 3.2.x bug-fix production release likely any time soon please? Or is FPC going to eventually jump direct to a  major new release?  TWhe recent Lazarus 3.2 is understandably still built against FPC 3.2.2 as the latest stable production release.   An update on possible timescales would be much appreciated.

Where did I get 15 months from ???

Good question, it has been more than two years since the first post appeared.