* Re: [TRACKING] glibc 2.36 (and gcc 12) build failures
2022-10-14 23:05 [ISSUE] [TRACKING] glibc 2.36 (and gcc 12) build failures paper42
@ 2022-10-31 17:31 ` dkwo
2022-10-31 17:44 ` paper42
` (11 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: dkwo @ 2022-10-31 17:31 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 182 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/39960#issuecomment-1297432010
Comment:
does the recent update to `arb` fix this?
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [TRACKING] glibc 2.36 (and gcc 12) build failures
2022-10-14 23:05 [ISSUE] [TRACKING] glibc 2.36 (and gcc 12) build failures paper42
2022-10-31 17:31 ` dkwo
@ 2022-10-31 17:44 ` paper42
2022-11-16 20:57 ` kruceter
` (10 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: paper42 @ 2022-10-31 17:44 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 218 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/39960#issuecomment-1297448035
Comment:
> does the recent update to `arb` fix this?
yes, thanks for the comment
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [TRACKING] glibc 2.36 (and gcc 12) build failures
2022-10-14 23:05 [ISSUE] [TRACKING] glibc 2.36 (and gcc 12) build failures 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
` (9 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: kruceter @ 2022-11-16 20:57 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
New comment by kruceter on void-packages repository
https://github.com/void-linux/void-packages/issues/39960#issuecomment-1317659419
Comment:
`runawk` does not build on musl with the same result.
The problem lays with `mk-configure` which has to be revbumped with gcc 12.
mk-configure has a tendency to do its work only when it was built with a compiler of the corresponding version.
If compiled with GCC 10.2, it looks for `/usr/share/mk-configure/mk/mkc_imp.cc_gcc-10.2.1.mk` and/or `/usr/share/mk-configure/mk/mkc_imp.cxx_gcc-10.2.1.mk` depending if CC or CXX are used.
If used with GCC 12.2 without getting recompiled first, the utility looks for `/usr/share/mk-configure/mk/mkc_imp.cc_gcc-12.2.0.mk` and/or `/usr/share/mk-configure/mk/mkc_imp.cxx_gcc-12.2.0.mk` and finds none because it was never built with GCC 12.
Build failure with GCC 12 on musl (x86_64-musl):
[runawk.fail.txt](https://github.com/void-linux/void-packages/files/10025637/runawk.fail.txt)
mk-configure revbump + rebuild with GCC 12:
[mk-configure-rbmp-gcc12.txt](https://github.com/void-linux/void-packages/files/10025645/mk-configure-rbmp-gcc12.txt)
Now runawk builds as expected:
[runawk.txt](https://github.com/void-linux/void-packages/files/10025648/runawk.txt)
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [TRACKING] glibc 2.36 (and gcc 12) build failures
2022-10-14 23:05 [ISSUE] [TRACKING] glibc 2.36 (and gcc 12) build failures paper42
` (2 preceding siblings ...)
2022-11-16 20:57 ` kruceter
@ 2022-11-16 21:02 ` kruceter
2022-11-17 15:22 ` wael444
` (8 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: kruceter @ 2022-11-16 21:02 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
New comment by kruceter on void-packages repository
https://github.com/void-linux/void-packages/issues/39960#issuecomment-1317659419
Comment:
`runawk` does not build on musl with the same result.
The problem lays with `mk-configure` which has to be revbumped with gcc 12.
mk-configure has a tendency to do its work only when it was built with a compiler of the corresponding version.
If built with GCC 10.2, it looks for `/usr/share/mk-configure/mk/mkc_imp.cc_gcc-10.2.1.mk` and/or `/usr/share/mk-configure/mk/mkc_imp.cxx_gcc-10.2.1.mk` depending if CC or CXX are used.
If used with GCC 12.2 without getting rebuilt first, the utility looks for `/usr/share/mk-configure/mk/mkc_imp.cc_gcc-12.2.0.mk` and/or `/usr/share/mk-configure/mk/mkc_imp.cxx_gcc-12.2.0.mk` and finds none because it was never revbumped with GCC 12.
Build failure with GCC 12 on musl (x86_64-musl):
[runawk.fail.txt](https://github.com/void-linux/void-packages/files/10025637/runawk.fail.txt)
mk-configure revbump + rebuild with GCC 12:
[mk-configure-rbmp-gcc12.txt](https://github.com/void-linux/void-packages/files/10025645/mk-configure-rbmp-gcc12.txt)
Now runawk builds as expected:
[runawk.txt](https://github.com/void-linux/void-packages/files/10025648/runawk.txt)
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [TRACKING] glibc 2.36 (and gcc 12) build failures
2022-10-14 23:05 [ISSUE] [TRACKING] glibc 2.36 (and gcc 12) build failures paper42
` (3 preceding siblings ...)
2022-11-16 21:02 ` kruceter
@ 2022-11-17 15:22 ` wael444
2022-11-17 17:26 ` paper42
` (7 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: wael444 @ 2022-11-17 15:22 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 219 bytes --]
New comment by wael444 on void-packages repository
https://github.com/void-linux/void-packages/issues/39960#issuecomment-1318795473
Comment:
glibc upstream has been updated to solve this... void should be using that.
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [TRACKING] glibc 2.36 (and gcc 12) build failures
2022-10-14 23:05 [ISSUE] [TRACKING] glibc 2.36 (and gcc 12) build failures paper42
` (4 preceding siblings ...)
2022-11-17 15:22 ` wael444
@ 2022-11-17 17:26 ` paper42
2022-11-17 18:28 ` wael444
` (6 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: paper42 @ 2022-11-17 17:26 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/39960#issuecomment-1318968525
Comment:
> glibc upstream has been updated to solve this... void should be using that.
@wael444 Do you have some more information about this? Solve what exactly? This looks like a problem with the mk-configure package that we should revbump.
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [TRACKING] glibc 2.36 (and gcc 12) build failures
2022-10-14 23:05 [ISSUE] [TRACKING] glibc 2.36 (and gcc 12) build failures paper42
` (5 preceding siblings ...)
2022-11-17 17:26 ` paper42
@ 2022-11-17 18:28 ` wael444
2022-11-19 22:39 ` oreo639
` (5 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: wael444 @ 2022-11-17 18:28 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
New comment by wael444 on void-packages repository
https://github.com/void-linux/void-packages/issues/39960#issuecomment-1319039741
Comment:
https://vasilek.cz/logs/gcc12-glibc-filtered/bad/toybox.txt fixed by:
commit glibc 3e279192749cfcae4ceebb1f21a3275e677d0561: https://github.com/bminor/glibc/archive/3e279192749cfcae4ceebb1f21a3275e677d0561.tar.gz
just try this for glibc, some of the packages would succeed to compile
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [TRACKING] glibc 2.36 (and gcc 12) build failures
2022-10-14 23:05 [ISSUE] [TRACKING] glibc 2.36 (and gcc 12) build failures paper42
` (6 preceding siblings ...)
2022-11-17 18:28 ` wael444
@ 2022-11-19 22:39 ` oreo639
2022-11-20 9:09 ` kruceter
` (4 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: oreo639 @ 2022-11-19 22:39 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 151 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39960#issuecomment-1320984658
Comment:
Thanks.
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [TRACKING] glibc 2.36 (and gcc 12) build failures
2022-10-14 23:05 [ISSUE] [TRACKING] glibc 2.36 (and gcc 12) build failures paper42
` (7 preceding siblings ...)
2022-11-19 22:39 ` oreo639
@ 2022-11-20 9:09 ` kruceter
2022-12-03 10:31 ` 7r3nzy
` (3 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: kruceter @ 2022-11-20 9:09 UTC (permalink / raw)
To: ml
[-- 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.
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [TRACKING] glibc 2.36 (and gcc 12) build failures
2022-10-14 23:05 [ISSUE] [TRACKING] glibc 2.36 (and gcc 12) build failures paper42
` (8 preceding siblings ...)
2022-11-20 9:09 ` kruceter
@ 2022-12-03 10:31 ` 7r3nzy
2022-12-03 10:44 ` 7r3nzy
` (2 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: 7r3nzy @ 2022-12-03 10:31 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 212 bytes --]
New comment by 7r3nzy on void-packages repository
https://github.com/void-linux/void-packages/issues/39960#issuecomment-1336130826
Comment:
`mono` builds with gcc-12, I think someone must've fixed this already
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [TRACKING] glibc 2.36 (and gcc 12) build failures
2022-10-14 23:05 [ISSUE] [TRACKING] glibc 2.36 (and gcc 12) build failures paper42
` (9 preceding siblings ...)
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
12 siblings, 0 replies; 14+ messages in thread
From: 7r3nzy @ 2022-12-03 10:44 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 231 bytes --]
New comment by 7r3nzy on void-packages repository
https://github.com/void-linux/void-packages/issues/39960#issuecomment-1336130826
Comment:
`mono` builds with gcc-12(tried with x86-64), I think someone must've fixed this already
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [ISSUE] [CLOSED] [TRACKING] glibc 2.36 (and gcc 12) build failures
2022-10-14 23:05 [ISSUE] [TRACKING] glibc 2.36 (and gcc 12) build failures paper42
` (10 preceding siblings ...)
2022-12-03 10:44 ` 7r3nzy
@ 2022-12-04 14:50 ` paper42
2022-12-04 14:50 ` paper42
12 siblings, 0 replies; 14+ messages in thread
From: paper42 @ 2022-12-04 14:50 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1490 bytes --]
Closed issue by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/39960
Description:
https://vasilek.cz/logs/gcc12-glibc-filtered/bad/
These are new failures from a gcc 12 glibc 2.36 world rebuild, this list doesn't include failures already found in previous musl rebuilds (https://github.com/void-linux/void-packages/issues/39809, https://github.com/void-linux/void-packages/issues/39083). These can be caused by glibc 2.36 or gcc 12 if they are not available on musl.
- [x] EternalTerminal (#40663)
- [x] arb
- [x] avr-gdb
- [x] cabbage (#40885)
- [x] catch2
- [x] cereal
- [x] clementine
- [x] cpp-hocon (#40645)
- [x] cppcodec
- [x] criu
- [x] cross-arm-none-eabi-gdb (#40887)
- [x] embree
- [x] fakechroot
- [x] fakeroot (#40644)
- [x] gamemode
- [x] gatling
- [x] ghidra (1740a52acb42507f4d86cbc5e4de3e8e97147975)
- [x] libhugetlbfs
- [x] libknet1
- [x] libowfat
- [x] libstatgrab
- [x] lxc
- [x] lxcfs
- [x] mono
- [x] mtd-utils
- [x] mtree
- [x] nethack
- [x] openmw
- [x] pam_zfscrypt
- [x] partclone
- [x] pencil2d
- [x] rawtherapee (#40692)
- [x] soci
- [x] stepmania (#40783)
- [x] systemtap
- [x] tcc #40900
- [x] tracebox (#40759)
- [x] wren-cli
- [x] xdm
fixed by rebuilding mk-configure
- [x] runawk
- [x] libmaa
fixed by using the glibc stable release branch instead of the 3.36 release
- [x] bootchart2
- [x] toybox
- [x] autofs
- [x] hwinfo
- [x] snapraid
- [x] x2goclient
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [TRACKING] glibc 2.36 (and gcc 12) build failures
2022-10-14 23:05 [ISSUE] [TRACKING] glibc 2.36 (and gcc 12) build failures paper42
` (11 preceding siblings ...)
2022-12-04 14:50 ` [ISSUE] [CLOSED] " paper42
@ 2022-12-04 14:50 ` paper42
12 siblings, 0 replies; 14+ messages in thread
From: paper42 @ 2022-12-04 14:50 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 148 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/39960#issuecomment-1336431241
Comment:
done
^ permalink raw reply [flat|nested] 14+ messages in thread