From: Troy Dack <troy@tkdack.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ccache
Date: Sat, 14 Jun 2003 12:52:21 +1000 [thread overview]
Message-ID: <3EEA8DE5.70609@tkdack.com> (raw)
In-Reply-To: <1055531969.477.9.camel@debian>
Hasse Hagen Johansen wrote:
>Hi
>
>A couple of days ago it was recommended on this list to use ccache. I
>have now tried ccache, and I think it breaks some builds horrible. As of
>now I have tried to build mozilla-1.3-r2, and jack-cvs. Those packages
>fail with an error that the linker parser cannot understand the format
>of one of the object files. I think it would be a very good idea not
>have the ccache flag enabled by default it simply breaks normally
>working ebuilds. I think that it should be something you can set in your
>use flags if you know what you are doing.
>
>Comments welcome. It could be me just to stupid to use ccache ;-)
>
>Regards
>Hasse
>
>
>
It is a setting you can put in your FEATURES in /etc/make.conf
I've never had any problems with ccache, in fact I built mozilla-1.3 the
other day with it (and distcc) and my ccache is shared via nfs between 3
machines. I probably shouldn't share the cache, but it hasn't hurt yet!
Troy
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-06-14 2:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 19:19 [gentoo-dev] ccache Hasse Hagen Johansen
2003-06-14 2:52 ` Troy Dack [this message]
2003-06-14 8:51 ` Hasse Hagen Johansen
2003-06-14 11:39 ` bsolar
2003-06-14 11:48 ` Stuart Bouyer
[not found] <1024596482.23674.234.camel@inventor.gentoo.org>
2002-06-22 4:36 ` Felipe Ghellar
[not found] <Pine.GSO.4.44.0206201340350.19554-100000@oaktree.cisco.com>
2002-06-20 17:18 ` Felipe Ghellar
-- strict thread matches above, loose matches on Subject: below --
2002-06-20 6:13 Felipe Ghellar
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=3EEA8DE5.70609@tkdack.com \
--to=troy@tkdack.com \
--cc=gentoo-dev@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