From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [TRACKING] glibc 2.36 (and gcc 12) build failures
Date: Sun, 04 Dec 2022 15:50:47 +0100 [thread overview]
Message-ID: <20221204145047.hBFmC2M7PiXK76JJdf_bRkjSlze3Q_pbXlJUVAKpU48@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: 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
next prev parent reply other threads:[~2022-12-04 14:50 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
2022-12-03 10:31 ` 7r3nzy
2022-12-03 10:44 ` 7r3nzy
2022-12-04 14:50 ` paper42 [this message]
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=20221204145047.hBFmC2M7PiXK76JJdf_bRkjSlze3Q_pbXlJUVAKpU48@z \
--to=paper42@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).