From: kruceter <kruceter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libgdal: update to 3.5.3
Date: Thu, 03 Nov 2022 21:40:34 +0100 [thread overview]
Message-ID: <20221103204034.jF7F7JFq9imI7m8Ics-1GSadI-KeGfhKh3GGy_XYUAs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40225@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]
New comment by kruceter on void-packages repository
https://github.com/void-linux/void-packages/pull/40225#issuecomment-1298086936
Comment:
CI builds indicate that OpenOrienteering-Mapper fails "sensor" test.
My attempts to "dig" into the issue itself brought more problems,
leading to the failing pre-build test on my side.
```
-- CMAKE_CXX_FLAGS: -DNDEBUG -fstack-clash-protection -D_FORTIFY_SOURCE=2 -O2 -mtune=generic -I/usr/x86_64-linux-gnu/usr/include -fdebug-prefix-map=/builddir/mapper-0.9.5/build=. -Wall -Wpedantic -Wextra
-- CMAKE_CXX_FLAGS_NONE:
-- CMAKE_C_FLAGS: -DNDEBUG -fstack-clash-protection -D_FORTIFY_SOURCE=2 -O2 -mtune=generic -I/usr/x86_64-linux-gnu/usr/include -fdebug-prefix-map=/builddir/mapper-0.9.5/build=. -std=c99 -Wall -Wpedantic
-- CMAKE_C_FLAGS_NONE:
-- Configuring done
CMake Error: AUTOMOC for target cove: Test run of "moc" executable "/usr/x86_64-linux-gnu/usr/lib/qt5/bin/moc" failed.
/usr/x86_64-linux-gnu/usr/lib/qt5/bin/moc -h
No such file or directory
CMake Generate step failed. Build files cannot be regenerated correctly.
=> ERROR: OpenOrienteering-Mapper-0.9.5_2: 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:75
```
~`chroot`ing into masterdir/usr/x86_64-linux-gnu and ensuring that the
"failing" binary executes correctly convince me that the problem might
be laying with my setup, although I am not sure what exactly is wrong.~
~Since I do not believe that I can solve it myself, I have disabled checks
for the time being to see what other issues the CI builder may show.~
The "sensors" check has been disabled for now.
next prev parent reply other threads:[~2022-11-03 20:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 5:27 [PR PATCH] libgdal: update to 3.5.2 kruceter
2022-10-30 6:22 ` [PR PATCH] [Updated] " kruceter
2022-10-30 9:04 ` [PR REVIEW] " classabbyamp
2022-10-30 9:04 ` classabbyamp
2022-10-30 18:09 ` [PR PATCH] [Updated] " kruceter
2022-10-30 18:12 ` [PR REVIEW] " kruceter
2022-10-31 1:37 ` kruceter
2022-10-31 1:57 ` classabbyamp
2022-10-31 12:51 ` [PR PATCH] [Updated] " kruceter
2022-10-31 12:55 ` kruceter
2022-11-01 6:06 ` kruceter
2022-11-01 6:32 ` kruceter
2022-11-01 6:33 ` kruceter
2022-11-01 6:34 ` [PR REVIEW] " classabbyamp
2022-11-01 7:15 ` kruceter
2022-11-01 11:14 ` kruceter
2022-11-01 11:35 ` [PR PATCH] [Updated] " kruceter
2022-11-01 17:59 ` [PR PATCH] [Updated] libgdal: update to 3.5.3 kruceter
2022-11-02 13:29 ` kruceter
2022-11-03 7:11 ` kruceter
2022-11-03 8:01 ` kruceter
2022-11-03 20:34 ` [PR PATCH] [Updated] " kruceter
2022-11-03 20:40 ` kruceter [this message]
2022-11-03 22:51 ` kruceter
2022-11-03 23:05 ` kruceter
2022-11-04 9:05 ` kruceter
2022-11-04 12:36 ` kruceter
2022-11-05 3:23 ` the-maldridge
2022-11-05 3:27 ` [PR PATCH] [Merged]: " classabbyamp
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=20221103204034.jF7F7JFq9imI7m8Ics-1GSadI-KeGfhKh3GGy_XYUAs@z \
--to=kruceter@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).