public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Upgrade Question
Date: Sat, 2 Nov 2013 09:35:52 +0000	[thread overview]
Message-ID: <20131102093552.0574228b@digimed.co.uk> (raw)
In-Reply-To: <20131102092738.4aec7562@digimed.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]

On Sat, 2 Nov 2013 09:27:38 +0000, Neil Bothwick wrote:

> > Maybe you should consider to use ccache. It considerable reduces the
> > merge time if you have to rebuild a package.  
> 
> It also creates elusive build failures with some packages, which is why
> I stopped using it.
> 
> >      Tue Oct 22 22:05:31 2013 >>> app-office/libreoffice-4.1.2.3
> >        merge time: 1 hour, 24 minutes and 27 seconds.
> > 
> >      Fri Nov  1 19:06:17 2013 >>> app-office/libreoffice-4.1.2.3
> >        merge time: 9 minutes and 5 seconds.  
> 
> Impressive, I think I'll try enabling it for specific packages that will
> benefit and don't cause problems.

On the other hand, after reading man make.conf, maybe it is not such a
good idea except in very limited cases.

Warning: This feature is known to cause numerous compilation failures.
Sometimes ccache will retain stale code objects or corrupted files, which
can lead to packages that cannot be emerged. If this happens (if you
receive errors like "File not recognized: File truncated"), try
recompiling the application with ccache disabled before reporting a bug.
Unless you are doing development work, do not enable ccache.

That reads more like an instruction than a recommendation.


-- 
Neil Bothwick

Sarchasm : The gulf between the author of sarcastic wit and the person
who doesn't get it.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-11-02  9:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 14:19 [gentoo-user] Upgrade Question Silvio Siefke
2013-11-01 20:40 ` Alan McKinnon
2013-11-01 23:31   ` Silvio Siefke
2013-11-02  1:19     ` Alan McKinnon
2013-11-02  2:38 ` wabenbau
2013-11-02  9:27   ` Neil Bothwick
2013-11-02  9:35     ` Neil Bothwick [this message]
2013-11-02 10:55       ` Silvio Siefke
2013-11-02 13:24         ` wabenbau
2013-11-02 15:31           ` Silvio Siefke
2013-11-02 13:01       ` wabenbau

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=20131102093552.0574228b@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@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