Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] cdrkit: fix build with ccache
Date: Mon, 24 Jan 2011 17:08:17 +0100	[thread overview]
Message-ID: <20110124170817.628499e6@surf> (raw)
In-Reply-To: <20110120202551.3757C8B537@busybox.osuosl.org>

Hello,

On Thu, 20 Jan 2011 21:23:23 +0100
Peter Korsgaard <jacmet@sunsite.dk> wrote:

> Cmake gets confused about ccache, so don't use ccache for cmake builds.

Which problems did you had exactly ?

While this is obviously the right short-term fix, it's a bit of a shame
of CMake doesn't play well with ccache, so maybe it's something I could
raise on the CMake mailing-list.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-01-24 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 20:23 [Buildroot] [git commit master 1/1] cdrkit: fix build with ccache Peter Korsgaard
2011-01-24 16:08 ` Thomas Petazzoni [this message]
2011-01-24 16:14   ` Peter Korsgaard
2011-01-24 16:55     ` Thomas Petazzoni

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=20110124170817.628499e6@surf \
    --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