Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] full rebuild and errors
Date: Tue, 28 Jan 2014 21:24:47 +0100	[thread overview]
Message-ID: <52E8120F.7080805@gmail.com> (raw)
In-Reply-To: <52E6945C.40202@mind.be>

Il 27/01/2014 18:16, Arnout Vandecappelle ha scritto:
>  I guess you mean
>
> make clean all


Yes of course, I apologize for the typo.

> This smells like it could be a ccache issue. Is it possible that you 
> had a major upgrade to your compiler since the first time you made a 
> build?

It's very unlikely because I have a Debian shell and I didn't update 
anything during the day (just few hours between the two compilations).

> Can you try with
>
> make clean all BR2_CCACHE=
>
> (or just edit your config to disable ccache).


Yeah! It did the trick!
I can't imagine it was a ccache problem because I deleted the whole 
directory and cloned again the repository from scratch - I thought it 
should reset anything to the initial state, my fault!

Thank you
Mark

  reply	other threads:[~2014-01-28 20:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26 12:07 [Buildroot] full rebuild and errors Marco Trapanese
2014-01-27 17:16 ` Arnout Vandecappelle
2014-01-28 20:24   ` Marco Trapanese [this message]
2014-01-28 22:09     ` Thomas Petazzoni
2014-01-29  7:14       ` Arnout Vandecappelle
2014-01-29  8:19         ` Marco Trapanese
2014-01-29  8:30         ` Thomas Petazzoni
2014-01-29 10:42           ` Arnout Vandecappelle
2014-01-30 13:45             ` [Buildroot] udev and serial port Marco Trapanese
2014-01-30 13:51               ` Gustavo Zacarias
2014-01-30 14:16                 ` Marco Trapanese
2014-01-30 17:19                   ` Marco Trapanese

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=52E8120F.7080805@gmail.com \
    --to=marcotrapanese@gmail.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