From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] rsync fails to build
Date: Mon, 31 Mar 2014 10:26:04 +0200 [thread overview]
Message-ID: <20140331102604.49ccba2b@skate> (raw)
In-Reply-To: <F9B5E559611E4C1580A5E85C9C0023A7@JohanW7>
Dear Sagaert Johan,
On Mon, 31 Mar 2014 02:36:43 +0200, Sagaert Johan wrote:
> Yes , I can confirm rsync builds with the ccache disabled.
So seems like you changed some toolchain options, or some other thing,
and ccache is re-using some invalid previous cache entries. We know we
have some things to improve on the ccache front, a few patches have
been floating around for some time.
> I have kept the 2 rync build dirs in case they could be of any use.
I guess comparing the two config.log files will help, but I'm not sure
I want to debug a problem related to the invalid re-use of ccache
results.
> As a sidenote :
> nettle sometimes (1 on 20 ) throws a build error, and just starting make again without actually removing
> its build directory just resumes the build without error.
This looks like a parallel build issue...
> It never gives an error when the ccache is off.
... but it should also occur with ccache I believe, unless maybe the
speed-up provided by ccache "hides" the parallel build issue. I don't
think we have seen nettle build issues in the autobuilders that looked
like parallel build problems, though.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-31 8:26 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 [this message]
2014-03-31 12:31 ` Sagaert Johan
2014-04-02 5:53 ` Arnout Vandecappelle
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=20140331102604.49ccba2b@skate \
--to=thomas.petazzoni@free-electrons.com \
--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