From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10536] New: Finding non-relative paths in the ccache
Date: Mon, 04 Dec 2017 18:04:35 +0000 [thread overview]
Message-ID: <bug-10536-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10536
Bug ID: 10536
Summary: Finding non-relative paths in the ccache
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: mhirota at impinj.com
CC: buildroot at uclibc.org
Target Milestone: ---
It appears that non-relative paths are leaking into the buildroot ccache
despite the default BR2_CCACHE_USE_BASEDIR=y.
Here are my steps to demonstrate this:
$ git clone git://git.buildroot.net/buildroot
$ cd buildroot
$ make zynq_zybo_defconfig
$ make menuconfig
$ # Build options -->
$ # [*] Enable compiler cache
$ # < Save > and < Exit > back to prompt
$ make
At this point, I grep the ccache for anything that starts with "/home":
$ grep -r --include "*.d" "^\/home" $HOME/.buildroot-ccache/ | wc -l
647
I was expecting this to be zero.
Just to confirm some assumptions:
$ grep -r --include "*.d" "^\.\." $HOME/.buildroot-ccache/ | wc -l
60840
$ grep CCACHE .config
BR2_CCACHE=y
BR2_CCACHE_DIR="$(HOME)/.buildroot-ccache"
BR2_CCACHE_INITIAL_SETUP=""
BR2_CCACHE_USE_BASEDIR=y
# BR2_PACKAGE_CCACHE is not set
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-12-04 18:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 18:04 bugzilla at busybox.net [this message]
2017-12-07 20:08 ` [Buildroot] [Bug 10536] Finding non-relative paths in the ccache 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
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@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox