Preparing FPC 3.2.4, point out road blocks now

[JuhaManninen]

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

... and FPC 3.2.2 was released almost 3 years ago. This is annoying.

[Wallaby]

It's best to use fpcupdeluxe and regularly update to FPC fixes and Lazarus fixes.

This way you could get the latest official releases plus any fixes made to them after the release.

I am using 3.2.3 (aka 3.2 + fixes) and Lazarus 3.0 + fixes with great success. No need to wait for  an official release, which seems to have been abandoned.

[zeljko]

I don't think it's abandoned, but yes, it need to be released soon, too much time is passed since last release.

[440bx]

There is probably a good reason why it hasn't been released after that much time and, it's likely (mostly) a technical reason.

It would be nice if one of the developers would mention what is holding the release back.

[wfbhappy]

fast

[ocloma]

maybe it fell into an infinite loop...

[Thaddy]

I don't think it's abandoned, but yes, it need to be released soon, too much time is passed since last release.

1. that can be taken as an offence by the core team (it also expresses ignorance)
2. normal users want a stable environment
3. there is a fixes branch if you need a point release approximation.
4. the amount of changes and new features in trunk does not warrant a full release yet, and that will probably take even more time.
5. you obviously have no experience with professional release management. The core team has.....and delivers every release.
6. scratch out time from your vocabulary. It is done when it is done.
7. i think a  is warranted.

i also want to add a <sigh> to such folly.

[marcov]

The last time I heard, an issue with arm-linux linking,  some ABI or other  binary format identifier was the problem. There are not that many status updates on core.

[Thaddy]

I know. But sometimes users still don't get the importance of mitigating such an issue first.

[marcov]

I know. But sometimes users still don't get the importance of mitigating such an issue first.

I'm sure that as a Lazarus core developer, Zeljan knows the issues :-)

[Thaddy]

Then why he shows impatience, Marco? An issue with ARM is by now a blocking issue, since it is such an important platform by now.
BTW I had to manage such things in my working carreer, so I understand the sentiments...
you know that. I respect everyone in the core team.

[BSaidus]

The last time I heard, an issue with arm-linux linking,  some ABI or other  binary format identifier was the problem. There are not that many status updates on core.

Hello, I have an issue with freebsd-aarch64 OS. After compiling a simple program with fpc ( ex: simple helloworld console ) I must use command :
   

Code: [Select]

   brandelf -t freebsd project1
   to execute the program.
Can FPC team do this just after compiling ?

Thank you.

[marcov]

The last time I heard, an issue with arm-linux linking,  some ABI or other  binary format identifier was the problem. There are not that many status updates on core.

Hello, I have an issue with freebsd-aarch64 OS. After compiling a simple program with fpc ( ex: simple helloworld console

Afaik the Aarch64 port was done by one Mikaël Urankar. I don't know anything about it, and don't have the HW. For LLVM based FreeBSDs, it might help to change the elf ident like in the i386/x64 one

The commit bugreport (https://gitlab.com/freepascal.org/fpc/source/-/issues/38441 ) seems to contain some patches by Pierre with the request to validate.

Please do any work on top of the fixes branch or trunk.