From Fedora Project Wiki

< Changes

Revision as of 14:51, 9 October 2019 by Suve (talk | contribs) (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...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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.

Owner

Current status

  • Targeted release: Fedora 32
  • Last updated: 2019-10-09
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

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.
    • Rebuild the compiler using the
    • 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

    • TODO**

N/A (not a System Wide Change)

User Experience

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes