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)
==
Pie was API version 28, so `BOARD_VNDK_VERSION := current` should give you
a v28 vndk. The v27 that comes with Pie is just the prebuilts so that you
can run older vendor images.
- Dan
On Mon, Nov 18, 2019 at 9:34 AM M.S. Mac-Donald
wrote:
> Hello,
>
> I'm trying to build AOSP branch:
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
Hello,
I'm trying to build AOSP branch: android-9.0.0_r46 for my device (Xiaomi mi
A3). This version of android comes with vndk v27. But the board however
supports v28 . How do we get vndk 28 working for android pie? Xiaomi has
done it, but during the build errors when i use v28... How do we
> Please manage the thing right, Google!
I'm not sure if comments like that are helpful.
Maybe there is a valid reason not to touch the SPL when google has not
published a device release from a given tag, or maybe it is just a
process issue (e.g. may be the release manager is in charge of
