Re: btrfs loses 32-bit application compatibility after a while

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 7/20/23 11:06, Florian Weimer wrote:
> * Demi Marie Obenour:
> 
>> On 7/17/23 09:51, Florian Weimer wrote:
>>> * Daniel P. Berrangé:
>>>
>>>>> But that still raises the question - why does it look like this
>>>>> started to happen pretty suddenly around June 30?
>>>>> The list of updates that were applied to builders in that timeframe
>>>>> doesn't raise any alarm bells (except maybe the 6.3 kernel):
>>>>> (see https://pagure.io/releng/issue/11531#comment-864471)
>>>>> I read the release notes for the 6.3 kernel but didn't see any
>>>>> mentions of BTRFS changes that could explain this. :(
>>>>
>>>> Or what 32-bit code is being run in the context of koji that is
>>>> NOT compiled with LFS ?  Is this something silly like configure
>>>> script tests not enabling LFS, but the resulting applications
>>>> correctly using LFS ?
>>>
>>> A dependency used during RPM file creation, libcap, is not fully built
>>> in LFS mode.  Once we fix that, we know that we'll run into issues with
>>> chkconfig and update-alternatives.  It's a never-ending source of bugs.
>>> It's not a good use of maintainer time.
>>>
>>> We can't change the overall distribution flags with CFLAGS injection
>>> because doing so has ABI implications.
>>
>> Can they be changed at the next mass rebuild?
> 
> Not if we want to maintain compatibility with non-Fedora software.  It
> probably doesn't matter for most packages, but doing a per-package
> analysis is a lot of work.

>From this thread, it appears that non-LFS 32-bit software is fundamentally
unsupportable in the long run, just like software with 32-bit time_t is
unsupportable.  That leaves two options:

1. Break the ABI, preferably in such a way that causes non-LFS
   code to fail at load time rather than crashing.

2. Drop 32-bit support from the distribution altogether.

It looks like trying to keep 32-bit non-LFS software working will be an
endless time sink and is not sustainable in the long term.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux