From Fedora Project Wiki

View ( | ) (20 | 50 | 100 | 250 | 500)
  • ===GraphicsMagick-1.3.x for F-11 (ABI change)=== ...ef>, “Heads up, I'm working on a GM-1.3.7 update to F-11 which includes an ABI break. I'll be taking care of building/fixing dependent packages (including ...
    24 KB (3,701 words) - 14:19, 18 September 2016
  • ...ailures during builds of multiple packages. These two versions have slight ABI incompatibility even though it's easily fixable. This step must be properly Full ABI Compatibility Report: ...
    15 KB (2,294 words) - 22:41, 8 February 2022
  • ...rebuilt binaries will have been compiled against a specific Fedora or EPEL ABI. ...
    7 KB (1,018 words) - 06:15, 17 June 2015
  • The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is absent from Boost, this entails rebuilding of all dependent pa ...
    7 KB (951 words) - 22:03, 10 March 2022
  • ...8 upstream release, but it can be backported to Fedora because there is no ABI impact. ...
    6 KB (937 words) - 16:50, 24 July 2019
  • ...might be necessary to create compatibility packages that provide older API/ABI level of the same library. However creating these compatibility packages is ...
    8 KB (1,121 words) - 20:18, 21 December 2018
  • The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is one of explicit Boost non-goals, this entails rebuilding of al ...
    7 KB (1,047 words) - 17:52, 25 January 2019
  • The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is absent from Boost, this entails rebuilding of all dependent pa ...
    7 KB (1,045 words) - 16:19, 29 January 2021
  • The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is one of explicit Boost non-goals, this entails rebuilding of al ...
    7 KB (959 words) - 14:48, 2 March 2018
  • * Provides a 100% BLAS and LAPACK compatible ABI/API, with interfaces for both 32- and 64-bit integers. ...
    7 KB (986 words) - 17:31, 18 January 2022
  • | Ensuring ABI stability in Fedora|| [[User:sinnykumari|sinnykumari]] , [[User:dodji|dodji ...
    17 KB (2,234 words) - 21:57, 1 April 2018
  • We're not removing any functionality and keeping the ABI in place (though we add new libraries). The upgrades should be seamless. ...
    6 KB (861 words) - 09:19, 21 March 2017
  • The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is absent from Boost, this entails rebuilding of all dependent pa ...
    7 KB (1,048 words) - 18:30, 4 January 2023
  • ===[[Changes/PPC64LE Float128 Transition | New 128-bit IEEE long double ABI for IBM 64-bit POWER LE]]=== Transition IBM 64-bit POWER LE systems to the new 128-bit IEEE long double ABI. ...
    21 KB (2,785 words) - 14:36, 10 May 2022
  • ...not to be practically "at all possible" to "[a]void Major version updates, ABI breakage or API changes". ...
    8 KB (1,184 words) - 10:10, 15 February 2017
  • The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is one of explicit Boost non-goals, this entails rebuilding of al ...
    7 KB (1,048 words) - 11:02, 20 July 2016
  • * Based on feedback from other WGs, provide a API and/or ABI stability for a specific release rather than simply package versions/releas ...
    7 KB (1,054 words) - 12:43, 24 August 2015
  • ...ebuild (if required) before the final release of glibc 2.35, but after the ABI is frozen. ...ar, but to do so may require a mass rebuild to remove new symbols from the ABI/API. ...
    16 KB (2,625 words) - 13:56, 16 February 2022
  • The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is absent from Boost, this entails rebuilding of all dependent pa ...
    8 KB (1,115 words) - 16:40, 12 November 2020
  • ** An ABI-compliant <code>-fstack-clash-protection</code> implementation has not yet ...
    7 KB (1,029 words) - 14:52, 2 March 2018
View ( | ) (20 | 50 | 100 | 250 | 500)