Hi Orion, I took a more careful look the Bugzilla entry, and what I see are the following 3 entries:
Version: 41 sudo dnf install suitesparse-devel -- Found OpenMP_C: -fopenmp (found version "4.5") -- Found OpenMP: TRUE (found version "4.5") found components: C -- SuiteSparse_config version: 7.6.0 -- SuiteSparse_config include: /usr/include/suitesparse What this is telling me is that he is trying to build version 7.6.0 of suitesparse on Fedora 41. That is not currently the approved version. If we take a look at the suitesparse-devel package for Fedora 41 at the following link, we see it has to be version 7.7.0-2: https://packages.fedoraproject.org/pkgs/suitesparse/suitesparse-devel/fedora-41.html The version 7.6.0-1 is only approved for Fedora 40, as shown in the following link: https://packages.fedoraproject.org/pkgs/suitesparse/suitesparse-devel/ The suitesparse releases are different for each Fedora version: Fedora Rawhide => 7.10.0-1.fc43 Fedora 42 => 7.8.3-1.fc42 Fedora 41 => 7.7.0-2.fc41 Fedora 40 => 7.6.0-1.fc40 So either the Fedora version being tested on has to be changed for a specific version of suitesparse, or vice versa. Hope it helps, Paul On Mon, May 12, 2025 at 6:10 PM Paul Grosu <pgr...@gmail.com> wrote: > Hi Orion, > > Thank you for pointing me to the Bugzilla page. Could you please add me > to the packager and/or qa group for my FAS account (pgrosu) so I can log > into f40-test.fedorainfracloud.org to test this out. > > Thanks, > Paul > > On Sun, May 11, 2025 at 4:45 PM Orion Poplawski <or...@nwra.com> wrote: > >> On 5/9/25 23:37, Paul Grosu wrote: >> > Hi Orion, >> > >> > Do you have the complete build-log to see the trace of it? Something >> > similar to this: >> > >> > https://build.alpinelinux.org/buildlogs/build-3-20-x86_64/community/ >> > suitesparse/suitesparse-7.7.0-r0.log <https://build.alpinelinux.org/ >> > >> buildlogs/build-3-20-x86_64/community/suitesparse/suitesparse-7.7.0-r0.log> >> > >> > There might be more details in that log, that might hint to a possible >> > cause. Do you by any chance have all the steps to replicate it? >> >> I think the cause is pretty clear - it's how to resolve it that is not. >> You can see: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=2355055 >> >> for more details. >> >> I did come across this: >> >> https://reviews.llvm.org/D32668 >> >> which seems promising, but not sure I'll be able to adapt that to >> SuiteSparse or not. >> >> >> > On Fri, May 9, 2025 at 11:42 PM Orion Poplawski <or...@nwra.com >> > <mailto:or...@nwra.com>> wrote: >> > >> > This seems to be a common issue with packages built with cmake that >> > generate both shared and static libraries. With the .a files >> separated >> > into a -static package if it is not installed you can get the >> following >> > type of error when importing the cmake package: >> > >> > CMake Error at >> > >> /usr/lib64/cmake/SuiteSparse_config/SuiteSparse_configTargets.cmake:104 >> > (message): >> > The imported target "SuiteSparse::SuiteSparseConfig_static" >> > references the >> > file >> > >> > "/usr/lib64/libsuitesparseconfig.a" >> > >> > but this file does not exist. Possible reasons include: >> > >> > * The file was deleted, renamed, or moved to another location. >> > >> > * An install or uninstall procedure did not complete >> successfully. >> > >> > * The installation package was faulty and contained >> > >> > "/usr/lib64/cmake/SuiteSparse_config/ >> > SuiteSparse_configTargets.cmake" >> > >> > but not all the files it references. >> > >> > >> > Is there some way that packages can handle having the static libs >> > not be >> > present in a general way? I'd like to avoid having to do separate >> > shared and static builds. >> > >> > >> > -- >> > Orion Poplawski >> > he/him/his - surely the least important thing about me >> > IT Systems Manager 720-772-5637 >> > NWRA, Boulder/CoRA Office FAX: 303-415-9702 >> > 3380 Mitchell Lane or...@nwra.com <mailto:or...@nwra.com> >> > Boulder, CO 80301 https://www.nwra.com/ <https://www.nwra.com/> >> > >> > -- >> > _______________________________________________ >> > devel mailing list -- devel@lists.fedoraproject.org >> > <mailto:devel@lists.fedoraproject.org> >> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org >> > <mailto:devel-le...@lists.fedoraproject.org> >> > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/ >> > project/code-of-conduct/ <https://docs.fedoraproject.org/en-US/ >> > project/code-of-conduct/> >> > List Guidelines: https://fedoraproject.org/wiki/ >> > Mailing_list_guidelines <https://fedoraproject.org/wiki/ >> > Mailing_list_guidelines> >> > List Archives: https://lists.fedoraproject.org/archives/list/ >> > devel@lists.fedoraproject.org <https://lists.fedoraproject.org/ >> > archives/list/devel@lists.fedoraproject.org> >> > Do not reply to spam, report it: https://pagure.io/fedora- >> > infrastructure/new_issue <https://pagure.io/fedora-infrastructure/ >> > new_issue> >> > >> > >> >> >> -- >> Orion Poplawski >> he/him/his - surely the least important thing about me >> IT Systems Manager 720-772-5637 >> NWRA, Boulder/CoRA Office FAX: 303-415-9702 >> 3380 Mitchell Lane or...@nwra.com >> Boulder, CO 80301 https://www.nwra.com/ >> -- >> _______________________________________________ >> 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 >> >
-- _______________________________________________ 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
