From Fedora Project Wiki
(Created page with "= Free Pascal Compiler 3.2.0 = == Summary == Update the Free Pascal Compiler used within Fedora to version 3.2.0, once it is published, and enable building (previously unsupp...")
 
(Add trackers)
 
(4 intermediate revisions by 2 users not shown)
Line 4: Line 4:
Update the Free Pascal Compiler used within Fedora to version 3.2.0, once it is published, and enable building (previously unsupported) AArch64 and ppc64le packages using the compiler.
Update the Free Pascal Compiler used within Fedora to version 3.2.0, once it is published, and enable building (previously unsupported) AArch64 and ppc64le packages using the compiler.


== Owner ==
== Owners ==
* Name: [[User:suve|Artur Iwicki]]
* Name: [[User:suve|Artur Iwicki]]
* Email: <fedora@svgames.pl>
* Email: <fedora@svgames.pl>
* Name: [[User:joost|Joost van der Sluis]]
* Email: <joost@cnoc.nl>
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
-->
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)
* Product:
* Responsible WG:
-->
-->


Line 18: Line 18:
* Targeted release: [[Releases/32 | Fedora 32 ]]  
* Targeted release: [[Releases/32 | Fedora 32 ]]  
* Last updated: {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* Last updated: {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1766231 #1766231]
* Release notes tracker: <will be assigned by the Wrangler>
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/416 #416]


== Detailed Description ==
== Detailed Description ==
Line 36: Line 36:
** Cross-compile the compiler for AArch64 and ppc64le (required for bootstrapping).
** Cross-compile the compiler for AArch64 and ppc64le (required for bootstrapping).
** Add AArch64 and ppc64le to the `ExclusiveArch:` tag in the package spec.
** Add AArch64 and ppc64le to the `ExclusiveArch:` tag in the package spec.
** Build the compiler for the new architectures.
** Build the compiler for the new architectures, using the cross-compiled binaries.
** Rebuild the compiler using the  
** Build the compiler once again, this time using the self-hosted binary.
** Update the `fpc-rpm-macros` package to accurately reflect the new, expanded architecture list.
** Update the `fpc-rpm-macros` package to accurately reflect the new, expanded architecture list.


Line 52: Line 52:


== How To Test ==
== How To Test ==
**TODO**
Since the main impact of this change is adding support for new architectures, a mass-rebuild of dependent packages will also act as a test.
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
 
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
 
A good "how to test" should answer these four questions:
 
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this change? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the change is
working like it's supposed to?
3. What are the expected results of those actions?
-->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
Users wanting to test this change may want to submit a scratch build against rawhide. If needed, a [b]copr[/b] repo may also be created, so anyone interested may install the compiler on F31 or F30.
N/A (not a System Wide Change)


== User Experience ==
== User Experience ==
<!-- If this change proposal is noticeable by users, how will their experiences change as a result?
FPC-dependent packages will become available on a larger number of architectures.  
 
This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
 
Describe what Users will see or notice, for example:
  - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
  - Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
- Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running".
- Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
-->


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
Lazarus depends on FPC exact version, so it will need to be rebuilt.
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== Contingency Plan ==
== Contingency Plan ==
If bugs are discovered, I'd appreciate help from the package owners in preparing self-contained testcases to speed up analysis and fixing the bugs. I do not expect the compiler to introduce any bugs for x86 / x86_64 / ARM, so the main question will be whether the new AArch64 and ppc64le targets work correctly.


<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->
* Contingency mechanism: If errors occur only for AArch64 / ppc64le builds, keep the compiler at the new version (3.2.0), but disable AArch64 and ppc64le (attempt to enable them again once F32 branches from Rawhide). If errors are also spotted on x86 / x86_64 / ARM, revert to the the older version (3.0.4). After choosing either option, perform a mass rebuild of dependent packages.
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency deadline: Before release
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Blocks release? No
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? No
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
Free Pascal wiki pages:
 
* [https://wiki.freepascal.org/FPC_New_Features_3.2|FPC New Features 3.2]
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* [https://wiki.freepascal.org/User_Changes_3.2|User Changes 3.2]
N/A (not a System Wide Change)


== Release Notes ==
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
Fedora 32 ships with Free Pascal Compiler 3.2.0, see the [https://wiki.freepascal.org/FPC_New_Features_3.2|FPC New Features 3.2] page for a list of new features and consult the [https://wiki.freepascal.org/User_Changes_3.2|User Changes 3.2] page for a list of backwards-incompatible changes.
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.  
 
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
-->
 
[[Category:ChangePageIncomplete]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->


[[Category:ChangeAcceptedF32]]
[[Category:SystemWideChange]]
[[Category:SystemWideChange]]

Latest revision as of 16:01, 28 October 2019

Free Pascal Compiler 3.2.0

Summary

Update the Free Pascal Compiler used within Fedora to version 3.2.0, once it is published, and enable building (previously unsupported) AArch64 and ppc64le packages using the compiler.

Owners


Current status

Detailed Description

The Free Pascal Compiler team plans to release a new release, 3.2.0, somewhere until the end of this year (2019). This date falls within the Fedora 32 release schedule, so the new compiler version could be introduced into F32 once it's released.

Benefit to Fedora

The Free Pascal Compiler will support new architectures, which in turn will allow programs compiled using FPC to run on more architectures supported by Fedora.

See also New Features 3.2 for a list of other new compiler features.

Scope

All packages depending on fpc should be rebuilt with the new fpc once it hits F32, or, if there is not enough time for that, just all packages built after the new fpc hits the buildroots.

  • Proposal owners:
    • Update the fpc package to version 3.2.0.
    • Cross-compile the compiler for AArch64 and ppc64le (required for bootstrapping).
    • Add AArch64 and ppc64le to the ExclusiveArch: tag in the package spec.
    • Build the compiler for the new architectures, using the cross-compiled binaries.
    • Build the compiler once again, this time using the self-hosted binary.
    • Update the fpc-rpm-macros package to accurately reflect the new, expanded architecture list.
  • Other developers: In the first few days or weeks, just voluntary rebuilds using the new fpc. Should there be any build failures, look at the Changes 3.2 page to see if the package is affected by any backwards-incompatible change. If the packaged program/library does not support one of the newly introduced architectures (AArch64/ppc64le), either resolve the issue or add an ExcludeArch: tag to the spec.
  • Release engineering: Mass rebuild requested for F32.
  • Policies and guidelines: No changes needed.
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

No impact

How To Test

Since the main impact of this change is adding support for new architectures, a mass-rebuild of dependent packages will also act as a test.

Users wanting to test this change may want to submit a scratch build against rawhide. If needed, a [b]copr[/b] repo may also be created, so anyone interested may install the compiler on F31 or F30.

User Experience

FPC-dependent packages will become available on a larger number of architectures.

Dependencies

Lazarus depends on FPC exact version, so it will need to be rebuilt.

Contingency Plan

If bugs are discovered, I'd appreciate help from the package owners in preparing self-contained testcases to speed up analysis and fixing the bugs. I do not expect the compiler to introduce any bugs for x86 / x86_64 / ARM, so the main question will be whether the new AArch64 and ppc64le targets work correctly.

  • Contingency mechanism: If errors occur only for AArch64 / ppc64le builds, keep the compiler at the new version (3.2.0), but disable AArch64 and ppc64le (attempt to enable them again once F32 branches from Rawhide). If errors are also spotted on x86 / x86_64 / ARM, revert to the the older version (3.0.4). After choosing either option, perform a mass rebuild of dependent packages.
  • Contingency deadline: Before release
  • Blocks release? No
  • Blocks product? No

Documentation

Free Pascal wiki pages:

Release Notes

Fedora 32 ships with Free Pascal Compiler 3.2.0, see the New Features 3.2 page for a list of new features and consult the Changes 3.2 page for a list of backwards-incompatible changes.

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/Free_Pascal_Compiler_3.2.0&oldid=556630"