Lazarus
Announcements => Free Pascal => Topic started by: marcov on May 21, 2021, 09:38:47 am
-
Hello,
Finally, the Free Pascal 3.2.2 release is available from our servers and from sourceforge.
Changes that may break backwards compatibility will be documented at:
http://wiki.freepascal.org/User_Changes_3.2.2
For an overview of what is new see the summary below
The website has been updated for the major targets and work is still being done for the rest.
All downloads are available at the main FTP server and sourceforge.
https://sourceforge.net/projects/freepascal/files/
ftp://ftp.freepascal.org/pub/fpc/dist/3.2.2/
Enjoy!
The Free Pascal Compiler Team
----------------------------------------------------------------------------
Free Pascal Compiler
Version 3.2.2
******************************************************************************
Free Pascal 3.2.2 is a minor release of the 3.2.x fixes branch. As such, it
contains mostly fixes of bugs discovered in the previous version, plus some
updates for included packages. In this case a new target was also backported
from trunk.
Please also see https://wiki.freepascal.org/User_Changes_3.2.2 for a list
of changes that may affect the behaviour of previously working code, and
how to cope with these changes.
The main highlights of this version:
Platforms:
- New platform: aarch64-darwin
- A new 32/64-bit combined installer for Windows.
Utilities:
- fpcres provides support for compiling resources from *.rc files
Packages:
- fcl-db extended with support for MySQL 8.0
- fcl-passrc updates
- pas2js updates
- fpdoc updates
- fcl-base includes new support for logging to StdOut and StdErr
- rtl-extra includes improvements for Sockets
-
Yeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeessssssssssssssssssssssss :D
Thank you for your hard work to make the world better .
-
Great work! :)
-
There seems to be quite a lot of builds missing, compared to 3.2.0 (most notably, for me, go32v2); will they be added later or will they be DIY? :-\
-
There seems to be quite a lot of builds missing, compared to 3.2.0 (most notably, for me, go32v2); will they be added later or will they be DIY? :-\
Minor target builds depend on time etc of the maintainer.
This might be the last release for FreeBSD, since the last supported (non LLVM) version goes out of support in September.
-
Minor target builds depend on time etc of the maintainer.
Ah!, OK, I'll keep on 3.2.0 for the moment and if I need something from 3.2.2 I'll BMO, if it's not yet released. Thanks!
Though I must mention that considering the go32v2 target a "minor" one is a little harsh, IMHO. ::)
-
Though I must mention that considering the go32v2 target a "minor" one is a little harsh, IMHO. ::)
The main targets are Windows, Linux and macOS. Everything else is considered minor compared to them.
-
The main targets are Windows, Linux and macOS. Everything else is considered minor compared to them.
I understand that. I just think that at least GO32v2 might also be a "main" target, even if just for historical reasons, never mind that without it it's somewhat difficult to keep "updated" there.
Of course, that's just an opinion, and I understand perfectly that we are at the "mercy" of the official maintainer, whether he has the time and inclination to do it.
And of course, others will have their pet systems that they would want to consider "major targets" ;)
-
Hi all,
sourceforge seems to have an empty dir where the sources should be. Do they come later?
-
sourceforge seems to have an empty dir where the sources should be. Do they come later?
Ah, no, that is an oversight. When I uploaded releases to SF, I was thinking of repackaging sources with some script fixes, but ultimately decided against it. I'll see if I can do it somewhen today.
-
sourceforge seems to have an empty dir where the sources should be. Do they come later?
Must be an oversight*, since they exists in the primary ftp site (ftp://ftp.freepascal.org/pub/fpc/dist/3.2.2/source). Or if you don't like ftp, you can always use svn to check out the release tag (https://svn.freepascal.org/svn/fpc/tags/release_3_2_0). ;)
* As Marco already said ... :-[
-
Uploaded the sources to SF.NET, thanks for noticing.
-
It still has the issues I posted on the rc thread: :(
This could also be merged: https://bugs.freepascal.org/view.php?id=37980
--
Also these are bad: https://bugs.freepascal.org/view.php?id=38129 https://bugs.freepascal.org/view.php?id=35651
These programs give all kinds of errors (access violation, division by zero): https://bugs.freepascal.org/view.php?id=37468 https://bugs.freepascal.org/view.php?id=37926
-
This could also be merged: https://bugs.freepascal.org/view.php?id=37980
Deemed as too invasive by MvC.
Also these are bad: https://bugs.freepascal.org/view.php?id=38129
Got no response on the core list when I asked whether it should be merged.
https://bugs.freepascal.org/view.php?id=35651
No specific revision known that fixed this, thus no merge possible.
These programs give all kinds of errors (access violation, division by zero): https://bugs.freepascal.org/view.php?id=37468
Seems that I missed that Florian fixed it again with a separate revision.
https://bugs.freepascal.org/view.php?id=37926
No final fix yet, thus nothing to merge.
-
As I am glad FreePascal 3.2.2 has been finally released, yesterday I downloaded the 32-bit Windows installer for me to try out this new version of FreePascal. However, there is a very concerning issue about it.
My antivirus (Avast Free Antivirus) detected malware in fpc-3.2.2.i386-win32.exe installer. The file in question was downloaded from Sourceforge yesterday, May 31, 2021. Attached is a screenshot of the antivirus program scanning result.
Today, June 1, 2021 I downloaded the installer again, hoping either the developers learned about this issue and the malware was removed or perhaps my antivirus, being updated, would not detect the aforementioned malware anymore and it was just a false positive. But, today the malware was detected as well. Attached is also a screenshot of today's Avast Antivirus scanning result.
Is there actual malware in fpc-3.2.2.i386-win32.exe installer or my antivirus detected a false positive? If the former is true, how did the fpc-3.2.2.i386-win32.exe installer get infected?
I hope this issue will be addressed as soon as possible. Thanks in advance.
-
Is there actual malware in fpc-3.2.2.i386-win32.exe installer or my antivirus detected a false positive? If the former is true, how did the fpc-3.2.2.i386-win32.exe installer get infected?
AntiVirus systems really like to detect FPC binaries. The binary on SourceForge has the same checksum as the one on our FTP servers and VirusTotal (https://www.virustotal.com/gui/file/7ec78b1790ecac7685f440b17f9e03865bc09846b7c068a9270c4d37704b5ac8/detection) reports that only Avast and AVG detect something. So yes, it's a false positive and you should report it to your AntiVirus vendor.
-
In the past i have always/often to report selfcompiled fpc and it tools to Avira, because the software detects and blocks it. After the reporting in 1 or 2 days it was no problem to compile. I think if the issue is reported, the AV-Provider will update their reporting.
Report, report and report, so the AV-Providers will have a look to get their product less producing positive false.
Now Avira is not useable for me, becaus with the last changes it installs a lot of unwanted software and i can not inhibit this. The Support have checked tis and the official answer was 'It by design'. Ok, with this design i have closed my paid subscription (it too - by design).
-
Thanks to both of you for your replies.
Curiously enough, after scanning the Win32 installers for fpc versions 3.0.4 and 3.2.0, which I still keep, Avast Antivirus didn't detect any malware threats. How come this antivirus only detected malware in the Win32 installer for fpc 3.2.2.?
Anyway, I've tried Kaspersky antivirus and it didn't detect any threat in fpc-3.2.2.i386-win32.exe installer, and given Kaspersky antivirus' very good reputation, I suspect the malware detected by Avast Antivirus is a false positive.
-
Curiously enough, after scanning the Win32 installers for fpc versions 3.0.4 and 3.2.0, which I still keep, Avast Antivirus didn't detect any malware threats. How come this antivirus only detected malware in the Win32 installer for fpc 3.2.2.?
Because AntiVirus software uses heuristics. The code from 3.2.0 to 3.2.2 changed enough that their heuristics triggered and they don't have the new binaries in their exclusion list, yet.
-
AntiVirus systems really like to detect FPC binaries. The binary on SourceForge has the same checksum as the one on our FTP servers and VirusTotal (https://www.virustotal.com/gui/file/7ec78b1790ecac7685f440b17f9e03865bc09846b7c068a9270c4d37704b5ac8/detection) reports that only Avast and AVG detect something. So yes, it's a false positive and you should report it to your AntiVirus vendor.
I don't think the misidentification and false positives are always just by accident, by these antivirus companies. Definitely users should report and make it clear that they expect their antivirus product to be accurate and not spewing BS alerts to appear more useful than it actually is.
-
I don't recommend to use Avast. Read "Antivirus firm Avast is reportedly selling users' web browsing data" from Cnet and other sources. The best antivirus is Windows Defender form Microsoft. We never had any issues with it.
We compiled our products with Delphi many years and now with FPC, earlier with Delphi we had false positives with Avast and some other antiviruses 1-2 times annually. Now with FPC compiled code no problem since 2019.
-
Thanks to the FPC team ;D
-
The Mac fpc source installer
fpc-src-3.2.2-1-laz.pkg
installs 3.2.0 not 3.2.2.
I am unable to get Lazarus configured due to this problem.
Download was from https://sourceforge.net/projects/lazarus/files/Lazarus%20macOS%20x86-64/Lazarus%202.2RC1/
-
The Mac fpc source installer
fpc-src-3.2.2-1-laz.pkg
installs 3.2.0 not 3.2.2.
I am unable to get Lazarus configured due to this problem.
Download was from https://sourceforge.net/projects/lazarus/files/Lazarus%20macOS%20x86-64/Lazarus%202.2RC1/
Please report this in the Lazarus 2.2 RC1 thread (https://forum.lazarus.freepascal.org/index.php/topic,55339.0.html). This is about the 3.2.2 release of FPC which does not provide such a download.
-
I recently installed FPC 3.2.2 on M1 Mac (fpc-3.2.2.intelarm64-macosx.dmg).
Thanks to FPC team for their great work!
I noticed that during installation I was informed about installation of Rosetta 2 emulator first time (I didn't use it earlier).
May I suggest that FPC binaries (or installer agents) should be Universal Binaries to work without Rosetta emulator.
Cross-compilation for x86-64 or aarch64 is very easy on any Mac with Big Sur. Universal Binary also can be created with one call of lipo command.
I'm sure that Apple will drop Rosetta 2 emulator in several years and we should be ready.
-
The FPC binaries themselves are Universal Binaries. They have been from the migration of PowerPC to Intel on.
I don't know about the installer however.