On Fri, 9 Sept 2022 at 08:59, Ron Olson <tachokni...@gmail.com> wrote:
> Hey all- > > I’m having an issue trying to get Swift 5.6.3 built on EPEL-8, even though > it builds fine for everything else (Rawhide, F36, F35, EPEL-9): “undefined > reference to 'std::__throw_bad_array_new_length()’”. > > https://koji.fedoraproject.org/koji/taskinfo?taskID=91757790 > > Never saw this issue before with previous Swift builds on EPEL-8, so I > tried troubleshooting it by building it with mock, but what’s weird is that > when I try building it with the various EPEL-8 flavors I have in /etc/mock, > they all build fine. I noticed there’s a “epel-7-x86_64.cfg”, but no > epel-8-x86_64.cfg; what is Koji using to build EPEL-8 projects? > > In order to do local mock builds of epel-8 you need to either make some symbolic links in /etc/mock or choose a distribution to build against: [root@alma8-wsl2 ~]# ls -l /etc/mock/*epel-8* -rw-r--r--. 1 root mock 251 Aug 10 08:06 /etc/mock/alma+epel-8-aarch64.cfg -rw-r--r--. 1 root mock 251 Aug 10 08:06 /etc/mock/alma+epel-8-ppc64le.cfg -rw-r--r--. 1 root mock 248 Aug 10 08:06 /etc/mock/alma+epel-8-x86_64.cfg -rw-r--r--. 1 root mock 310 Aug 10 08:06 /etc/mock/centos-stream+epel-8-aarch64.cfg -rw-r--r--. 1 root mock 310 Aug 10 08:06 /etc/mock/centos-stream+epel-8-ppc64le.cfg -rw-r--r--. 1 root mock 307 Aug 10 08:06 /etc/mock/centos-stream+epel-8-x86_64.cfg -rw-r--r--. 1 root mock 262 Aug 10 08:06 /etc/mock/circlelinux+epel-8-aarch64.cfg -rw-r--r--. 1 root mock 262 Aug 10 08:06 /etc/mock/circlelinux+epel-8-ppc64le.cfg -rw-r--r--. 1 root mock 259 Aug 10 08:06 /etc/mock/circlelinux+epel-8-x86_64.cfg lrwxrwxrwx. 1 root root 23 Feb 25 2022 /etc/mock/epel-8-aarch64.cfg -> alma+epel-8-aarch64.cfg lrwxrwxrwx. 1 root root 22 Feb 25 2022 /etc/mock/epel-8-x86_64.cfg -> alma+epel-8-x86_64.cfg -rw-r--r--. 1 root mock 263 Aug 10 08:06 /etc/mock/oraclelinux+epel-8-aarch64.cfg -rw-r--r--. 1 root mock 260 Aug 10 08:06 /etc/mock/oraclelinux+epel-8-x86_64.cfg -rw-r--r--. 1 root mock 162 Aug 10 08:06 /etc/mock/rhel+epel-8-aarch64.cfg -rw-r--r--. 1 root mock 162 Aug 10 08:06 /etc/mock/rhel+epel-8-ppc64le.cfg -rw-r--r--. 1 root mock 160 Aug 10 08:06 /etc/mock/rhel+epel-8-s390x.cfg -rw-r--r--. 1 root mock 161 Aug 10 08:06 /etc/mock/rhel+epel-8-x86_64.cfg -rw-r--r--. 1 root mock 250 Aug 10 08:06 /etc/mock/rocky+epel-8-aarch64.cfg -rw-r--r--. 1 root mock 247 Aug 10 08:06 /etc/mock/rocky+epel-8-x86_64.cfg In my case, I chose alma+epel-8 to make the builds. Koji does not use any of these configs but for every build creates its own 'buildroot' and aims the mocks spawned against that. This makes it hard to make a 1:1 link but the closest would be /etc/mock/rhel+epel-8-${basearch}.cfg My guess is that the default epel-8 libstdc is too old and you will need to set up the spec to use the gcc-toolset-10 or gcc-toolset-11 to get a new enough compiler and library to work with. > Also, on a related note, what is the protocol for having one platform fail > to build, while the others do? Is it okay to submit the Fedora/EPEL-9 > builds to production, or is it more of a all-or-nothing kind of thing? I’ve > been taking the latter approach, but I’ve been wondering if it’s not okay > to let everyone else have the latest-n-greatest, as I’ve been having a lot > of trouble finding the time to troubleshoot this EPEL-8 issue. > > > Thanks! > > Ron > _______________________________________________ > 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, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren
_______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
