From: Logarithmus <Logarithmus@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: xbps-src: add sccache support
Date: Thu, 06 May 2021 16:48:27 +0200 [thread overview]
Message-ID: <20210506144827.n2WlPb72OM80KJ4CnM2CgTCdDpOpGvS6FGs8KVWfP_M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30702@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
New comment by Logarithmus on void-packages repository
https://github.com/void-linux/void-packages/pull/30702#issuecomment-833583789
Comment:
> This will blow up once you run parallel builds in different masterdirs. sccache always listens on some tcp port on localhost. You would need to figure out how to either allocate a TCP port per masterdir or implement the communication via unix sockets and upstream it.
I should definitely test this scenario. I still think this PR can be merged in its current state, because `$XBPS_SCCACHE` is turned off by default. Maybe I should add a disclaimer in `README.md` about parallel builds in differrent masterdirs though.
next prev parent reply other threads:[~2021-05-06 14:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 9:33 [PR PATCH] " Logarithmus
2021-05-06 10:16 ` [PR REVIEW] " q66
2021-05-06 10:24 ` Logarithmus
2021-05-06 10:24 ` Logarithmus
2021-05-06 10:26 ` Logarithmus
2021-05-06 10:48 ` q66
2021-05-06 12:19 ` Logarithmus
2021-05-06 12:23 ` Logarithmus
2021-05-06 12:28 ` Piraty
2021-05-06 12:39 ` [PR REVIEW] " q66
2021-05-06 12:40 ` q66
2021-05-06 12:45 ` [PR PATCH] [Updated] " Logarithmus
2021-05-06 12:45 ` [PR REVIEW] " q66
2021-05-06 12:47 ` [PR PATCH] [Updated] " Logarithmus
2021-05-06 12:54 ` [PR REVIEW] " ericonr
2021-05-06 12:59 ` Duncaen
2021-05-06 13:36 ` Logarithmus
2021-05-06 13:39 ` [PR PATCH] [Updated] " Logarithmus
2021-05-06 13:39 ` [PR REVIEW] " Logarithmus
2021-05-06 14:07 ` Johnnynator
2021-05-06 14:48 ` Logarithmus [this message]
2021-05-06 14:52 ` ericonr
2021-05-06 14:52 ` ericonr
2022-05-19 2:16 ` github-actions
2022-06-03 2:11 ` [PR PATCH] [Closed]: " github-actions
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=20210506144827.n2WlPb72OM80KJ4CnM2CgTCdDpOpGvS6FGs8KVWfP_M@z \
--to=logarithmus@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).