From: kruceter <kruceter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [TRACKING] glibc 2.36 (and gcc 12) build failures
Date: Wed, 16 Nov 2022 21:57:25 +0100 [thread overview]
Message-ID: <20221116205725.mcACsZk18wLBQoORN5guvvXwNmW9uAow6n48Im53iqo@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: 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)
next prev parent reply other threads:[~2022-11-16 20:57 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 [this message]
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 ` [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=20221116205725.mcACsZk18wLBQoORN5guvvXwNmW9uAow6n48Im53iqo@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).