Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] problem with absolute paths to tools in ccache
Date: Fri, 24 Nov 2006 13:07:41 +0100	[thread overview]
Message-ID: <20061124120740.GA5505@aon.at> (raw)
In-Reply-To: <20061124105312.100310@gmx.net>

On Fri, Nov 24, 2006 at 11:53:12AM +0100, Real.Magic at gmx.de wrote:

>I have got a problem because ccache is using absolute paths to the ccache working directory and to the tools like gcc.
>
>To prevent ccache from using an absolute path to the ccache working directory, I have applied the following patch successfully:
>
>http://www.busybox.net/lists/buildroot/2006-October/000355.html

1) I don't use ccache
2) If somebody can come up with a patch that makes ccache behave like
the majority desires (or as it is intended), then bug Eric or Mike or
anybody else who uses ccache to apply it.

>But how can I prevent ccache from using absolute paths to tools like gcc?

no idea, see 1)
sorry but i can't help with this, fwiw.

  reply	other threads:[~2006-11-24 12:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-24 10:53 [Buildroot] problem with absolute paths to tools in ccache Real.Magic at gmx.de
2006-11-24 12:07 ` Bernhard Fischer [this message]
2006-11-24 14:06   ` "Matthias Gülck"
2006-11-24 14:10     ` Bernhard Fischer
2006-11-24 14:25       ` "Matthias Gülck"
2006-11-24 14:28       ` "Matthias Gülck"
2006-11-24 16:45 ` M. Edward Borasky
  -- strict thread matches above, loose matches on Subject: below --
2006-11-24 14:33 "Matthias Gülck"
2006-11-24 14:39 "Matthias Gülck"
2006-11-24 16:37 Paugam Luc

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=20061124120740.GA5505@aon.at \
    --to=rep.nop@aon.at \
    --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