Github messages for voidlinux
 help / color / mirror / Atom feed
From: kruceter <kruceter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [TRACKING] glibc 2.36 (and gcc 12) build failures
Date: Sun, 20 Nov 2022 10:09:27 +0100	[thread overview]
Message-ID: <20221120090927.WBQNNvcHGhY5OO9PV97Iw-VCMXfPKwL4CgFzRo7THoU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39960@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 3637 bytes --]

New comment by kruceter on void-packages repository

https://github.com/void-linux/void-packages/issues/39960#issuecomment-1321076198

Comment:
# cpp-hocon

Since I was not able to find Michal's logs about this package, I may include this one: [cpp-hocon_fail.txt](https://github.com/void-linux/void-packages/files/10049155/cpp-hocon_fail.txt)

Errors clearly indicate that `catch.hpp` is not found. Despite including `catch2` and fixing header inclusion to `catch2/catch.hpp`, adventures do not end here:

```
[50/68] Building CXX object lib/tests/CMakeFiles/libcpp-hocon_test.dir/concatenation_test.cc.o
FAILED: lib/tests/CMakeFiles/libcpp-hocon_test.dir/concatenation_test.cc.o
/usr/bin/g++ -DBOOST_ALL_DYN_LINK -DBOOST_ATOMIC_DYN_LINK -DBOOST_ATOMIC_NO_LIB -DBOOST_CHRONO_DYN_LINK -DBOOST_CHRONO_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_DATE_TIME_NO_LIB -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_FILESYSTEM_NO_LIB -DBOOST_LOCALE_DYN_LINK -DBOOST_LOCALE_NO_LIB -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_NO_LIB -DBOOST_REGEX_DYN_LINK -DBOOST_REGEX_NO_LIB -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_DEPRECATED -DBOOST_SYSTEM_NO_LIB -DBOOST_THREAD_DYN_LINK -DBOOST_THREAD_NO_LIB -DLEATHERMAN_I18N -DLEATHERMAN_LOGGING_NAMESPACE=\"puppetlabs.cpp-hocon\" -DLEATHERMAN_USE_LOCALES -DPROJECT_DIR=\"/builddir/cpp-hocon-0.3.0/build\" -DPROJECT_NAME=\"cpp-hocon\" -I/builddir/cpp-hocon-0.3.0/lib/inc -I/builddir/cpp-hocon-0.3.0/lib/tests/catch/include -Wextra -std=c++11 -Wall -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas -Wno-missing-field-initializers -Werror -Wno-maybe-uninitialized -DNDEBUG -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2    -fdebug-prefix-map=/builddir/cpp-hocon-0.3.0/build=. -MD -MT lib/tests/CMakeFiles/libcpp-hocon_test.dir/concatenation_test.cc.o -MF lib/tests/CMakeFiles/libcpp-hocon_test.dir/concatenation_test.cc.o.d -o lib/tests/CMakeFiles/libcpp-hocon_test.dir/concatenation_test.cc.o -c /builddir/cpp-hocon-0.3.0/lib/tests/concatenation_test.cc
In file included from /builddir/cpp-hocon-0.3.0/lib/tests/concatenation_test.cc:1:
/builddir/cpp-hocon-0.3.0/lib/tests/concatenation_test.cc: In function 'void C_A_T_C_H_T_E_S_T_0()':
/builddir/cpp-hocon-0.3.0/lib/tests/concatenation_test.cc:300:9: error: cannot declare reference to 'struct hocon::config_exception&', which is not a typedef or a template type argument
  300 |         REQUIRE_THROWS_AS(
      |         ^~~~~~~~~~~~~~~~~
/builddir/cpp-hocon-0.3.0/lib/tests/concatenation_test.cc:300:9: error: 'const' qualifiers cannot be applied to 'hocon::config_exception&'
/builddir/cpp-hocon-0.3.0/lib/tests/concatenation_test.cc:309:9: error: cannot declare reference to 'struct hocon::config_exception&', which is not a typedef or a template type argument
  309 |         REQUIRE_THROWS_AS(
      |         ^~~~~~~~~~~~~~~~~
/builddir/cpp-hocon-0.3.0/lib/tests/concatenation_test.cc:309:9: error: 'const' qualifiers cannot be applied to 'hocon::config_exception&'
[51/68] Building CXX object lib/CMakeFiles/libprojectsrc.dir/src/config_value_factory.cc.o
[52/68] Building CXX object lib/tests/CMakeFiles/libcpp-hocon_test.dir/config_document_parser_test.cc.o
[53/68] Building CXX object lib/CMakeFiles/libprojectsrc.dir/src/values/config_concatenation.cc.o
ninja: build stopped: subcommand failed.
=> ERROR: cpp-hocon-0.3.0_4: do_build: '${make_cmd} ${makejobs} ${make_build_args} ${make_build_target}' exited with 1
=> ERROR:   in do_build() at common/build-style/cmake.sh:93
```

This problem persists with musl-based environment the same way, too.

  parent reply	other threads:[~2022-11-20  9:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 23:05 [ISSUE] " paper42
2022-10-31 17:31 ` dkwo
2022-10-31 17:44 ` paper42
2022-11-16 20:57 ` kruceter
2022-11-16 21:02 ` kruceter
2022-11-17 15:22 ` wael444
2022-11-17 17:26 ` paper42
2022-11-17 18:28 ` wael444
2022-11-19 22:39 ` oreo639
2022-11-20  9:09 ` kruceter [this message]
2022-12-03 10:31 ` 7r3nzy
2022-12-03 10:44 ` 7r3nzy
2022-12-04 14:50 ` [ISSUE] [CLOSED] " paper42
2022-12-04 14:50 ` paper42

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=20221120090927.WBQNNvcHGhY5OO9PV97Iw-VCMXfPKwL4CgFzRo7THoU@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).