From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] ebuild: look for ccache symlinks in /usr/lib/ccache/bin
Date: Sat, 24 Sep 2016 08:09:55 -0400 [thread overview]
Message-ID: <CAJ0EP41WycSSEHDFP+AwbZHCWno-4=+fpp0VNnsKiJvDOrsJxQ@mail.gmail.com> (raw)
In-Reply-To: <CAMiTYSpZp4d5G3CGdpPy4pAwor+HZ2hTPP9VX8OUe1bRPX2MHg@mail.gmail.com>
On Sat, Sep 24, 2016 at 3:37 AM, Zac Medico <zmedico@gentoo.org> wrote:
> On Fri, Sep 23, 2016 at 7:55 PM, Mike Gilbert <floppym@gentoo.org> wrote:
>> ccache-config has been installing the symlinks there since Nov 2014.
>>
>> Bug: https://bugs.gentoo.org/509956
>> Bug: https://bugs.gentoo.org/594982
>> ---
>> pym/portage/package/ebuild/prepare_build_dirs.py | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/pym/portage/package/ebuild/prepare_build_dirs.py b/pym/portage/package/ebuild/prepare_build_dirs.py
>> index 7fdac74..808e77d 100644
>> --- a/pym/portage/package/ebuild/prepare_build_dirs.py
>> +++ b/pym/portage/package/ebuild/prepare_build_dirs.py
>> @@ -154,7 +154,7 @@ def _prepare_features_dirs(mysettings):
>>
>> features_dirs = {
>> "ccache":{
>> - "path_dir": "%s/usr/%s/ccache/bin" % (EPREFIX, libdir),
>> + "path_dir": "%s/usr/lib/ccache/bin" % EPREFIX,
>> "basedir_var":"CCACHE_DIR",
>> "default_dir":os.path.join(mysettings["PORTAGE_TMPDIR"], "ccache"),
>> "always_recurse":False},
>> --
>> 2.10.0
>
> The /usr/lib/ccache/bin code lives in doebuild_environment now:
>
> https://gitweb.gentoo.org/proj/portage.git/commit/?id=96338b8a2add3ab5f7f77fef41570807374771e3
>
Got it. Thanks for the fix!
prev parent reply other threads:[~2016-09-24 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 2:55 [gentoo-portage-dev] [PATCH] ebuild: look for ccache symlinks in /usr/lib/ccache/bin Mike Gilbert
2016-09-24 7:37 ` Zac Medico
2016-09-24 12:09 ` Mike Gilbert [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='CAJ0EP41WycSSEHDFP+AwbZHCWno-4=+fpp0VNnsKiJvDOrsJxQ@mail.gmail.com' \
--to=floppym@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.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