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
