>From the stack trace after ctrl-c, lunch will be waiting for the child
soong_ui process to complete.  An strace of that process would be
interesting.

On Mon, Dec 18, 2017 at 4:12 PM, Alessandro Brucato <ale13br...@gmail.com>
wrote:

> This is the output of strace attached to the process in which I execute
> "lunch".
>
>
>
> <https://lh3.googleusercontent.com/-Rk-T1kCPUnA/WjhYORJYCKI/AAAAAAAAGSY/LIzqOc58jvkTpj7dowKqjz1OsKoAy0dZQCLcBGAs/s1600/strace.PNG>
>
> When "lunch" is stuck, the output of strace ends with "wait4(-1,". All the
> remaining part appears when I abort "lunch" with CTRL+C.
>
> Maybe this issue is due to the fact that I'm using a guest in Virtualbox?
>
> Il giorno lunedì 18 dicembre 2017 23:45:48 UTC+1, Colin Cross ha scritto:
>>
>> Can you capture the full output of all the stack traces?
>>
>> It's getting stuck while trying to walk all the checked-out code looking
>> for various build files.  If it was completely deadlocked then it would
>> have died on its own, so it's probably stuck in a loop somehow.
>>
>> On Mon, Dec 18, 2017 at 8:12 AM, Alessandro Brucato <ale13...@gmail.com>
>> wrote:
>>
>>> Hello, I'm trying to build the Android source code for my Hikey 960
>>> board.
>>> I'm following this video tutorial https://www.youtube.c
>>> om/watch?v=RD_NZRKiZBU in parallel to the official Android guide
>>> https://source.android.com/setup/devices#hikey-boards.
>>>
>>>
>>> Everything went fine until I reached the command "lunch
>>> hikey960-userdebug". It blocks, without returning any output. I left it
>>> "working" for 1 hour and then I aborted it (even if I know that this
>>> command should take few seconds). If I execute only "lunch" it shows the
>>> list of available build targets, and when I select "hikey960-userdebug" it
>>> blocks. When I abort it with CTRL+C, it says "Still alive, killing
>>> subprocesses" and then it shows a lot of messages referring to threads.
>>> Here is the screenshot https://ibb.co/k32KQR
>>> I noticed that also the "make" command (inside the AOSP directory) has
>>> the same behaviour.
>>>
>>>
>>> This is the list of commands I've used during the process:
>>>
>>>
>>> sudo apt-get install openjdk-7-jdk
>>>
>>> sudo apt-get install git-core gnupg flex bison gperf build-essential zip
>>> curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev
>>> x11proto-core-dev libx11-dev lib32z-dev ccache libgl1-mesa-dev
>>> libxml2-utils xsltproc unzip
>>>
>>> mkdir output
>>>
>>> export OUT_DIR_COMMON_BASE=/home/brucedh/output/
>>>
>>> mkdir ~/bin
>>>
>>> PATH=~/bin:$PATH
>>>
>>> curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
>>>
>>> chmod a+x ~/bin/repo
>>>
>>> mkdir dev
>>>
>>> cd dev
>>>
>>> mkdir hikey960
>>>
>>> cd hikey960
>>>
>>> git config --global user.name "<REDACTED>"
>>>
>>> git config --global user.email "<REDACTED>"
>>>
>>> repo init -u https://android.googlesource.com/platform/manifest -b
>>> master
>>>
>>> repo sync –j4
>>>
>>> git clone https://android.googlesource.com/kernel/hikey-linaro
>>>
>>> cd hikey-linaro
>>>
>>> git checkout -b android-hikey-linaro-4.9 origin/android-hikey-linaro-4.9
>>>
>>> make ARCH=arm64 menuconfig
>>>
>>> make ARCH=arm64 hikey960_defconfig
>>>
>>> PATH=/home/brucedh/dev/hikey960/prebuilts/gcc/linux-x86/
>>> aarch64/aarch64-linux-android-4.9/bin/:$PATH
>>>
>>> make ARCH=arm64 CROSS_COMPILE=aarch64-linux-android- -j4
>>>
>>> cp arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dtb
>>> ../device/linaro/hikey-kernel/hi3660-hikey960.dtb-4.9
>>>
>>> cp arch/arm64/boot/Image.gz ../device/linaro/hikey-kernel/
>>> Image.gz-hikey960-4.9
>>>
>>> cd ~/dev/hikey960
>>>
>>> . ./build/envsetup.sh
>>>
>>> lunch hikey960-userdebug
>>>
>>>
>>>
>>> I'm using Ubuntu 16.04 LTS as guest on Virtualbox. I tried to do all the
>>> process once again from the beginning with a new virtualbox image, but I
>>> found the same problem.
>>>
>>> Thanks in advance!
>>>
>>> --
>>> --
>>> You received this message because you are subscribed to the "Android
>>> Building" mailing list.
>>> To post to this group, send email to android-...@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> android-buildi...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/android-building?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Android Building" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to android-buildi...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to