From: d4r1us-drk <d4r1us-drk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: packages broken by cmake build-style change
Date: Sun, 24 Dec 2023 23:08:36 +0100 [thread overview]
Message-ID: <20231224220836.RMgaXvTn1Ikv3XojO-dIz0KfMhogva5lxPPyhcI4PBU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45679@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2774 bytes --]
New comment by d4r1us-drk on void-packages repository
https://github.com/void-linux/void-packages/issues/45679#issuecomment-1868601731
Comment:
In my case, adding cmake to hostmakedepends didn't result in the package building correctly and I don't really know why.
```
=> ueberzugpp-2.9.2_1: installing host dependencies: pkg-config-0.29.2_3 cmake-3.27.6_1 cmake-bootstrap-3.27.6_1 ninja-1.11.1_4 ...
=> ueberzugpp-2.9.2_1: installing target dependencies: chafa-devel-1.12.5_1 extra-cmake-modules-5.112.0_1 libopencv-devel-4.6.0_6 libsixel-devel-1.10.3_1 libvips-devel-8.14.4_2 openssl-devel-3.1.4_2 tbb-devel-2020.U3_2 wayland-devel-1.22.0_1 wayland-protocols-1.32_1 xcb-util-image-devel-0.4.1_1 xcb-util-renderutil-devel-0.3.10_1 ...
=> ueberzugpp-2.9.2_1: running pre-configure hook: 00-gnu-configure-asneeded ...
=> ueberzugpp-2.9.2_1: running pre-configure hook: 01-override-config ...
=> ueberzugpp-2.9.2_1: running pre-configure hook: 02-script-wrapper ...
=> ueberzugpp-2.9.2_1: running do_configure ...
CMake Deprecation Warning at build/_deps/cli11-src/CMakeLists.txt:1 (cmake_minimum_required):
Compatibility with CMake < 3.5 will be removed from a future version of
CMake.
Update the VERSION argument <min> value or use a ...<max> suffix to tell
CMake that the project does not need compatibility with older versions.
CMake Deprecation Warning at build/_deps/nlohmann_json-src/CMakeLists.txt:1 (cmake_minimum_required):
Compatibility with CMake < 3.5 will be removed from a future version of
CMake.
Update the VERSION argument <min> value or use a ...<max> suffix to tell
CMake that the project does not need compatibility with older versions.
-- Using the multi-header code from /builddir/ueberzugpp-2.9.2/build/_deps/nlohmann_json-src/include/
-- Version: 10.1.0
-- Build type: None
-- Build spdlog: 1.12.0
-- Build type: None
CMake Error at /usr/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
Could NOT find OpenGL (missing: OPENGL_opengl_LIBRARY OPENGL_glx_LIBRARY
OPENGL_INCLUDE_DIR)
Call Stack (most recent call first):
/usr/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-3.27/Modules/FindOpenGL.cmake:545 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:110 (find_package)
-- Configuring incomplete, errors occurred!
=> ERROR: ueberzugpp-2.9.2_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
```
next prev parent reply other threads:[~2023-12-24 22:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-20 0:25 [ISSUE] " classabbyamp
2023-08-20 0:30 ` sgn
2023-08-20 2:51 ` classabbyamp
2023-08-22 21:24 ` motorto
2023-08-29 14:10 ` sgn
2023-12-24 19:35 ` d4r1us-drk
2023-12-24 21:17 ` 0x5c
2023-12-24 22:08 ` d4r1us-drk [this message]
2023-12-24 22:11 ` d4r1us-drk
2023-12-24 22:53 ` 0x5c
2023-12-25 1:00 ` d4r1us-drk
2023-12-25 1:07 ` classabbyamp
2023-12-25 1:56 ` sgn
2023-12-25 2:10 ` 0x5c
2023-12-25 2:13 ` d4r1us-drk
2023-12-25 2:15 ` sgn
2023-12-25 2:16 ` sgn
2023-12-25 2:17 ` sgn
2023-12-25 2:17 ` sgn
2023-12-25 2:19 ` d4r1us-drk
2023-12-25 3:03 ` 0x5c
2023-12-25 3:07 ` d4r1us-drk
2024-04-18 7:33 ` [ISSUE] [CLOSED] " classabbyamp
2024-04-18 7:33 ` classabbyamp
2024-04-19 4:43 ` ibhagwan
2024-04-20 20:24 ` d4r1us-drk
2024-04-20 20:25 ` d4r1us-drk
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=20231224220836.RMgaXvTn1Ikv3XojO-dIz0KfMhogva5lxPPyhcI4PBU@z \
--to=d4r1us-drk@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).