Re: Free Pascal and the new glibc
On 23/09/21 16:30, Mamoru TASAKA wrote: > Mattia Verga via devel wrote on 2021/09/23 15:11: >> I've created f35-build-side-46123 and tagged fpc-3.2.2-3.fc35 into that. >> >> Lazarus rebuild is in progress. I will take care of rebuilding the other >> packages listed in bug 1987485 as soon as I can. If the maintainers of >> those packages want to rebuild their package (in the side-tag), please >> do so, it will speed up the process. >> >> Mattia >> > > [tasaka1@localhost ~]$ dnf repoquery --arch=src --whatrequires lazarus > ccdciel-0:0.9.75.1-2.fc36.src > cqrlog-0:2.5.2-3.fc36.src > doublecmd-0:0.9.10-2.fc34.src > goverlay-0:0.6.3-1.fc36.src > indistarter-0:2.2.0-4.fc36.src > lazpaint-0:7.1.6-3.fc36.src > skychart-0:4.3-7.4358svn.fc36.src > > [tasaka1@localhost ~]$ dnf repoquery --arch=src --whatrequires fpc > ccdciel-0:0.9.75.1-2.fc36.src > colorful-0:1.3-13.fc36.src > cqrlog-0:2.5.2-3.fc36.src > doublecmd-0:0.9.10-2.fc34.src > fpc-0:3.2.2-3.fc36.src > gearhead1-0:1.310-7.fc36.src > hedgewars-0:1.0.0-19.fc35.src > indistarter-0:2.2.0-4.fc36.src > lazarus-0:2.0.12-3.fc36.src > lazpaint-0:7.1.6-3.fc36.src > nbc-0:1.2.1.r3-22.fc34.src > skychart-0:4.3-7.4358svn.fc36.src > > Although hedgewars is listed, looking at hedgewars.spec and build.log, it uses > "-DBUILD_ENGINE_C=1" option which converts .pas source to .c (using hedgewars > internal > tool) and build .c files with clang, so hedgewars can be omitted from the > list above. > > Now I think all packages using fpc or lazarus on build are now rebuilt: > https://koji.fedoraproject.org/koji/builds?inherited=0&tagID=46123&order=-completion_time&latest=1 > > Regards, > Mamoru Wonderful! Thank you Mamoru, I've pushed a Bodhi update [1] from the side-tag. If we missed any package, just let me know and I'll edit the update. Thanks all Mattia [1] https://bodhi.fedoraproject.org/updates/FEDORA-2021-6c20029f5d ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
Mattia Verga via devel wrote on 2021/09/23 15:11: I've created f35-build-side-46123 and tagged fpc-3.2.2-3.fc35 into that. Lazarus rebuild is in progress. I will take care of rebuilding the other packages listed in bug 1987485 as soon as I can. If the maintainers of those packages want to rebuild their package (in the side-tag), please do so, it will speed up the process. Mattia [tasaka1@localhost ~]$ dnf repoquery --arch=src --whatrequires lazarus ccdciel-0:0.9.75.1-2.fc36.src cqrlog-0:2.5.2-3.fc36.src doublecmd-0:0.9.10-2.fc34.src goverlay-0:0.6.3-1.fc36.src indistarter-0:2.2.0-4.fc36.src lazpaint-0:7.1.6-3.fc36.src skychart-0:4.3-7.4358svn.fc36.src [tasaka1@localhost ~]$ dnf repoquery --arch=src --whatrequires fpc ccdciel-0:0.9.75.1-2.fc36.src colorful-0:1.3-13.fc36.src cqrlog-0:2.5.2-3.fc36.src doublecmd-0:0.9.10-2.fc34.src fpc-0:3.2.2-3.fc36.src gearhead1-0:1.310-7.fc36.src hedgewars-0:1.0.0-19.fc35.src indistarter-0:2.2.0-4.fc36.src lazarus-0:2.0.12-3.fc36.src lazpaint-0:7.1.6-3.fc36.src nbc-0:1.2.1.r3-22.fc34.src skychart-0:4.3-7.4358svn.fc36.src Although hedgewars is listed, looking at hedgewars.spec and build.log, it uses "-DBUILD_ENGINE_C=1" option which converts .pas source to .c (using hedgewars internal tool) and build .c files with clang, so hedgewars can be omitted from the list above. Now I think all packages using fpc or lazarus on build are now rebuilt: https://koji.fedoraproject.org/koji/builds?inherited=0&tagID=46123&order=-completion_time&latest=1 Regards, Mamoru ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
> I've created f35-build-side-46123 and tagged fpc-3.2.2-3.fc35 into that. > Lazarus rebuild is in progress. Thanks. Lazarus has been built successfully. > If the maintainers of those packages want to rebuild their package > (in the side-tag), please do so, it will speed up the process. I'll go over my packages (colorful, gearhead1, lazpaint) today. Thanks again. A.FI. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
I've created f35-build-side-46123 and tagged fpc-3.2.2-3.fc35 into that. Lazarus rebuild is in progress. I will take care of rebuilding the other packages listed in bug 1987485 as soon as I can. If the maintainers of those packages want to rebuild their package (in the side-tag), please do so, it will speed up the process. Mattia ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
> I can take care of creating the side-tag, > tagging the fpc build in it (no need to rebuild it again) > and trying to rebuild all dependent packages there. Sure, thanks for the help. A.FI. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
On 22/09/21 12:47, Artur Frenszek-Iwicki wrote: > The build for f35 was successful: > https://koji.fedoraproject.org/koji/buildinfo?buildID=1835338 > I've submitted an update to bodhi as well: > https://bodhi.fedoraproject.org/updates/FEDORA-2021-032397269f > > Although now that I think of it, it probably would've been cleaner to do > create a side tag, perform the build there, and then use it to re-build all > the dependent packages. Should we unpush this update and go the side tag > route, or just create a buildroot override for the dependants? > > A.FI. A side-tag update would be nice, so that we can pack fpc and lazarus in the same update, at least. Are you a provenpackager? If not, I am. I can take care of creating the side-tag, tagging the fpc build in it (no need to rebuild it again) and trying to rebuild all dependent packages there. But I will probably not have time to do that until Saturday. The already created fpc update will not be pushed to stable until the beta freeze ends, so no need to hurry, though. Let me know. Mattia ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
The build for f35 was successful: https://koji.fedoraproject.org/koji/buildinfo?buildID=1835338 I've submitted an update to bodhi as well: https://bodhi.fedoraproject.org/updates/FEDORA-2021-032397269f Although now that I think of it, it probably would've been cleaner to do create a side tag, perform the build there, and then use it to re-build all the dependent packages. Should we unpush this update and go the side tag route, or just create a buildroot override for the dependants? A.FI. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
On Tue, 21 Sep 2021 12:19:10 - "Artur Frenszek-Iwicki" wrote: > The build was successful: > https://koji.fedoraproject.org/koji/taskinfo?taskID=76057984 > I see you've made a commit to the rawhide branch only; I'll go ahead and > apply the patch to the f35 branch as well. yes, please > Thanks for the help. The patch doesn't look complicated, but unfortunately I > have zero experience working with assembly, so I couldn't have done it myself. you are welcome :-) Based on Florian's reply we can't push the change to upstream as it is due to the incompatibility with older systems. Dan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
The build was successful: https://koji.fedoraproject.org/koji/taskinfo?taskID=76057984 I see you've made a commit to the rawhide branch only; I'll go ahead and apply the patch to the f35 branch as well. Thanks for the help. The patch doesn't look complicated, but unfortunately I have zero experience working with assembly, so I couldn't have done it myself. A.FI. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
On Mon, 20 Sep 2021 19:37:21 +0200
Dan Horák wrote:
> On Mon, 20 Sep 2021 18:34:44 +0200
> Dan Horák wrote:
>
> > On Mon, 20 Sep 2021 18:15:44 +0200
> > Florian Weimer wrote:
> >
> > > * Dan Horák:
> > >
> > > > On Mon, 20 Sep 2021 13:36:33 -
> > > > "Artur Frenszek-Iwicki" wrote:
> > > >
> > > >> Back in July, during the F35 Mass Rebuild, the Free Pascal Compiler
> > > >> package failed to build [1] because of linking issues on aarch64, i686
> > > >> and ppc64le, related to the new glibc 2.34. x86_64 and arm we
> > > >> unaffected, however.
> > > >> This was discussed briefly here on devel in thread [2]. The issue was
> > > >> submitted upstream [3], but so far, there has been little response.
> > > >
> > > > if I see right, then the libc_csu_{init,fini} symbols are not used for
> > > > anything inside fpc. I am going to try something to get rid of them
> > > > (starting with ppc64le) ...
> > >
> > > It is possible to replace them with 0 in the startup code that FPC has
> > > copied from glibc.
> >
> > yup, there are multiple places to fix (for ppc64le), but in general it's
> > possible to clone the change you made for glibc.
> >
> > see https://koji.fedoraproject.org/koji/taskinfo?taskID=76011952
>
> and almost there
> patch: https://paste.centos.org/view/53ad5822
> scratch build:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=76015030
>
> the aarch64 failure might be some parallel make problem ...
and all should be fixed now with
https://src.fedoraproject.org/rpms/fpc/c/b1d39299ade42686ca8e2a491f662efc4219a1f9?branch=rawhide
build for rawhide is in progress, a scratch build was successful
Dan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
* Dan Horák: > Florian, can the patch go upstream as it is or are there any side > effects when the resulting binary would run on system with glibc < 2.34? ELF constructors for the main program will not run on glibc < 2.34. But I don't think there will be immediate crashes. Whether the missing ELF constructors matter depends on the program of course. Constructors from dynamically shared objects are not impacted. Thanks, Florian ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
On Mon, 20 Sep 2021 18:34:44 +0200
Dan Horák wrote:
> On Mon, 20 Sep 2021 18:15:44 +0200
> Florian Weimer wrote:
>
> > * Dan Horák:
> >
> > > On Mon, 20 Sep 2021 13:36:33 -
> > > "Artur Frenszek-Iwicki" wrote:
> > >
> > >> Back in July, during the F35 Mass Rebuild, the Free Pascal Compiler
> > >> package failed to build [1] because of linking issues on aarch64, i686
> > >> and ppc64le, related to the new glibc 2.34. x86_64 and arm we
> > >> unaffected, however.
> > >> This was discussed briefly here on devel in thread [2]. The issue was
> > >> submitted upstream [3], but so far, there has been little response.
> > >
> > > if I see right, then the libc_csu_{init,fini} symbols are not used for
> > > anything inside fpc. I am going to try something to get rid of them
> > > (starting with ppc64le) ...
> >
> > It is possible to replace them with 0 in the startup code that FPC has
> > copied from glibc.
>
> yup, there are multiple places to fix (for ppc64le), but in general it's
> possible to clone the change you made for glibc.
>
> see https://koji.fedoraproject.org/koji/taskinfo?taskID=76011952
and almost there
patch: https://paste.centos.org/view/53ad5822
scratch build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=76015030
the aarch64 failure might be some parallel make problem ...
Florian, can the patch go upstream as it is or are there any side
effects when the resulting binary would run on system with glibc < 2.34?
for the record - ppc (32-bit), m68k, mips and riscv64 need similar fix
but that's all for tomorrow ...
Dan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
On Mon, 20 Sep 2021 18:15:44 +0200
Florian Weimer wrote:
> * Dan Horák:
>
> > On Mon, 20 Sep 2021 13:36:33 -
> > "Artur Frenszek-Iwicki" wrote:
> >
> >> Back in July, during the F35 Mass Rebuild, the Free Pascal Compiler
> >> package failed to build [1] because of linking issues on aarch64, i686 and
> >> ppc64le, related to the new glibc 2.34. x86_64 and arm we unaffected,
> >> however.
> >> This was discussed briefly here on devel in thread [2]. The issue was
> >> submitted upstream [3], but so far, there has been little response.
> >
> > if I see right, then the libc_csu_{init,fini} symbols are not used for
> > anything inside fpc. I am going to try something to get rid of them
> > (starting with ppc64le) ...
>
> It is possible to replace them with 0 in the startup code that FPC has
> copied from glibc.
yup, there are multiple places to fix (for ppc64le), but in general it's
possible to clone the change you made for glibc.
see https://koji.fedoraproject.org/koji/taskinfo?taskID=76011952
Dan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
* Dan Horák:
> On Mon, 20 Sep 2021 13:36:33 -
> "Artur Frenszek-Iwicki" wrote:
>
>> Back in July, during the F35 Mass Rebuild, the Free Pascal Compiler package
>> failed to build [1] because of linking issues on aarch64, i686 and ppc64le,
>> related to the new glibc 2.34. x86_64 and arm we unaffected, however.
>> This was discussed briefly here on devel in thread [2]. The issue was
>> submitted upstream [3], but so far, there has been little response.
>
> if I see right, then the libc_csu_{init,fini} symbols are not used for
> anything inside fpc. I am going to try something to get rid of them
> (starting with ppc64le) ...
It is possible to replace them with 0 in the startup code that FPC has
copied from glibc.
(I have made this suggestion multiple times …)
Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
On 20/09/21 15:36, Artur Frenszek-Iwicki wrote: > In order to avoid retiring FPC (and all the other dependent packages) from > Fedora due to the FTBFS issue, we want to temporarily disable support for the > failing architectures (aarch64, i686 and ppc64le), leaving only the working > ones (arm and x86_64). Once either upstream solves the issue, or we come up > with Fedora-specific patches, these architectures can be bootstrapped and > re-enabled. > The plan seems reasonable to me. +1 I don't think we can expect upstream putting much effort fixing this incompatibility until Debian switches to glibc 2.34: as I understand, upstream uses Debian for development. Mattia ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
We'll remove these from %{fpc_arches} so that dependent packages can rebuild
without requiring changes to spec files.
A.FI.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
Should i disabled myself this arches for Goverlay or you add them into
`ExclusiveArch: %{fpc_arches}` and rebuild affected packages yourself? Thanks.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Free Pascal and the new glibc
On Mon, 20 Sep 2021 13:36:33 -
"Artur Frenszek-Iwicki" wrote:
> Back in July, during the F35 Mass Rebuild, the Free Pascal Compiler package
> failed to build [1] because of linking issues on aarch64, i686 and ppc64le,
> related to the new glibc 2.34. x86_64 and arm we unaffected, however.
> This was discussed briefly here on devel in thread [2]. The issue was
> submitted upstream [3], but so far, there has been little response.
if I see right, then the libc_csu_{init,fini} symbols are not used for
anything inside fpc. I am going to try something to get rid of them
(starting with ppc64le) ...
Dan
> In order to avoid retiring FPC (and all the other dependent packages) from
> Fedora due to the FTBFS issue, we want to temporarily disable support for the
> failing architectures (aarch64, i686 and ppc64le), leaving only the working
> ones (arm and x86_64). Once either upstream solves the issue, or we come up
> with Fedora-specific patches, these architectures can be bootstrapped and
> re-enabled.
>
> Since these issues are architecture-specific and solving them would likely
> involve editing upstream assembly code, I created separate RHBZ tickets for
> tracking each architecture separately:
> - aarch64: [4]
> - i686: [5]
> - ppc64le: [6]
>
> Let me know if this seems like a sensible plan, or if you have some other
> ideas. (In [2], a workaround solution was proposed. This didn't work. See [6]
> for details.)
> If we can't come up with anything else, I'll go through with this plan before
> the end of the month.
>
> Sincerely,
> A.FI.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1987485
> [2]
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/RLTQ5CJ7F2FAFYVPBZZHVRJK2LZX7D36/
> [3] https://gitlab.com/freepascal.org/fpc/source/-/issues/39295
> [4] https://bugzilla.redhat.com/show_bug.cgi?id=2005908
> [5] https://bugzilla.redhat.com/show_bug.cgi?id=2005909
> [6] https://bugzilla.redhat.com/show_bug.cgi?id=2005910
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> 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@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Free Pascal and the new glibc
Back in July, during the F35 Mass Rebuild, the Free Pascal Compiler package failed to build [1] because of linking issues on aarch64, i686 and ppc64le, related to the new glibc 2.34. x86_64 and arm we unaffected, however. This was discussed briefly here on devel in thread [2]. The issue was submitted upstream [3], but so far, there has been little response. In order to avoid retiring FPC (and all the other dependent packages) from Fedora due to the FTBFS issue, we want to temporarily disable support for the failing architectures (aarch64, i686 and ppc64le), leaving only the working ones (arm and x86_64). Once either upstream solves the issue, or we come up with Fedora-specific patches, these architectures can be bootstrapped and re-enabled. Since these issues are architecture-specific and solving them would likely involve editing upstream assembly code, I created separate RHBZ tickets for tracking each architecture separately: - aarch64: [4] - i686: [5] - ppc64le: [6] Let me know if this seems like a sensible plan, or if you have some other ideas. (In [2], a workaround solution was proposed. This didn't work. See [6] for details.) If we can't come up with anything else, I'll go through with this plan before the end of the month. Sincerely, A.FI. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1987485 [2] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/RLTQ5CJ7F2FAFYVPBZZHVRJK2LZX7D36/ [3] https://gitlab.com/freepascal.org/fpc/source/-/issues/39295 [4] https://bugzilla.redhat.com/show_bug.cgi?id=2005908 [5] https://bugzilla.redhat.com/show_bug.cgi?id=2005909 [6] https://bugzilla.redhat.com/show_bug.cgi?id=2005910 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
