Re: Help needed: build failure trying to upgrade healpix
We could use something like this instead:```%{__sed} --in-place=.backup --regexp-extended --_expression_='/^lt_cv_sys_global_symbol_to_cdecl=/{:start;s/""//;s/^(.*)\\$/\1/;T end;N;s/\n//;t start;:end}' configurediff -u configure.backup configure && mv configure.backup configure``` It is a bit more complex, due to the branching, but should be understandable.`lt_cv_sys_global_symbol_to_cdecl` is likely to be the definition causing issues. I would suggest only using this on an as needed basis. Hope this is helpful.-- Jarryd LisherSoftware Engineer2CF5D54114C1765FF66F8C3BCD174774D8A69173 15.08.2022, 00:50, "Jeff Law" :On 8/14/2022 6:29 AM, Jarryd Lisher via devel wrote: Hey, I figured out that this is mainly caused by the configure script containing multi-line definitions. So, the hacks only operate on the first part and land up leaving random lines of nonsense in the file. You can fix this by adding the following "unwrap" `sed` script just before the `%{configure}` line: ``` %{__sed} -i -z -e 's/\\\n//g' configure ``` It's not perfect, but is a simple fix to remove those errors from the configure.That seems like a pretty big hammer with fair potential for changingsomething we didn't really want to. Can we key it's behavior somehow onlines we care about?Thanks,Jeff___devel mailing list -- devel@lists.fedoraproject.orgTo unsubscribe send an email to devel-le...@lists.fedoraproject.orgFedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelinesList Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.orgDo not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue___
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
Re: Help needed: build failure trying to upgrade healpix
Hey, I figured out that this is mainly caused by the configure script containing multi-line definitions. So, the hacks only operate on the first part and land up leaving random lines of nonsense in the file. You can fix this by adding the following "unwrap" `sed` script just before the `%{configure}` line:```%{__sed} -i -z -e 's/\\\n//g' configure```It's not perfect, but is a simple fix to remove those errors from the configure.-- Jarryd LisherSoftware Engineer2CF5D54114C1765FF66F8C3BCD174774D8A69173 30.07.2022, 18:35, "Kevin Kofler via devel" :Mattia Verga via devel wrote: I'm at a dead end, can someone have a look at the scratch build [1] and explain me where's the fault?What I see is that the hacks that you apply to configure are apparently notworking:checking command to parse /usr/bin/nm -B output from gcc object/configure: line 7304: -e 's/^T .* \(.*\)$/extern int \1();/p' -e's/^[ABCDGIRSTW][ABCDGIRSTW]* .* \(.*\)$/extern char \1;/p': No such file ordirectoryIt is possible that that is what is causing the:checking for ffgnrwll in -lcfitsio... noconfigure: error: could not find the cfitsio libraryfailure in the C++ part's configure.Or maybe it is the code from this hack:+ /usr/bin/sed -r --in-place=.backup 's/^char \(\*f\) \(\) = /__attribute__((used)) char (*f) () = /g' ./configure+ /usr/bin/sed -r --in-place=.backup 's/^char \(\*f\) \(\);/__attribute__((used)) char (*f) ();/g' ./configure+ /usr/bin/sed -r --in-place=.backup 's/^char \$2 \(\);/__attribute__((used)) char \$2 ();/g' ./configurethat is not accepted by the C++ compiler?Kevin Kofler___devel mailing list -- devel@lists.fedoraproject.orgTo unsubscribe send an email to devel-le...@lists.fedoraproject.orgFedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelinesList Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.orgDo 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, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: F37 Change Proposal: Unfiltered Flathub (System-Wide Change)
Hi, I think the response article has one paragraph which is important to this discussion:"Since Fedora Flatpaks converts RPMs from the Fedora repositories to Flatpak applications, it is much easier to trust and audit from a Fedora Project developer and maintainer perspective. Furthermore, these RPMs already comply with all Fedora Project’s conducts and standards. They’re all built inside the Fedora Project’s infrastructure and based on RPMs that are maintained by Fedora Project maintainers. Flathub, on the other hand, is independent and unaffiliated with the Fedora Project. This also makes auditing harder for the Fedora Project maintainers."Which highlights the importance of prioritising Fedora packages over Flathub packages, regardless of whether they are RPMs or Flatpaks. --Jarryd 18:27, 05 July 2022, "Timothée Ravier" :The two articles mentioned above all full of errors and misconceptions about how Flatpak and Flathub works.See https://theevilskeleton.gitlab.io/2022/05/16/response-to-flatpak-is-not-the-future.html___devel mailing list -- devel@lists.fedoraproject.orgTo unsubscribe send an email to devel-le...@lists.fedoraproject.orgFedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelinesList Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.orgDo 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
