From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10536] Finding non-relative paths in the ccache
Date: Mon, 22 Jan 2018 17:57:43 +0000 [thread overview]
Message-ID: <bug-10536-163-Ek9mxCuYdp@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10536-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10536
--- Comment #6 from Arnout Vandecappelle <arnout@mind.be> ---
Hm, this build failure doesn't look like it will be solved with CCACHE_BASEDIR.
Indeed, it is the *target* ccache'd compiler that generated a *.d file that
apparently still has a full path in it. I don't see how this could happen...
Possibly the issue is that this is a path that is embedded in the specs file,
and ccache will only substitute paths that get passed on the command line
(through -I etc.).
Needs more debugging...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-01-22 17:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 18:04 [Buildroot] [Bug 10536] New: Finding non-relative paths in the ccache bugzilla at busybox.net
2017-12-07 20:08 ` [Buildroot] [Bug 10536] " bugzilla at busybox.net
2017-12-07 20:15 ` bugzilla at busybox.net
2018-01-10 20:42 ` bugzilla at busybox.net
2018-01-17 22:44 ` bugzilla at busybox.net
2018-01-22 15:28 ` bugzilla at busybox.net
2018-01-22 17:57 ` bugzilla at busybox.net [this message]
2018-01-26 14:15 ` bugzilla at busybox.net
2018-01-26 14:17 ` bugzilla at busybox.net
2018-01-31 19:16 ` bugzilla at busybox.net
2018-01-31 19:29 ` bugzilla at busybox.net
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=bug-10536-163-Ek9mxCuYdp@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.