All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] still trusting ccache ?
Date: Tue, 26 Nov 2013 23:11:22 +0100	[thread overview]
Message-ID: <52951C8A.5030603@mind.be> (raw)
In-Reply-To: <DD0F4606257B467E8A4CA405E36B5548@JohanW7>

On 25/11/13 22:13, Sagaert Johan wrote:
>
> Hi all;
>
> Last weekend I had an strange build error building libglib when ccache was enabled:
> (something thread related)
>
> - A clean build with ccache on  -> Failed
> - A clean build with ccache off -> Ok
> - Deleted the whole buildroot-ccache directory tree
> - A clean build with ccache on -> Ok !!

  Is it possible that you changed compiler? We have disabled hashing the 
compiler in ccache about a year ago, but the result of that is that the 
cached results are wrong when you switch to a different compiler.

  One big problem is that in the current situation, changing the compiler 
isn't even detected if you switch output directory. Fortunately, ccache 
still hashes the basename of the compiler, so when you switch 
architectures, ccache will not use the wrong object files.

  There has been a discussion about this a couple of weeks ago [1] so the 
situation will hopefully change again in the near future.

[1] http://lists.busybox.net/pipermail/buildroot/2013-November/083028.html


> In my build I only gain 3 minutes (10%) in time.

  If you don't gain anything, there's certainly no point to use ccache of 
course. Other people have reported much larger gains.


> I have some doubts on trusting ccache after this experience.
>
> So I think that some un-reproducable build errors could be ccache related as well.

  I don't think that any of the autobuilders use ccache. Though perhaps 
they should, so we would detect these problems. But at the moment it 
wouldn't be a good idea because we know it would fail :-)

>
> PS I noticed that besides .buildroot-ccache there is also a .ccache created when building.

  Hm, that's strange...


  Regards,
  Arnout

>
> Regards
> Sagaert Johan
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
>


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-11-26 22:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 21:13 [Buildroot] still trusting ccache ? Sagaert Johan
2013-11-26 22:11 ` Arnout Vandecappelle [this message]
2013-11-26 23:01   ` Yann E. MORIN
2013-11-27  9:43   ` Sagaert Johan

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=52951C8A.5030603@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.