From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] ccache: missing symlinks for x86_64-unknown-linux-gnu-*
Date: Sat, 16 Jul 2022 04:13:22 +0200 [thread overview]
Message-ID: <20220716021322.k1UERd4iXDNRzKGXB1faGfLi2qQn7sp_Z3HvtX-oGfQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36379@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
Closed issue by tornaria on void-packages repository
https://github.com/void-linux/void-packages/issues/36379
Description:
Package `gcc-10.2.1pre1_3` ships binaries like `/usr/bin/x86_64-unknown-linux-gnu-gcc`, etc. However, `ccache-4.5.1_2` doesn't ship symlinks for these binaries.
One way this issue shows up is:
- In python3 sysconfig has `CC='x86_64-unknown-linux-gnu-gcc -pthread'`
- Building python extension modules (using setuptools) picks CC from sysconfig
- since ccache doesn't include a symlink for `x86_64-unknown-linux-gnu-gcc` the ccache is bypassed, in spite `/usr/lib/ccache/bin/` being in PATH.
A possible workaround would be to add symlinks for `x86_64-unknown-linux-gnu-gcc` etc in ccache.
NOTE: the cache entries are tagged by the compiler filename, so `gcc` and `x86_64-unknown-linux-gnu-gcc` would NOT share the cache (even if the compilers are the same, as in hardlinks of each other). I think this should not be a problem, since the same build system would use the same binary name.
Another (minor) issue is that `ccache` ships symlinks for `*-cc` compilers, but the gcc packages don't ship those (except for `/usr/bin/cc` which is a symlink to `/usr/bin/gcc`).
The same issue may happen for `x86_64-linux-musl-gcc`, etc. which are also not included in ccache.
CC: @Gottox
prev parent reply other threads:[~2022-07-16 2:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 16:24 [ISSUE] " tornaria
2022-07-01 2:15 ` github-actions
2022-07-16 2:13 ` github-actions [this message]
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=20220716021322.k1UERd4iXDNRzKGXB1faGfLi2qQn7sp_Z3HvtX-oGfQ@z \
--to=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).