From: ddmgh <ddmgh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: kup: update to 0.10.0.
Date: Fri, 15 Nov 2024 17:15:00 +0100 [thread overview]
Message-ID: <20241115161500.8AFDF2E7D7@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52769@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1735 bytes --]
New comment by ddmgh on void-packages repository
https://github.com/void-linux/void-packages/pull/52769#issuecomment-2479334129
Comment:
New to this stuff and, when I went to build it, I received the following:
```
CMake Error at /usr/share/cmake-3.30/Modules/CMakeFindDependencyMacro.cmake:76 (find_package):
Could not find a configuration file for package "KF6CoreAddons" that is
compatible with requested version "6.7.0".
The following configuration files were considered but not accepted:
/usr/lib64/cmake/KF6CoreAddons/KF6CoreAddonsConfig.cmake, version: 6.6.0
/usr/lib/cmake/KF6CoreAddons/KF6CoreAddonsConfig.cmake, version: 6.6.0
/lib64/cmake/KF6CoreAddons/KF6CoreAddonsConfig.cmake, version: 6.6.0
/lib/cmake/KF6CoreAddons/KF6CoreAddonsConfig.cmake, version: 6.6.0
Call Stack (most recent call first):
/usr/lib64/cmake/KF6Package/KF6PackageConfig.cmake:55 (find_dependency)
/usr/share/cmake-3.30/Modules/CMakeFindDependencyMacro.cmake:76 (find_package)
/usr/lib64/cmake/Plasma/PlasmaConfig.cmake:52 (find_dependency)
CMakeLists.txt:51 (find_package)
-- Configuring incomplete, errors occurred!
=> ERROR: kup-0.10.0_1: do_configure: 'CFLAGS="-DNDEBUG ${CFLAGS/ -pipe / }" CXXFLAGS="-DNDEBUG ${CXXFLAGS/ -pipe / }" cmake ${cmake_args} ${configure_args} ${LIBS:+-DCMAKE_C_STANDARD_LIBRARIES="$LIBS"} ${LIBS:+-DCMAKE_CXX_STANDARD_LIBRARIES="$LIBS"} ${wrksrc}/${build_wrksrc}' exited with 1
=> ERROR: in do_configure() at common/build-style/cmake.sh:77
```
This appears to have happened after building all the dependencies, which took about a day on a two core virtual machine.
It appears something is out-of-sync, but I'm uncertain of the best way to resolve it.
prev parent reply other threads:[~2024-11-15 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 1:24 [PR PATCH] " Astate
2024-10-25 12:29 ` Astate
2024-10-25 23:36 ` [PR REVIEW] " classabbyamp
2024-10-26 0:30 ` [PR PATCH] [Updated] " Astate
2024-10-26 21:33 ` [PR REVIEW] " AnInternetTroll
2024-10-27 0:57 ` [PR PATCH] [Updated] " Astate
2024-11-12 22:46 ` ddmgh
2024-11-12 22:48 ` classabbyamp
2024-11-13 0:15 ` Astate
2024-11-13 21:43 ` classabbyamp
2024-11-15 16:15 ` ddmgh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241115161500.8AFDF2E7D7@inbox.vuxu.org \
--to=ddmgh@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).