Ernest Zaslavsky
Ernest Zaslavsky
> It is usually useful to run bazel with `-s --sandbox_debug --verbose_failures` and include the output from this. [sandbox_debug.txt](https://github.com/bazelbuild/bazel/files/5245181/sandbox_debug.txt) here you go
> My guess is that bazel sandboxing is blocking access. If that is the case, try building with ` --sandbox_writable_path=$HOME/.ccache` > > Your workaround using `sudo` suggests sandboxing may not...
`sudo chown -R $USER:$USER ~/.ccache` same result `bazel shutdown` same result `bazel build --spawn_strategy=standalone //tcmalloc/...` worked as expected Dont get it, am I the only one who have a problem...
worked too
then it is odd the problem is not easily searchable on the net, since it sounds as something quite usual. BTW, where is I'm whitelisting `.ccache` folder? I dont want...
Whatever discoverable by google search will do, I guess
Same here. Did you find a way to solve this problem?
it depends. do you consider using these constants as something legitimate user would use? If yes, no need for `internal`, on the other hand if you consider such a behaviour...
Wanted to add it to `vcpkg` but while the fate of the problem is questionable I will refrain from that. Please keep us posted if it gonna be revived
Correct, exclusion from build can be set per single file. Moreover, user can set "content type" on a file, so, you cant trust file extension. Thats it, there were no...