Can't build Android (AOSP) after recent updates [SOLVED]

mitch_feaster · 2013-08-30 00:41:54

Is anyone using Arch for AOSP development? I was using it for a few months but a recent update appears to have broken the jdk... I'm using jdk-6 and make-3.81 from AUR since that is the suggested environment from Google.

Could someone confirm whether things are broken by following the instructions here: http://source.android.com/source/downloading.html. I've verified that building AOSP no longer works on my desktop as well as on a fresh Arch VM in VirtualBox.

The error message I get is:

[mitchelh@mitchelh-linux aosp]$ source build//envsetup.sh 
including device/ti/panda/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/lge/mako/vendorsetup.sh
including device/asus/tilapia/vendorsetup.sh
including device/asus/flo/vendorsetup.sh
including device/asus/deb/vendorsetup.sh
including device/asus/grouper/vendorsetup.sh
including device/samsung_slsi/arndale/vendorsetup.sh
including device/samsung/manta/vendorsetup.sh
including device/samsung/toroplus/vendorsetup.sh
including device/samsung/maguro/vendorsetup.sh
including device/samsung/toro/vendorsetup.sh
including sdk/bash_completion/adb.bash
[mitchelh@mitchelh-linux aosp]$ lunch full-eng

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3.2.1.000.000
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.10.9-1-ARCH-x86_64-with-glibc2.2.5
HOST_BUILD_TYPE=release
BUILD_ID=OPENMASTER
OUT_DIR=out
============================================

[mitchelh@mitchelh-linux aosp]$ which make
/opt/make-3.81/bin/make
[mitchelh@mitchelh-linux aosp]$ make -j4
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3.2.1.000.000
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.10.9-1-ARCH-x86_64-with-glibc2.2.5
HOST_BUILD_TYPE=release
BUILD_ID=OPENMASTER
OUT_DIR=out
============================================
Checking build tools versions...
************************************************************
You are attempting to build with the incorrect version
of javac.
 
Your version is: #.
The correct version is: 1.6.
 
Please follow the machine setup instructions at
    https://source.android.com/source/download.html
************************************************************
build/core/main.mk:183: *** stop.  Stop.

It's erroring out because javac -version crashing and burning. I can reproduce the javac crash with the following simple makefile:

[mitchelh@mitchelh-linux aosp]$ cat ~/java.mk
all:
        javac -version
[mitchelh@mitchelh-linux aosp]$ make-3.81 -f ~/java.mk
javac -version
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00002b3b1042101b, pid=16761, tid=47560005850880
#
# JRE version: 6.0_51-b09
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.51-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# J  java.lang.String.indexOf(II)I
#
# An error report file with more information is saved as:
# /local/mnt/workspace/mitchelh/aosp/hs_err_pid16761.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
make-3.81: *** [all] Aborted (core dumped)

Note that when I use `make' from my system (as opposed to make-3.81) I don't get this error:

[mitchelh@mitchelh-linux aosp]$ make -f ~/java.mk
javac -version
javac 1.6.0_51

Does anyone have any idea what could have been updated that would cause jdk-6 and make-3.81 to no longer work together? It just stopped working within the last few weeks...

Last edited by mitch_feaster (2013-09-04 19:43:54)

seanmcneil3 · 2013-08-31 04:43:05

This is a problem I see on Fedora as well. It appears that kernel 3.10.9 has broken something in x86_64 support of Sun Java 6. You can get around the problem by using the i586 version of Sun Java 6 or downgrading your kernel.

I opted to go with the 32bit Sun Java SDK. There doesn't seem to be any penalty in build time and perhaps just a very slight improvement.

ItachiSan · 2013-09-02 08:19:44

I've the same problem.
If I downgrade the kernel, I can't boot into DM; that sucks because my laptop backlight died and I'm now using an external monitor... in which I can't see anything.
Also, as mantainer of jre6-compat, I built a 32 bit version of it but I can't install it.

So, this is my help request:
- A working tutorial for downgrading Arch kernel (the Wiki idea does not work, yep, I searched there)
- A way to force pacman installing 32 bit package (kinda 'ignore architecture' but I didn't found it)

Thanks.

ItachiSan · 2013-09-02 14:24:01

Just solved.
The easy way:
Install linux-lts and nvidia-lts (last one if you're using NVIDIA proprietary drivers).
On LTS kernel no errors regarding Java 6. Bye, hope this help you

mitch_feaster · 2013-09-04 19:43:26

Looks like this is resolved in kernel version 3.10.10. I updated this morning and can now compile AOSP again!

[2013-09-04 12:11] [PACMAN] upgraded linux (3.10.9-1 -> 3.10.10-1)

Thanks to everyone who piped in. Pretty crazy that the kernel could break java...

Arch Linux

#1 2013-08-30 00:41:54

Can't build Android (AOSP) after recent updates [SOLVED]

#2 2013-08-31 04:43:05

Re: Can't build Android (AOSP) after recent updates [SOLVED]

#3 2013-09-02 08:19:44

Re: Can't build Android (AOSP) after recent updates [SOLVED]

#4 2013-09-02 14:24:01

Re: Can't build Android (AOSP) after recent updates [SOLVED]

#5 2013-09-04 19:43:26

Re: Can't build Android (AOSP) after recent updates [SOLVED]

Board footer