Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] rsync fails to build
Date: Wed, 02 Apr 2014 07:53:45 +0200	[thread overview]
Message-ID: <533BA5E9.70505@mind.be> (raw)
In-Reply-To: <1D90109776E04A139DC0C95B4F945F47@JohanW7>

On 31/03/14 14:31, Sagaert Johan wrote:
>  
> Dear Thomas
> 
> I have 2 buildroot build trees, since they are run on the same user account they share the same buildroot-ccache directories.
> Could this be a cause of ccache trouble ?

 Yes. Until we solve the compilercheck problem, you should give a
different BR2_CCACHE_DIR for both trees.

 In fact, the same applies if you have different output directories for
the same architecture.

 If the architecture is different, ccache will work OK because the
compiler basename is hashed.

 Regards,
 Arnout


-- 
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:[~2014-04-02  5:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-29 13:11 [Buildroot] rsync fails to build Sagaert Johan
2014-03-29 13:30 ` Thomas Petazzoni
2014-03-29 16:39   ` Sagaert Johan
2014-03-29 17:00     ` Thomas Petazzoni
2014-03-29 22:11       ` Sagaert Johan
2014-03-29 22:20         ` Thomas Petazzoni
2014-03-31  0:36           ` Sagaert Johan
2014-03-31  8:26             ` Thomas Petazzoni
2014-03-31 12:31               ` Sagaert Johan
2014-04-02  5:53                 ` Arnout Vandecappelle [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=533BA5E9.70505@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox