Thanks, that worked :)
On Mon, Nov 18, 2019 at 2:16 PM 'Dan Willemsen' via Android Building <
android-building@googlegroups.com> wrote:
> I've created a change to empty out the BASH_ENV environment variable
> during the build:
>
I've created a change to empty out the BASH_ENV environment variable during
the build:
https://android-review.googlesource.com/c/platform/build/soong/+/1168864
- Dan
On Mon, Nov 18, 2019 at 10:48 AM 'Colin Cross' via Android Building <
android-building@googlegroups.com> wrote:
> I was able to
I was able to reproduce this on Fedora 30, it's something to do with the
environment BASH_ENV=/usr/share/Modules/init/bash, which is causing
arbitrary bash code that can use any binary to be run on every
non-interactive bash shell startup.
On Mon, Nov 18, 2019 at 9:50 AM Michael Goffioul
wrote:
Yes, I've already looked into that, but there's not much of a trace, e.g.:
2019/11/18 11:22:34.837088 build/soong/ui/build/sandbox_linux.go:86:
[prebuilts/build-tools/linux-x86/bin/nsjail -H android-build -e -u nobody
-g nobody -B / --disable_clone_newcgroup -- /bin/bash -c if [ $(hostname)
==
If you check out/soong.log, there should be trace logs that include the
parent processes all the way up to ninja.
It sounds like one of the existing tools that we allow through is always
trying to call manpath? Let me know what you find, we've definitely been
shrinking this list on master.
- Dan
