Hi everyone,
I've been an XDA reader for a few years and up until now just flashed new roms every month or two to keep my S2 alive.
I just registered on XDA after deciding to try building roms from source. I have a i9100 and thought the easiest thing to try first was to compile an ordinary Lineage 14.1 rom without modification.
So, I installed ubuntu 16.04 LTS as the OS(not VM), then as per the instructions on the Lineage page, installed the SDK, build packages, and JDK. Then I executed the repo binary and put ~/bin in the correct path and updated the environment. After this I did repo init and repo sync. I tried breakfast at this stage which failed, but after extracting proprietry blobs from the device, breakfast succeeded.
After this I used croot and brunch, but I get these errors:
Code:
build/core/binary.mk:1253: external/deqp/Android.mk: libdeqp: Unused source files: \
build/core/binary.mk:1253: external/pdfium/third_party/pdfiumbigint.mk: libpdfiumbigint: Unused source files: bigint/BigInteger.cc bigint/BigIntegerUtils.cc bigint/BigUnsigned.cc bigint/BigUnsignedInABase.cc
build/core/package_internal.mk:143: Empty argument supplied to find-subdir-assets
find: ‘/home/Clyde00/android/lineage/out/target/common/obj/SHARED_LIBRARIES/libwifi-hal-mock_intermediates’: No such file or directory
build/core/package_internal.mk:143: Empty argument supplied to find-subdir-assets
build/core/base_rules.mk:183: *** vendor/samsung/galaxys2-common/proprietary: MODULE.TARGET.SHARED_LIBRARIES.libUMP already defined by hardware/samsung/exynos4/hal/libUMP.
build/core/ninja.mk:166: recipe for target '/home/Clyde00/android/lineage/out/build-lineage_i9100.ninja' failed
make: *** [/home/Clyde00/android/lineage/out/build-lineage_i9100.ninja] Error 1
make: Leaving directory '/home/Clyde00/android/lineage'
#### make failed to build some targets (11 seconds) ####
At this point I am stuck. I'm sure there is something simple I'm missing; I've been searching for answers for the last few days and haven't been able to come up with anything to fix these errors. I'm thinking something needs to be added to roomservice.xml or something. I'm a bit lost. Any help would be much appreciated.
Clyde00 said:
Hi everyone,
I've been an XDA reader for a few years and up until now just flashed new roms every month or two to keep my S2 alive.
I just registered on XDA after deciding to try building roms from source. I have a i9100 and thought the easiest thing to try first was to compile an ordinary Lineage 14.1 rom without modification.
So, I installed ubuntu 16.04 LTS as the OS(not VM), then as per the instructions on the Lineage page, installed the SDK, build packages, and JDK. Then I executed the repo binary and put ~/bin in the correct path and updated the environment. After this I did repo init and repo sync. I tried breakfast at this stage which failed, but after extracting proprietry blobs from the device, breakfast succeeded.
After this I used croot and brunch, but I get these errors:
At this point I am stuck. I'm sure there is something simple I'm missing; I've been searching for answers for the last few days and haven't been able to come up with anything to fix these errors. I'm thinking something needs to be added to roomservice.xml or something. I'm a bit lost. Any help would be much appreciated.
Click to expand...
Click to collapse
I'm at work atm... I know how to solve the libUMP problem... I will reply later today...
Sub_Zero2 said:
I'm at work atm... I know how to solve the libUMP problem... I will reply later today...
Click to expand...
Click to collapse
Thanks for the reply. I already did a search for this issue and found someone who suggested to delete one of the libUMP folders, but this only gave a different error. I would be grateful for any advise for this. I still haven't got any further with these errors. :fingers-crossed:
Clyde00 said:
Thanks for the reply. I already did a search for this issue and found someone who suggested to delete one of the libUMP folders, but this only gave a different error. I would be grateful for any advise for this. I still haven't got any further with these errors. :fingers-crossed:
Click to expand...
Click to collapse
Iirc, you have to delete/comment out two lines in a file. But atm i can not remember the filename of this file. I will have a look at it when I get home, in 3-4 hours.
You have to edit this file: vendor/samsung/galaxys2-common/proprietary/Android.mk
Uncomment these lines with a # om each line:
include $(CLEAR_VARS)
LOCAL_MODULE := libUMP
LOCAL_MODULE_OWNER := samsung
LOCAL_SRC_FILES := system/lib/libUMP.so
LOCAL_MODULE_TAGS := optional
LOCAL_MODULE_SUFFIX := .so
LOCAL_MODULE_CLASS := SHARED_LIBRARIES
LOCAL_MODULE_PATH := $(TARGET_OUT)/lib
include $(BUILD_PREBUILT)
There... Now you should be able to brunch successfully
@Sub_Zero2
Thank you very much for your input. I tried brunch again and got much further, but now I have OOM problems(8gb ram) stopping the build from succeeding. Now I'm doing some searching to solve this issue.
I need to figure out how(and whether to) change JACK_SERVER_VM_ARGUMENTS or change jack.server.max-service= to a lower value.
EDIT: I got a successful build! For anyone having similar out of memory errors, I ran these commands before starting brunch:
Code:
export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4g"
./prebuilts/sdk/tools/jack-admin kill-server
./prebuilts/sdk/tools/jack-admin start-server
Clyde00 said:
@Sub_Zero2
Thank you very much for your input. I tried brunch again and got much further, but now I have OOM problems(8gb ram) stopping the build from succeeding. Now I'm doing some searching to solve this issue.
I need to figure out how(and whether to) change JACK_SERVER_VM_ARGUMENTS or change jack.server.max-service= to a lower value.
EDIT: I got a successful build! For anyone having similar out of memory errors, I ran these commands before starting brunch:
Click to expand...
Click to collapse
There you go!
Good luck!
[GUIDE] Build LineageOS 14.1
See my posts in this thread. This guide works for all lineage-13.0 and 14.1 devices. On that note, feel free to try my i9100 builds and the latest bootloader and modem, links in my signature.
anyone know how to solve this
1 error generated. [ 0% 32/81917] target thumb C++: libinit_m... <= device/asus/Z010D/init/init_msm8916.cpp FAILED: /home/christo/los/out/target/product/Z010D/obj_arm/STATIC_LIBRARIES/libinit_msm8916_intermediates/init_msm8916.o /bin/bash -c "PWD=/proc/self/cwd prebuilts/clang/host/linux-x86/clang-3859424/bin/clang++ -I device/asus/msm8916-common/include -I system/core/init -I external/selinux/libselinux/include -I device/asus/Z010D/init -I /home/christo/los/out/target/product/Z010D/obj_arm/STATIC_LIBRARIES/libinit_msm8916_intermediates -I /home/christo/los/out/target/product/Z010D/gen/STATIC_LIBRARIES/libinit_msm8916_intermediates -I libnativehelper/include/nativehelper \$(cat /home/christo/los/out/target/product/Z010D/obj_arm/STATIC_LIBRARIES/libinit_msm8916_intermediates/import_includes) -I system/core/include -I system/media/audio/include -I hardware/libhardware/include -I hardware/libhardware_legacy/include -I hardware/ril/include -I libnativehelper/include -I frameworks/native/include -I frameworks/native/opengl/include -isystem frameworks/av/include -isystem /home/christo/los/out/target/product/Z010D/obj/include -isystem bionic/libc/arch-arm/include -isystem bionic/libc/include -isystem bionic/libc/kernel/uapi -isystem bionic/libc/kernel/uapi/asm-arm -isystem bionic/libc/kernel/android/uapi -c -fno-exceptions -Wno-multichar -ffunction-sections -fdata-sections -funwind-tables -fstack-protector-strong -Wa,--noexecstack -Werror=format-security -D_FORTIFY_SOURCE=2 -fno-short-enums -no-canonical-prefixes -DNDEBUG -g -Wstrict-aliasing=2 -DANDROID -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith -DNDEBUG -UDEBUG -fdebug-prefix-map=/proc/self/cwd= -D__compiler_offsetof=__builtin_offsetof -Werror=int-conversion -Wno-reserved-id-macro -Wno-format-pedantic -Wno-unused-command-line-argument -fcolor-diagnostics -Wno-expansion-to-defined -fdebug-prefix-map=\$PWD/= -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Werror=date-time -nostdlibinc -msoft-float -mfloat-abi=softfp -mfpu=neon -march=armv7-a -target arm-linux-androideabi -Bprebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/arm-linux-androideabi/bin -Wsign-promo -Wno-inconsistent-missing-override -Wno-null-dereference -fvisibility-inlines-hidden -std=gnu++14 -mthumb -Os -fomit-frame-pointer -fno-strict-aliasing -fno-rtti -Wall -DANDROID_TARGET=\\\"msm8916\\\" -fPIC -D_USING_LIBCXX -DANDROID_STRICT -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -Werror=address-of-temporary -Werror=return-type -MD -MF /home/christo/los/out/target/product/Z010D/obj_arm/STATIC_LIBRARIES/libinit_msm8916_intermediates/init_msm8916.d -o /home/christo/los/out/target/product/Z010D/obj_arm/STATIC_LIBRARIES/libinit_msm8916_intermediates/init_msm8916.o device/asus/Z010D/init/init_msm8916.cpp" device/asus/Z010D/init/init_msm8916.cpp:54:7: error: using declaration requires a qualified name using property_set; ^ 1 error generated. [ 0% 40/81917] target C++: libsdcard <= system/core/sdcard/fuse.cpp ninja: build stopped: subcommand failed. 06:53:31 ninja failed with: exit status 1 make: *** [build/core/main.mk:21: run_soong_ui] Error 1 make: Leaving directory '/home/christo/los' #### make failed to build some targets (01:08 (mm:ss)) #### [email protected]:~/los$
Related
Hi all !
My current project is to use my Raspberry Pi as a Build Machine to build all Android sources (AOSP). In fact, I'll not build AOSP but the CyanogenMod (wich is mainly a fork from AOSP).
I know this may sound crazy, dumb or useless (according to Google, a 64-bit environment is required, and a lot (>> 4GB) of RAM if you're in a hurry), especially to use an ARM processor to build while all the Makefiles has been written to be used on x86...
But what I'm thinking about is a really cheap, silent, but working build machine, to sync the repo and build nightlies everyday. The first build will take some days but then, only the changes will be build so I think that only some hours per day will be required.
If I success, I'll create a big tutorial to explain what changes was required.
First of all, I had to add the Linux-armv61 arch as Host OS/ARCH :
Code:
[email protected] ~/buildspace/android/system/build $ git diff
diff --git a/core/envsetup.mk b/core/envsetup.mk
index 862b7f0..34eb31a 100644
--- a/core/envsetup.mk
+++ b/core/envsetup.mk
@@ -77,6 +77,10 @@ ifneq (,$(findstring Power,$(UNAME)))
HOST_ARCH := ppc
endif
[COLOR="SeaGreen"]+ifneq (,$(findstring arm,$(UNAME)))
+ HOST_ARCH := armv61
+endif
+[/COLOR]
BUILD_ARCH := $(HOST_ARCH)
ifeq ($(HOST_ARCH),)
then, I did this (because the raspbian ld doesn't support --icf) :
AdamOutler said:
so I did a
Code:
[email protected] ~/adb $ grep -r 'icf=safe' ./*
./build/core/combo/TARGET_linux-arm.mk: -Wl,--icf=safe \
and I removed that icf parameter.
Click to expand...
Click to collapse
-->
Code:
[email protected] ~/buildspace/android/system/build $ git diff
diff --git a/core/combo/TARGET_linux-arm.mk b/core/combo/TARGET_linux-arm.mk
index b36111f..24e0d99 100644
--- a/core/combo/TARGET_linux-arm.mk
+++ b/core/combo/TARGET_linux-arm.mk
@@ -146,7 +146,6 @@ TARGET_GLOBAL_LDFLAGS += \
-Wl,-z,relro \
-Wl,-z,now \
-Wl,--warn-shared-textrel \
[COLOR="Red"]- -Wl,--icf=safe \[/COLOR]
$(arch_variant_ldflags)
# We only need thumb interworking in cases where thumb support
but now I am stuck with this error :
Code:
make -C kernel/samsung/smdk4210 O=/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-" headers_install
make[1]: Entering directory `/media/totoext4part/cyanogenmod/system/kernel/samsung/smdk4210'
/media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: 1: /media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: Syntax error: "(" unexpected
CHK include/linux/version.h
make[1]: Leaving directory `/media/totoext4part/cyanogenmod/system/kernel/samsung/smdk4210'
/bin/bash: r: command not found
make: [/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/lib/crtbegin_static.o] Error 127 (ignored)
[COLOR="SeaGreen"]target SharedLib[/COLOR]: libdl (/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so)
/usr/bin/ld: error: /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so uses VFP register arguments, /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/libdl.o does not
/usr/bin/ld: failed to merge target specific data of file /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/libdl.o
/usr/bin/ld: warning: creating a DT_TEXTREL in a shared object.
collect2: ld returned 1 exit status
make: *** [/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so] Error 1
I don't really know what I have to do and if it is because the HOST is an arm arch...
It have been a long time since I didn't put my hands in this kind of things and I need help to solve this problems... Thanks in advance !
cmoatoto said:
Hi all !
My current project is to use my Raspberry Pi as a Build Machine to build all Android sources (AOSP). In fact, I'll not build AOSP but the CyanogenMod (wich is mainly a fork from AOSP).
I know this may sound crazy, dumb or useless (according to Google, a 64-bit environment is required, and a lot (>> 4GB) of RAM if you're in a hurry), especially to use an ARM processor to build while all the Makefiles has been written to be used on x86...
But what I'm thinking about is a really cheap, silent, but working build machine, to sync the repo and build nightlies everyday. The first build will take some days but then, only the changes will be build so I think that only some hours per day will be required.
If I success, I'll create a big tutorial to explain what changes was required.
First of all, I had to add the Linux-armv61 arch as Host OS/ARCH :
Code:
[email protected] ~/buildspace/android/system/build $ git diff
diff --git a/core/envsetup.mk b/core/envsetup.mk
index 862b7f0..34eb31a 100644
--- a/core/envsetup.mk
+++ b/core/envsetup.mk
@@ -77,6 +77,10 @@ ifneq (,$(findstring Power,$(UNAME)))
HOST_ARCH := ppc
endif
[COLOR="SeaGreen"]+ifneq (,$(findstring arm,$(UNAME)))
+ HOST_ARCH := armv61
+endif
+[/COLOR]
BUILD_ARCH := $(HOST_ARCH)
ifeq ($(HOST_ARCH),)
then, I did this (because the raspbian ld doesn't support --icf) :
-->
Code:
[email protected] ~/buildspace/android/system/build $ git diff
diff --git a/core/combo/TARGET_linux-arm.mk b/core/combo/TARGET_linux-arm.mk
index b36111f..24e0d99 100644
--- a/core/combo/TARGET_linux-arm.mk
+++ b/core/combo/TARGET_linux-arm.mk
@@ -146,7 +146,6 @@ TARGET_GLOBAL_LDFLAGS += \
-Wl,-z,relro \
-Wl,-z,now \
-Wl,--warn-shared-textrel \
[COLOR="Red"]- -Wl,--icf=safe \[/COLOR]
$(arch_variant_ldflags)
# We only need thumb interworking in cases where thumb support
but now I am stuck with this error :
Code:
make -C kernel/samsung/smdk4210 O=/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-" headers_install
make[1]: Entering directory `/media/totoext4part/cyanogenmod/system/kernel/samsung/smdk4210'
/media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: 1: /media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: Syntax error: "(" unexpected
CHK include/linux/version.h
make[1]: Leaving directory `/media/totoext4part/cyanogenmod/system/kernel/samsung/smdk4210'
/bin/bash: r: command not found
make: [/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/lib/crtbegin_static.o] Error 127 (ignored)
[COLOR="SeaGreen"]target SharedLib[/COLOR]: libdl (/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so)
/usr/bin/ld: error: /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so uses VFP /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/libdl.o does not
/usr/bin/ld: failed to merge target specific data of file /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/libdl.o
/usr/bin/ld: warning: creating a DT_TEXTREL in a shared object.
collect2: ld returned 1 exit status
make: *** [/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so] Error 1
I don't really know what I have to do and if it is because the HOST is an arm arch...
It have been a long time since I didn't put my hands in this kind of things and I need help to solve this problems... Thanks in advance !
Click to expand...
Click to collapse
Hi There,
First lets roll it back a bit....... I would ditch the kernel building to begin with.... and just see if you can build the OS.
I'd also probably sanity check the toolchains by doing "BUILD_TINY_ANDROID=true make -j<whatever> " This build the very basics of the system and will probably highlight any issues
Looking at it however .... Are you building this on the PI? becuase your kernel build looks like it is still using the x86 tool-chain
Code:
ARCH=arm CROSS_COMPILE=" /media/totoext4part/cyanogenmod/system/prebuilt[B]/linux-x86/[/B]toolchain/arm-eabi-4.4.3/bin/arm-eabi-"
One more thing the HOST_ARCH can be just set to arm and not armv61 , I was going to submit the change to AOSP , JBQ has at least said it's a viable . I just haven't be chewing on PI too much! If you end up with a working patch set then feel free to add the AOSP change yourself, they only want the host file and probably the envsetup.mk
Good Luck
trevd said:
Hi There,
First lets roll it back a bit....... I would ditch the kernel building to begin with.... and just see if you can build the OS.
I'd also probably sanity check the toolchains by doing "BUILD_TINY_ANDROID=true make -j<whatever> " This build the very basics of the system and will probably highlight any issues
Looking at it however .... Are you building this on the PI? becuase your kernel build looks like it is still using the x86 tool-chain
Code:
ARCH=arm CROSS_COMPILE=" /media/totoext4part/cyanogenmod/system/prebuilt[B]/linux-x86/[/B]toolchain/arm-eabi-4.4.3/bin/arm-eabi-"
One more thing the HOST_ARCH can be just set to arm and not armv61 , I was going to submit the change to AOSP , JBQ has at least said it's a viable. I just haven't be chewing on PI too much! If you end up with a working patch set then feel free to add the AOSP change yourself, they only want the host file and probably the envsetup.mk
Good Luck
Click to expand...
Click to collapse
I launched a
Code:
BUILD_TINY_ANDROID=true make -j1
and I'll tell you what comes out.
Are you building this on the PI? becuase your kernel build looks like it is still using the x86 tool-chain
Code:
ARCH=arm CROSS_COMPILE=" /media/totoext4part/cyanogenmod/system/prebuilt[B]/linux-x86/[/B]toolchain/arm-eabi-4.4.3/bin/arm-eabi-"
Click to expand...
Click to collapse
I know that but I had difficulty to fix it.
First of all, I forgot to tell I added this host file :
Code:
[email protected] ~/buildspace/android/system/build $ cat core/combo/HOST_linux-armv61.mk
# Configuration for builds hosted on linux-armv6l.
# $(1): The file to check
define get-file-size
stat --format "%s" "$(1)" | tr -d '\n'
endef
HOST_SDK_TOOLCHAIN_PREFIX :=
ifneq (,$(strip $(wildcard $(HOST_SDK_TOOLCHAIN_PREFIX)/gcc)))
HOST_CC := $(HOST_SDK_TOOLCHAIN_PREFIX)/gcc
HOST_CXX := $(HOST_SDK_TOOLCHAIN_PREFIX)/g++
HOST_AR := $(HOST_SDK_TOOLCHAIN_PREFIX)/ar
endif # $(HOST_SDK_TOOLCHAIN_PREFIX)/gcc exists
HOST_GLOBAL_CFLAGS += -fPIC
HOST_GLOBAL_CFLAGS += -include $(call select-android-config-h,linux-armv61)
HOST_GLOBAL_CFLAGS += -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0
HOST_NO_UNDEFINED_LDFLAGS := -Wl,--no-undefined
Then, here is the result of "lunch" command (I build for n7000) :
Code:
[email protected] ~/buildspace/android/system $ lunch cm_n7000-userdebug
Looking for dependencies
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.2.1
TARGET_PRODUCT=cm_n7000
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=armv61
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.2.27+-armv6l-with-debian-7.0
HOST_BUILD_TYPE=release
BUILD_ID=JOP40D
OUT_DIR=/media/totoext4part/cyanogenmod/system/out
============================================
About the "linux-x86" problem, I searched a lot and I think I have some change to do in tools/releasetools/common.py but I'll wait to understand well toolchains before doing useless bad things.
Here is the "BUILD_TINY_ANDROID=true make -j1" command result.
Code:
make -C kernel/samsung/smdk4210 O=/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-" headers_install
make[1]: Entering directory `/media/totoext4part/cyanogenmod/system/kernel/samsung/smdk4210'
/media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: 1: /media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: Syntax error: "(" unexpected
CHK include/linux/version.h
make[1]: Leaving directory `/media/totoext4part/cyanogenmod/system/kernel/samsung/smdk4210'
host C: mkbootfs <= system/core/cpio/mkbootfs.c
cc1: fatal error: build/core/combo/include/arch/linux-armv61/AndroidConfig.h: No such file or directory
compilation terminated.
make: *** [/media/totoext4part/cyanogenmod/system/out/host/linux-armv61/obj/EXECUTABLES/mkbootfs_intermediates/mkbootfs.o] Error 1
Ok I have to create some more host files...
Ok, I changed HOST_ARCH from armv61 to arm in build/core/envsetup.mk,
build/core/combo/HOST_linux-armv61.mk became build/core/combo/HOST_linux-arm.mk and in this file, I changed
Code:
HOST_GLOBAL_CFLAGS += -include $(call select-android-config-h,linux-armv61)
to
HOST_GLOBAL_CFLAGS += -include $(call select-android-config-h,linux-arm)
Here is what I got now (with "BUILD_TINY_ANDROID=true make -j1")
Code:
[COLOR="SeaGreen"][email protected][/COLOR] [COLOR="RoyalBlue"]~/buildspace/android/system $[/COLOR] BUILD_TINY_ANDROID=true make -j1
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.2.1
TARGET_PRODUCT=cm_n7000
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=arm
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.2.27+-armv6l-with-debian-7.0
HOST_BUILD_TYPE=release
BUILD_ID=JOP40D
OUT_DIR=/media/totoext4part/cyanogenmod/system/out
============================================
build/core/Makefile:44: warning: overriding commands for target `/media/totoext4part/cyanogenmod/system/out/target/product/n7000/system/etc/mkshrc'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/media/totoext4part/cyanogenmod/system/out/target/product/n7000/system/etc/mkshrc'
PRODUCT_COPY_FILES system/bluetooth/data/main.le.conf:system/etc/bluetooth/main.conf ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/AVRCP.kl:system/usr/keylayout/AVRCP.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Generic.kl:system/usr/keylayout/Generic.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/qwerty.kl:system/usr/keylayout/qwerty.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_05ac_Product_0239.kl:system/usr/keylayout/Vendor_05ac_Product_0239.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_22b8_Product_093d.kl:system/usr/keylayout/Vendor_22b8_Product_093d.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_045e_Product_028e.kl:system/usr/keylayout/Vendor_045e_Product_028e.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_046d_Product_c216.kl:system/usr/keylayout/Vendor_046d_Product_c216.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_046d_Product_c294.kl:system/usr/keylayout/Vendor_046d_Product_c294.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_046d_Product_c299.kl:system/usr/keylayout/Vendor_046d_Product_c299.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_046d_Product_c532.kl:system/usr/keylayout/Vendor_046d_Product_c532.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_054c_Product_0268.kl:system/usr/keylayout/Vendor_054c_Product_0268.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keychars/Generic.kcm:system/usr/keychars/Generic.kcm ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keychars/qwerty.kcm:system/usr/keychars/qwerty.kcm ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keychars/qwerty2.kcm:system/usr/keychars/qwerty2.kcm ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keychars/Virtual.kcm:system/usr/keychars/Virtual.kcm ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/idc/qwerty.idc:system/usr/idc/qwerty.idc ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/idc/qwerty2.idc:system/usr/idc/qwerty2.idc ignored.
PRODUCT_COPY_FILES vendor/samsung/n7000/proprietary/system/etc/gps.xml:system/etc/gps.xml ignored.
build/core/tasks/kernel.mk:161: warning: overriding commands for target `TARGET_KERNEL_BINARIES'
device/samsung/galaxys2-common/shbootimg.mk:26: warning: ignoring old commands for target `TARGET_KERNEL_BINARIES'
[COLOR="Olive"]host C[/COLOR]: acp <= build/tools/acp/acp.c
[COLOR="MediumTurquoise"]Import includes file[/COLOR]: /media/totoext4part/cyanogenmod/system/out/host/linux-arm/obj/STATIC_LIBRARIES/libhost_intermediates/import_includes
[COLOR="Olive"]host C++[/COLOR]: libhost <= build/libs/host/pseudolocalize.cpp
[COLOR="olive"]host C[/COLOR]: libhost <= build/libs/host/CopyFile.c
[COLOR="olive"]host StaticLib[/COLOR]: libhost (/media/totoext4part/cyanogenmod/system/out/host/linux-arm/obj/STATIC_LIBRARIES/libhost_intermediates/libhost.a)
[COLOR="MediumTurquoise"]Export includes file[/COLOR]: build/tools/acp/Android.mk -- /media/totoext4part/cyanogenmod/system/out/host/linux-arm/obj/EXECUTABLES/acp_intermediates/export_includes
[COLOR="Olive"]host Executable[/COLOR]: acp (/media/totoext4part/cyanogenmod/system/out/host/linux-arm/obj/EXECUTABLES/acp_intermediates/acp)
[COLOR="MediumTurquoise"]Install: /media/totoext4part/cyanogenmod/system/out/host/linux-arm/bin/acp[/COLOR]
make -C kernel/samsung/smdk4210 O=/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-" headers_install
make[1]: Entering directory `/media/totoext4part/cyanogenmod/system/kernel/samsung/smdk4210'
/media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: 1: /media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: Syntax error: "(" unexpected
CHK include/linux/version.h
make[1]: Leaving directory `/media/totoext4part/cyanogenmod/system/kernel/samsung/smdk4210'
[COLOR="MediumTurquoise"]Import includes file[/COLOR]: /media/totoext4part/cyanogenmod/system/out/host/linux-arm/obj/EXECUTABLES/mkbootfs_intermediates/import_includes
[COLOR="Olive"]host C[/COLOR]: mkbootfs <= system/core/cpio/mkbootfs.c
[COLOR="MediumTurquoise"]Export includes file[/COLOR]: system/core/cpio/Android.mk -- /media/totoext4part/cyanogenmod/system/out/host/linux-arm/obj/EXECUTABLES/mkbootfs_intermediates/export_includes
[COLOR="olive"]host Executable[/COLOR]: mkbootfs (/media/totoext4part/cyanogenmod/system/out/host/linux-arm/obj/EXECUTABLES/mkbootfs_intermediates/mkbootfs)
[COLOR="MediumTurquoise"]Install: /media/totoext4part/cyanogenmod/system/out/host/linux-arm/bin/mkbootfs[/COLOR]
/bin/bash: r: command not found
make: [/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/lib/crtbegin_static.o] Error 127 (ignored)
[COLOR="MediumTurquoise"]Import includes file[/COLOR]: /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/EXECUTABLES/init_intermediates/import_includes
[COLOR="rgb(46, 139, 87)"]target thumb C[/COLOR]: init <= system/core/init/builtins.c
system/core/init/builtins.c: In function ‘do_exec’:
system/core/init/builtins.c:283:34: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/init.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/devices.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/property_service.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/util.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/parser.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/logo.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/keychords.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/signal_handler.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/init_parser.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/ueventd.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/ueventd_parser.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/watchdogd.c
[COLOR="SeaGreen"]target SharedLib[/COLOR]: libdl (/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so)
/usr/bin/ld: error: /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so uses VFP register arguments, /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/libdl.o does not
/usr/bin/ld: failed to merge target specific data of file /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/libdl.o
/usr/bin/ld: warning: creating a DT_TEXTREL in a shared object.
collect2: ld returned 1 exit status
make: *** [/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so] Error 1
So I'm stuck with almost my initial problem, a kind of two different libdl. But which one do I have to change and where can I find them?
cmoatoto said:
Ok, I changed HOST_ARCH from armv61 to arm in build/core/envsetup.mk,
build/core/combo/HOST_linux-armv61.mk became build/core/combo/HOST_linux-arm.mk and in this file, I changed
Code:
HOST_GLOBAL_CFLAGS += -include $(call select-android-config-h,linux-armv61)
to
HOST_GLOBAL_CFLAGS += -include $(call select-android-config-h,linux-arm)
Here is what I got now (with "BUILD_TINY_ANDROID=true make -j1")
Code:
[COLOR="SeaGreen"][email protected][/COLOR] [COLOR="RoyalBlue"]~/buildspace/android/system $[/COLOR] BUILD_TINY_ANDROID=true make -j1
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.2.1
TARGET_PRODUCT=cm_n7000
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=arm
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.2.27+-armv6l-with-debian-7.0
HOST_BUILD_TYPE=release
BUILD_ID=JOP40D
OUT_DIR=/media/totoext4part/cyanogenmod/system/out
============================================
build/core/Makefile:44: warning: overriding commands for target `/media/totoext4part/cyanogenmod/system/out/target/product/n7000/system/etc/mkshrc'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/media/totoext4part/cyanogenmod/system/out/target/product/n7000/system/etc/mkshrc'
PRODUCT_COPY_FILES system/bluetooth/data/main.le.conf:system/etc/bluetooth/main.conf ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/AVRCP.kl:system/usr/keylayout/AVRCP.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Generic.kl:system/usr/keylayout/Generic.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/qwerty.kl:system/usr/keylayout/qwerty.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_05ac_Product_0239.kl:system/usr/keylayout/Vendor_05ac_Product_0239.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_22b8_Product_093d.kl:system/usr/keylayout/Vendor_22b8_Product_093d.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_045e_Product_028e.kl:system/usr/keylayout/Vendor_045e_Product_028e.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_046d_Product_c216.kl:system/usr/keylayout/Vendor_046d_Product_c216.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_046d_Product_c294.kl:system/usr/keylayout/Vendor_046d_Product_c294.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_046d_Product_c299.kl:system/usr/keylayout/Vendor_046d_Product_c299.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_046d_Product_c532.kl:system/usr/keylayout/Vendor_046d_Product_c532.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keylayout/Vendor_054c_Product_0268.kl:system/usr/keylayout/Vendor_054c_Product_0268.kl ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keychars/Generic.kcm:system/usr/keychars/Generic.kcm ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keychars/qwerty.kcm:system/usr/keychars/qwerty.kcm ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keychars/qwerty2.kcm:system/usr/keychars/qwerty2.kcm ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/keychars/Virtual.kcm:system/usr/keychars/Virtual.kcm ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/idc/qwerty.idc:system/usr/idc/qwerty.idc ignored.
PRODUCT_COPY_FILES device/samsung/n7000/usr/idc/qwerty2.idc:system/usr/idc/qwerty2.idc ignored.
PRODUCT_COPY_FILES vendor/samsung/n7000/proprietary/system/etc/gps.xml:system/etc/gps.xml ignored.
build/core/tasks/kernel.mk:161: warning: overriding commands for target `TARGET_KERNEL_BINARIES'
device/samsung/galaxys2-common/shbootimg.mk:26: warning: ignoring old commands for target `TARGET_KERNEL_BINARIES'
[COLOR="Olive"]host C[/COLOR]: acp <= build/tools/acp/acp.c
[COLOR="MediumTurquoise"]Import includes file[/COLOR]: /media/totoext4part/cyanogenmod/system/out/host/linux-arm/obj/STATIC_LIBRARIES/libhost_intermediates/import_includes
[COLOR="Olive"]host C++[/COLOR]: libhost <= build/libs/host/pseudolocalize.cpp
[COLOR="olive"]host C[/COLOR]: libhost <= build/libs/host/CopyFile.c
[COLOR="olive"]host StaticLib[/COLOR]: libhost (/media/totoext4part/cyanogenmod/system/out/host/linux-arm/obj/STATIC_LIBRARIES/libhost_intermediates/libhost.a)
[COLOR="MediumTurquoise"]Export includes file[/COLOR]: build/tools/acp/Android.mk -- /media/totoext4part/cyanogenmod/system/out/host/linux-arm/obj/EXECUTABLES/acp_intermediates/export_includes
[COLOR="Olive"]host Executable[/COLOR]: acp (/media/totoext4part/cyanogenmod/system/out/host/linux-arm/obj/EXECUTABLES/acp_intermediates/acp)
[COLOR="MediumTurquoise"]Install: /media/totoext4part/cyanogenmod/system/out/host/linux-arm/bin/acp[/COLOR]
make -C kernel/samsung/smdk4210 O=/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-" headers_install
make[1]: Entering directory `/media/totoext4part/cyanogenmod/system/kernel/samsung/smdk4210'
/media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: 1: /media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: Syntax error: "(" unexpected
CHK include/linux/version.h
make[1]: Leaving directory `/media/totoext4part/cyanogenmod/system/kernel/samsung/smdk4210'
[COLOR="MediumTurquoise"]Import includes file[/COLOR]: /media/totoext4part/cyanogenmod/system/out/host/linux-arm/obj/EXECUTABLES/mkbootfs_intermediates/import_includes
[COLOR="Olive"]host C[/COLOR]: mkbootfs <= system/core/cpio/mkbootfs.c
[COLOR="MediumTurquoise"]Export includes file[/COLOR]: system/core/cpio/Android.mk -- /media/totoext4part/cyanogenmod/system/out/host/linux-arm/obj/EXECUTABLES/mkbootfs_intermediates/export_includes
[COLOR="olive"]host Executable[/COLOR]: mkbootfs (/media/totoext4part/cyanogenmod/system/out/host/linux-arm/obj/EXECUTABLES/mkbootfs_intermediates/mkbootfs)
[COLOR="MediumTurquoise"]Install: /media/totoext4part/cyanogenmod/system/out/host/linux-arm/bin/mkbootfs[/COLOR]
/bin/bash: r: command not found
make: [/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/lib/crtbegin_static.o] Error 127 (ignored)
[COLOR="MediumTurquoise"]Import includes file[/COLOR]: /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/EXECUTABLES/init_intermediates/import_includes
[COLOR="rgb(46, 139, 87)"]target thumb C[/COLOR]: init <= system/core/init/builtins.c
system/core/init/builtins.c: In function ‘do_exec’:
system/core/init/builtins.c:283:34: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/init.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/devices.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/property_service.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/util.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/parser.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/logo.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/keychords.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/signal_handler.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/init_parser.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/ueventd.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/ueventd_parser.c
[COLOR="SeaGreen"]target thumb C[/COLOR]: init <= system/core/init/watchdogd.c
[COLOR="SeaGreen"]target SharedLib[/COLOR]: libdl (/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so)
/usr/bin/ld: error: /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so uses VFP register arguments, /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/libdl.o does not
/usr/bin/ld: failed to merge target specific data of file /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/libdl.o
/usr/bin/ld: warning: creating a DT_TEXTREL in a shared object.
collect2: ld returned 1 exit status
make: *** [/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so] Error 1
So I'm stuck with almost my initial problem, a kind of two different libdl. But which one do I have to change and where can I find them?
Click to expand...
Click to collapse
libdl is in the bionic directory, Did you clear your out ( rm -rf out ) directory before rebuilding?
You all of these are intermediate files ( i.e halfway done) what I suspect has happen is the obj/SHARED_LIBRARIES/libdl_intermediates/libdl.o object file has been recompiled by the x86 toolchain and it's trying the link that in with some arm stuff.... That's all speculation however and I could be full of s**t! ,
EDIT: To find stuff type godir <word>
this indexes the source first time round the "cd's" to the chosen one ( might take a while to index on the pi )
also "hmm" is the help command which lists the majority of commands available to you.
trevd said:
libdl is in the bionic directory, Did you clear your out ( rm -rf out ) directory before rebuilding?
You all of these are intermediate files ( i.e halfway done) what I suspect has happen is the obj/SHARED_LIBRARIES/libdl_intermediates/libdl.o object file has been recompiled by the x86 toolchain and it's trying the link that in with some arm stuff.... That's all speculation however and I could be full of s**t! ,
EDIT: To find stuff type godir <word>
this indexes the source first time round the "cd's" to the chosen one ( might take a while to index on the pi )
also "hmm" is the help command which lists the majority of commands available to you.
Click to expand...
Click to collapse
Thanks for the tip !
I'll do "rm -rf out" but I'll cry a bit, because it took some days to build some stuff (framework.jar, javadoc etc...). But as I said in the first post, I'm not in a hurry. I'll follow your idea.
About the toolchain problem, I think so (a x86 libdl compared to an arm one, one something like that). Now I have to find out how to force the x86 libdl to be build with arm.
I'll tell you when the rm -rf and the make will end.
cmoatoto said:
Thanks for the tip !
I'll do "rm -rf out" but I'll cry a bit, because it took some days to build some stuff (framework.jar, javadoc etc...). But as I said in the first post, I'm not in a hurry. I'll follow your idea.
About the toolchain problem, I think so (a x86 libdl compared to an arm one, one something like that). Now I have to find out how to force the x86 libdl to be build with arm.
I'll tell you when the rm -rf and the make will end.
Click to expand...
Click to collapse
What you need is an native armv6l androideabi toolchain thats capable of outputting armv7 and armv7-neon that supports the androideabi but run... probably something your going to have to build yourself.... also the cm toolchain are a little old now and they are probably not you best reference.
I would highly recommend talking to Linaro, They know a trick or two about the android toolchain and maintain an android repo which builds against the latest gcc! Although they don't directly build the arm for arm android toolchain ( I don't think ) they will probably be able to offer some guidance if you ask them nicely!!
Like I said earlier... Good Luck!
Some useful links:
http://www.linaro.org/
https://wiki.linaro.org/Platform/Android/FollowTheToolchainCycle
https://wiki.linaro.org/Platform/Android/AndroidOnPanda
This is something that took me crazy :thumbsup: good work.. will try soon! Btw android cannot run on Raspberry Pi due to the crap gpu in it
cmoatoto said:
Thanks for the tip !
I'll do "rm -rf out" but I'll cry a bit, because it took some days to build some stuff (framework.jar, javadoc etc...). But as I said in the first post, I'm not in a hurry. I'll follow your idea.
About the toolchain problem, I think so (a x86 libdl compared to an arm one, one something like that). Now I have to find out how to force the x86 libdl to be build with arm.
I'll tell you when the rm -rf and the make will end.
Click to expand...
Click to collapse
Did you ever get this working all the way? It would be awesome to be able to build some ROMs for my phone using the rpi!
Sent from my SPH-D710 using xda app-developers app
Won't building CM10 on a raspberrypi take ages? I know it easily takes 2-3 hours on my laptop to build it from scratch.
Yes and no.
The gnomes that lurk on Raspberry Pi Forums have gotten a working Gingerbread on the Pi, but it's not hardware accelerated due to Broadcom playing fast and loose with the GPU specs. A test build of ICS with said specs had been made seen, but it's not in the wild due to it being volunteer based, and with super secret sauce to boot.
lol @ gnomes
svenvv said:
Won't building CM10 on a raspberrypi take ages? I know it easily takes 2-3 hours on my laptop to build it from scratch.
Click to expand...
Click to collapse
Yes and no, but not for the reason moocow1452 said : The goal is not to RUN Android (or CM) on Raspberry, but to BUILD it on a Raspberry.
So, to answer the question, yes, it takes ages (days actually as far as I could go). Especially the Java builds are a pain in the a** (I had to swipe up to 2Go on a usb disk and reduce via scripts (to catch and log all java, javac and javadoc calls) the java heap size).
But once this builds have been done, they will not be run again until someone change the code associated. So if you pull the source everyday then build the code (= nightly builds), it will not take that long (maybe a couple of hour when it should take some minutes on a real computer)
Pyro96 said:
Did you ever get this working all the way? It would be awesome to be able to build some ROMs for my phone using the rpi!
Click to expand...
Click to collapse
No I didn't. They're is a looot of work to prepare the native armv6l androideabi toolchain and I don't really have time now. I keep this project in my mind but I will need some help with that (I might get it in some days/week if I'm lucky)
Hey guys. Great thread (subscribed) so far, many thanks.
One thing I normally use is distcc, but the android build system doesn't want to play. It would be nice if we could use that extra power.
...
cmoatoto said:
Hi all !
My current project is to use my Raspberry Pi as a Build Machine to build all Android sources (AOSP). In fact, I'll not build AOSP but the CyanogenMod (wich is mainly a fork from AOSP).
I know this may sound crazy, dumb or useless (according to Google, a 64-bit environment is required, and a lot (>> 4GB) of RAM if you're in a hurry), especially to use an ARM processor to build while all the Makefiles has been written to be used on x86...
But what I'm thinking about is a really cheap, silent, but working build machine, to sync the repo and build nightlies everyday. The first build will take some days but then, only the changes will be build so I think that only some hours per day will be required.
If I success, I'll create a big tutorial to explain what changes was required.
First of all, I had to add the Linux-armv61 arch as Host OS/ARCH :
Code:
[email protected] ~/buildspace/android/system/build $ git diff
diff --git a/core/envsetup.mk b/core/envsetup.mk
index 862b7f0..34eb31a 100644
--- a/core/envsetup.mk
+++ b/core/envsetup.mk
@@ -77,6 +77,10 @@ ifneq (,$(findstring Power,$(UNAME)))
HOST_ARCH := ppc
endif
[COLOR="SeaGreen"]+ifneq (,$(findstring arm,$(UNAME)))
+ HOST_ARCH := armv61
+endif
+[/COLOR]
BUILD_ARCH := $(HOST_ARCH)
ifeq ($(HOST_ARCH),)
then, I did this (because the raspbian ld doesn't support --icf) :
-->
Code:
[email protected] ~/buildspace/android/system/build $ git diff
diff --git a/core/combo/TARGET_linux-arm.mk b/core/combo/TARGET_linux-arm.mk
index b36111f..24e0d99 100644
--- a/core/combo/TARGET_linux-arm.mk
+++ b/core/combo/TARGET_linux-arm.mk
@@ -146,7 +146,6 @@ TARGET_GLOBAL_LDFLAGS += \
-Wl,-z,relro \
-Wl,-z,now \
-Wl,--warn-shared-textrel \
[COLOR="Red"]- -Wl,--icf=safe \[/COLOR]
$(arch_variant_ldflags)
# We only need thumb interworking in cases where thumb support
but now I am stuck with this error :
Code:
make -C kernel/samsung/smdk4210 O=/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-" headers_install
make[1]: Entering directory `/media/totoext4part/cyanogenmod/system/kernel/samsung/smdk4210'
/media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: 1: /media/totoext4part/cyanogenmod/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: Syntax error: "(" unexpected
CHK include/linux/version.h
make[1]: Leaving directory `/media/totoext4part/cyanogenmod/system/kernel/samsung/smdk4210'
/bin/bash: r: command not found
make: [/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/lib/crtbegin_static.o] Error 127 (ignored)
[COLOR="SeaGreen"]target SharedLib[/COLOR]: libdl (/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so)
/usr/bin/ld: error: /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so uses VFP register arguments, /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/libdl.o does not
/usr/bin/ld: failed to merge target specific data of file /media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/libdl.o
/usr/bin/ld: warning: creating a DT_TEXTREL in a shared object.
collect2: ld returned 1 exit status
make: *** [/media/totoext4part/cyanogenmod/system/out/target/product/n7000/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so] Error 1
I don't really know what I have to do and if it is because the HOST is an arm arch...
It have been a long time since I didn't put my hands in this kind of things and I need help to solve this problems... Thanks in advance !
Click to expand...
Click to collapse
This was interesting. I may try to build a CM10 on a raspberry pi.
Did you guys actually manage to get it running?
I don't really want to dual boot my sp4 so a raspberry pi would be ideal. The 3 even has wi-fi, so it's easy to stay away somewhere. Would be ideal to build weeklys or bi-weeklys. I already have a spare 1TB external hard drive with power supply laying around.
Was thinking of getting one anyways as a htpc. Ordering 2 means less shipping xD.
The last post before yours is 3 years old, this thread is dead...
What a shame. I wanted to put my pi to a better use.
chrisvrose said:
What a shame. I wanted to put my pi to a better use.
Click to expand...
Click to collapse
Take a look here instead, might be more up to date: https://groups.google.com/forum/#!forum/android-rpi
I put this tutorial together in an attempt to create the most complete and easy to follow guide for building a ROM from source. Including steps for adding apps to your build, changing toolchains and more... The entire guide uses a single Linux terminal window from start to finish in an attempt to keep everything as user friendly as possible. Please feel free to PM me suggestions on where changes need be made.
If you find this guide helpful please press the Thanks button on my posts and rate the thread a 5.
Prerequisites1. This guide is for 64-bit, 32-bit machines will not work for building newer android versions, Ubuntu 12+ based machine, I run Linux Mint 15. Follow links at end of OP for alternate directions
Windows Users: Setup Ubuntu in Virtualbox Instructions
2. You need to know the location for your device, vendor, and kernel repos. This can be found fairly easily in the forum for your phone. Also take note of your phones codename.
For example the Optimus G is the e970 and its device repo can be found here https://github.com/CyanogenMod/android_device_lge_e970
Note*All terminal commands will be in Code boxes*
Part 1 - Setting Up The Build Environment
Install Java JDK
Code:
sudo add-apt-repository ppa:webupd8team/java
Code:
sudo apt-get update
Lollipop Roms:
Code:
sudo apt-get install oracle-java7-installer
Kit-Kat Roms:
Code:
sudo apt-get install oracle-java6-installer
Installing required packages
Ubuntu 14 based:
Code:
sudo apt-get install bison g++-multilib git gperf libxml2-utils
Ubuntu 12 based:
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Code:
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
Set-up ccache This Is Optional
Code:
nano ~/.bashrc
Add these two lines
export USE_CCACHE=1
export CCACHE_DIR=<path-to-your-cache-directory>
Click to expand...
Click to collapse
Save and exit by pressing ctrl+x, selecting Y then enter.
Install ADB & Fastboot This is optional, as you may already have them working. If not, they're a good thing to have.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Setup Repo
Code:
mkdir ~/bin
Code:
PATH=~/bin:$PATH
Code:
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
Code:
chmod a+x ~/bin/repo
Create working directory
Code:
mkdir [I][B]working-dir[/B][/I]
(Replace working-dir with whatever you'd like to call it, ie. aokp)
Code:
cd working-dir
Part 2 - Get SourceROM Source
Choose which custom rom you are going to build and initialize the repo for it
Code:
repo init -u [I][B]chosen-manifest[/B][/I]
(Replace chosen-manifest appropriately from the list below)
AOKP: https://github.com/AOKP/platform_manifest.git -b Branch
Cyanogenmod: https://github.com/CyanogenMod/android.git -b Branch
CarbonDev: https://github.com/CarbonDev/android.git -b Branch
Liquid Smooth: https://github.com/LiquidSmooth/android.git -b Branch
Replace Branch with appropriate branch from github repo ie cm-10.2 or jb3
If unsure which branch click the link above to locate appropriate branch
Click to expand...
Click to collapse
Device Source
Go HERE and follow instructions on obtaining your device specific repos.
Sync the repo
Code:
repo sync
This will take a while as it downloads all the required source
Part 3 - Preparing SourceBefore you're ready to build your source needs to be configured to include your device. This preparation varies slightly for different custom Roms.
Go HERE and follow instructions for your ROM choice
Part 4 - Edit SourceThis Is OptionalThis is where you can make edits to the source before building to suit your needs.
Go HERE and follow the instructions to tweak source
Part 5 - Building ROM
Code:
. build/envsetup.sh
Code:
lunch
Locate your device on the list and enter appropriate number
Code:
make -j[B][I]# [/I][/B]otapackage
Replace # with the number of cores in your system (Is the number of jobs that will be done at once, more cores means more jobs)
Build Errors
This can be hard, especially if you're new to programming languages and building. Meet Google your new best friend.
Here is a basic overview to get you started, and if no more at least googling in the right direction.
FinishedWhen it's done you're rom will be in working-dir/out/target/product/codename/
Enjoy.
I used these sites while making this guide
http://source.android.com/source/initializing.html
http://www.webupd8.org/2012/11/oracle-sun-java-6-installer-available.html
http://www.webupd8.org/2012/08/install-adb-and-fastboot-android-tools.html
Device Source As stated in the prerequisites you will need a device specific Device repo, Vendor repo, and Kernel repo. You can find links to them in the threads for your devices. Also take note of your device codename ie Nexus 4 is mako, Optimus G is gee.
There are two options for adding in device specific source, local manifest and git clone.
Local manifest syncs the device repos each time a repo sync is run. This is probably the better choice if you don't make edits and rely on the repo's maintainer for changes.
Git clone is a one time download of a specific repo to the directory indicated and is not affected by repo sync. This is probably the better choice if you make edits to the device source as they won't be over written or cause conflicts when syncing.
The local path for your phone's repos be device/manufacturer/codename, vendor/manufacturer/codename, kernel/manufacturer/codename regardless of method chosen.
Git Clone
Code:
git clone [B][COLOR="DarkOrange"]repo[/COLOR][/B] -b [B][COLOR="Magenta"]branch[/COLOR][/B] [B][COLOR=Lime]destination-path[/COLOR][/B]
here is and example for the vendor repo for the E973 from TeamPlaceHolder
git clone https://github.com/TeamPlaceholder/proprietary_vendor_lge_gee -b cm-10.2 vendor/lge/gee
Click to expand...
Click to collapse
Local Manifest
Code:
mkdir .repo/local_manifests
Code:
touch .repo/local_manifests/local_manifest.xml
Code:
nano .repo/local_manifests/local_manifest.xml
Add these lines replacing path, name and revision according to the repo's you are using.
This example is for E973 using TeamPlaceHolder repos, adding all device/vendor/kernel repos.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="gh"
fetch="git://github.com/" />
<project path="kernel/lge/gee" name="TeamPlaceholder/android_kernel_lge_gee" remote="gh" revision="cm-10.2-merge" />
<project path="device/lge/geeb" name="TeamPlaceholder/android_device_lge_geeb" remote="gh" revision="cm-10.2" />
<project path="device/lge/gee-common" name="TeamPlaceholder/android_device_lge_gee-common" remote="gh" revision="cm-10.2" />
<project path="vendor/lge/gee" name="TeamPlaceholder/proprietary_vendor_lge_gee" remote="gh" revision="cm-10.2" />
</manifest>
Click to expand...
Click to collapse
Preparing SourceROM specific setup instructions prior to building. All source should be downloaded already.
Manufacturer and codename MUST be updated to reflect your device.
Cyanogenmod
Add this line to vendor/cm/vendorsetup.sh
cm_device-userdebug
Click to expand...
Click to collapse
device - The codename for your device. ie. mako for the Nexus 4
Code:
touch [COLOR="Purple"]path-to-device-tree[/COLOR]/cm.mk
path-to-device-tree - Example device/lge/mako for the Nexus 4
Code:
nano [COLOR="Purple"]path-to-device-tree[/COLOR]/cm.mk
Add these lines **This example is for the Nexus 4 Mako, change mako references to reflect your device**
## Specify phone tech before including full_phone
$(call inherit-product, vendor/cm/config/gsm.mk)
# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/common_full_phone.mk)
# Enhanced NFC
$(call inherit-product, vendor/cm/config/nfc_enhanced.mk)
# Inherit device configuration
$(call inherit-product, device/lge/mako/full_mako.mk)
## Device identifier. This must come after all inclusions
PRODUCT_DEVICE := mako
PRODUCT_NAME := cm_mako
PRODUCT_BRAND := google
PRODUCT_MODEL := Nexus 4
PRODUCT_MANUFACTURER := LGE
# Enable Torch
PRODUCT_PACKAGES += Torch
Click to expand...
Click to collapse
Save and exit by pressing ctrl+x, selecting Y then enter.
Now you're ready to build! Go back to the OP and complete the guide from where you left off.
AOSP
AOSP requires a prebuilt kernel for your device. HERE is a guide for building a kernel if you do not have a prebuilt kernel for your device
The rest coming soon...
Liquid Smooth
Coming soon...
AOKP
Code:
nano vendor/aokp/vendorsetup.sh
Add this line
add_lunch_combo aokp_geeb-userdebug
Click to expand...
Click to collapse
Save and exit by pressing ctrl+x, selecting Y then enter.
Code:
touch vendor/aokp/products/geeb.mk
Code:
nano vendor/aokp/products/geeb.mk
Add these lines
If building for CDMA network change gsm.mk to cdma.mk
# Inherit AOSP device configuration for geeb
$(call inherit-product, device/lge/geeb/full_geeb.mk)
# Inherit AOKP common bits
$(call inherit-product, vendor/aokp/configs/common.mk)
# Inherit GSM common stuff
$(call inherit-product, vendor/aokp/configs/gsm.mk)
# Setup device specific product configuration
PRODUCT_NAME := aokp_geeb
PRODUCT_BRAND := google
PRODUCT_DEVICE := geeb
PRODUCT_MODEL := Optimus G
PRODUCT_MANUFACTURER := LGE
Click to expand...
Click to collapse
Save and exit by pressing ctrl+x, selecting Y then enter.
Code:
nano vendor/aokp/products/AndroidProducts.mk
Add this line
$(LOCAL_DIR)/geeb.mk \
Click to expand...
Click to collapse
Save and exit by pressing ctrl+x, selecting Y then enter.
Now you're ready to build! Go back to the OP and complete the guide from where you left off.
CarbonDev
Coming soon...
Now you're ready to build! Go back to the OP and complete the guide from where you left off.
Edit Source
If you plan to edit the device/kernel repos for your phone you should either have used git clone to obtain your repos, or created forks of the repos to your own Github account to use in your local manifest. This way you can still do a repo sync to update the source without overwriting your changes or creating conflicts.
That being said these are the items disscused so far:
Adding Prebuilt APK's to Build
Adding Apps Via Source Code
Changing Toolchain
Cherry Picking Commits
Fixing Conflicts From Cherry Picks
Syncing Repo with Upstream Repo
Syncing Your Local Changes to Your Github Repo
Click to expand...
Click to collapse
Adding Prebuilt APK's to Build
Open the device folder for your phone. ie device/lge/geeb
Add these lines to android.mk
include $(CLEAR_VARS)
LOCAL_MODULE := Name
LOCAL_SRC_FILES := $(LOCAL_MODULE).apk
LOCAL_MODULE_TAGS := optional
LOCAL_MODULE_SUFFIX := .apk
LOCAL_MODULE_CLASS := APPS
LOCAL_CERTIFICATE := PRESIGNED
include $(BUILD_PREBUILT)
Click to expand...
Click to collapse
Name - Any name you want to asign to this apk to call for it in the build process
**NOTE** LOCAL_SRC_FILES is the location of the apk file. Above assumes it is in the root of your device folder**
Then edit your device.mk to call for your newly assigned apk
PRODUCT_PACKAGES += \
name
Click to expand...
Click to collapse
If the apk you want to add requires additional files to be added along with it, also add this
PRODUCT_COPY_FILES += \
Path-to-additional-file:Destination-path-in-finished-build
Click to expand...
Click to collapse
Path-to-additional-file - Where the file is located in your device tree that you need to add to your build
Destination-path-in-finished-build - Where in the final rom structure this file needs to be
Here is an example for adding required libs for Terminal Emulator to the geeb device tree:
PRODUCT_COPY_FILES += \
device/lge/geeb/libjackpal-androidterm3.so:system/lib/libjackpal-androidterm3.so \
device/lge/geeb/libjackpal-androidterm4.so:system/lib/libjackpal-androidterm4.so
Click to expand...
Click to collapse
Adding Apps Via Source Code
Adding apps to your build using source code is easier then adding prebuilt apks.
Example given is using Gallery2(I realize this is included with builds by default, just using it as an example)
Copy or clone your app's source code to working-dir/packages/apps in its own folder. ie. aokp/packages/Gallery2
Go into the source code folder for your app and open Android.mk
Look for this line LOCAL_PACKAGE_NAME , This will tell you what the call name for your app is
LOCAL_AAPT_FLAGS := --auto-add-overlay
LOCAL_PACKAGE_NAME := Gallery2
LOCAL_OVERRIDES_PACKAGES := Gallery Gallery3D GalleryNew3D
Click to expand...
Click to collapse
Then open device.mk from your phones device tree and add the call name for the app.
Add these lines:
PRODUCT_PACKAGES += \
Gallery2
Click to expand...
Click to collapse
Changing Toolchain
Download a new prebuilt toolchain that you wish to use
Example: Linaro 4.7 toolchain
Copy unziped prebuilt toolchain folder to working-folder/prebuilt/gcc/linux-x86/arm
Open build/envsetup.sh
Find this block of code:
# The gcc toolchain does not exists for windows/cygwin. In this case, do not reference it.
export ANDROID_EABI_TOOLCHAIN=
local ARCH=$(get_build_var TARGET_ARCH)
case $ARCH in
x86) toolchaindir=x86/i686-linux-android-$targetgccversion/bin
;;
arm) toolchaindir=arm/android-toolchain-eabi/bin
;;
mips) toolchaindir=mips/mipsel-linux-android-$targetgccversion/bin
;;
*)
echo "Can't find toolchain for unknown architecture: $ARCH"
toolchaindir=xxxxxxxxx
;;
esac
if [ -d "$gccprebuiltdir/$toolchaindir" ]; then
export ANDROID_EABI_TOOLCHAIN=$gccprebuiltdir/$toolchaindir
fi
unset ARM_EABI_TOOLCHAIN ARM_EABI_TOOLCHAIN_PATH
case $ARCH in
arm)
toolchaindir=arm/android-toolchain-eabi/bin
if [ -d "$gccprebuiltdir/$toolchaindir" ]; then
export ARM_EABI_TOOLCHAIN="$gccprebuiltdir/$toolchaindir"
ARM_EABI_TOOLCHAIN_PATH=":$gccprebuiltdir/$toolchaindir"
fi
Click to expand...
Click to collapse
Replace bold text with your toolchain folder name
The following group of instructions are for making edits to your own repo. Before using any of the info below PLEASE create your own GitHub account and Fork the repo you'd like to edit. Then clone YOUR forked repo from YOUR github account and make edits to it.
If that didn't make sence then you may want to refrain from using this for the time being.
Cherry Picking Commits
Move to the directory for the git repo you wish to add the commit to. ie kernel/lge/geeb
Code:
cd path-to-git-repo
Add the remote repo that holds the commit - This only needs to be done the first time
Code:
git remote add [COLOR="Red"]name[/COLOR] [COLOR="SeaGreen"]url[/COLOR]
name - a name you choose to identify that remote repo
url - the location of the repo ie. https://github.com/TeamPlaceholder/android_kernel_lge_gee.git
Fetch the repo
Code:
git fetch [COLOR="Red"]name[/COLOR]
Cherry pick commit
Code:
git cherry-pick [COLOR="DarkOrange"]commit-id[/COLOR]
commit-id - An unique id given to every commit. It's a long alphanumeric id shown on the commit page of your repo. ie. cc3581ff8692b517ddda8baad73a5d110568f0da
Fixing Conflicts From Cherry Picks
Somtimes when you cherry pick a commit to your repo you'll have a conflict. This is just saying that it did not see what it expected to see when adding the commit to a certain file. To fix a conflict and commit the cherry pick do as follows:
Determine which file(s) contain conflicts.
Code:
git status
This will show you edits waiting to be commited from the cherry-pick. The files shown in green accepted the changes without conflict, the files listed in red contain conflicts that need to be addressed.
Open the file in red
Code:
gedit [COLOR="DarkOrange"]Path-To-File-In-Red[/COLOR]
Press crtl+f to bring up a find window and search for head. Conflicts will be shown in the file using the following structure
<<<<<Head
<Original Code>
=======
<Code from Cherry-pick>
>>>>>Name Of Cherry Pick Commit
Click to expand...
Click to collapse
Compare the original code to the code from the cherry pick and see if anything needs to be saved. If so, merge what needs to be saved into the code from the cherry pick. Then delete the original code and the <<<< ===== >>>>> lines(everything shown in red above). In the end you should be left only with the code from the cherry pick, plus anything you may have merged to it.
Search again for 'head' to see if there are any further conflicts within that file. If there is use the same method to resolve them, if there is not save and exit the file.
Add the newly edited file to the pending commit
Code:
git add [COLOR="DarkOrange"]Path-To-File-In-Red[/COLOR]
Check for any more files that need to be addressed
Code:
git status
If you still have files in red, repeat the process above for those files.
Once all files from git status are shown in green you are ready to commit the cherry pick.
Code:
git commit
Save and exit the commit log by pressing ctrl+x
Done. That cherry pick is now commited to your repo, you can move on to the next cherry pick you wish to add.
Sync Forked Repo with Upstream(Parent) Repo
If you would like to commit to your forked repo all the commits made upstream since you forked(or previously sync'd)
Add the upstream repo - This only needs to be done the first time
Code:
git remote add [COLOR="Red"]name[/COLOR] [COLOR="SeaGreen"]url[/COLOR]
name - a name you choose to identify that remote repo
url - the location of the repo ie. https://github.com/TeamPlaceholder/android_kernel_lge_gee.git
Fetch the upstream repo
Code:
git fetch [COLOR="Red"]name[/COLOR]
Merge upstream commits
Code:
git merge [COLOR="Red"]name[/COLOR]/[COLOR="DarkOrange"]branch[/COLOR]
branch - The branch from the upstream repo you are syncing up
Syncing Your Local Changes to Your Github Repo
Check to ensure you have everything in order to push your changes
Code:
git status
If there are no conflicts/changes that need to be commited you are ready to push. If everything is good it will simply state your are x number of commits ahead
Push your commits to your GitHub account
Code:
git push
Enter your github user name then password. All your local commits will then be applied to your github repo.
More to Come...
Build Errors
Build Errors
This is way to broad a subject to cover in a post, but here are some steps to take to help get you building again.
When your build output stops without clearly saying it's finished or directing you to the created zip file, it Failed.
Sometimes it will stop with the error right at the end of the output, but not very often. Most of the time you must look up through the build output in order to locate the actual error. Sometimes they can be buried very far up, depending on the number of jobs being built.
Here is an example of what you are looking for:
hardware/qcom/display-caf/libgralloc/framebuffer.cpp:116:39: error: 'MSMFB_DISPLAY_COMMIT' was not declared in this scope
Click to expand...
Click to collapse
File having the error
Line in the file where the error occurs
Error that has occured
The quickest way to locate the errors in the build output is the search 'ctrl+shfit+F' for ': error:'
Once you have located your error(s), you can begin troubleshooting to get past them. Start by opening the File having the error and going to the Line in the file where the error occurs. Though without programing knowledge you may not make much sense of it, it's always good to start familiarizing yourself with the code. If you're not able to correct the issue this is where google will come in very handy.
Quite often if you search simply for the Error that has occured exactly as it appears, you'll find its an error that has been encountered many times over and solutions are availible within the first couple of results in a google search.
Should all else fail Post a question and see what suggestions come up.
Here are a few common build errors that I have come across and some solutions for them, again this is by no means a one stop for build erros. Google...Google...Then try to post your error and see who can help if your still stuck. The more you fix by yourself the more it feels like YOUR build.
make: *** No rule to make target `Example_File'. Stop.
Click to expand...
Click to collapse
It can't find the file in question. This can be a incorrect path in a makefile, a missing file or a typo.
last one
Finally usefull guide! not only theory. Thank you very much!
Nice job. Just one thing: when using our sources, the cm-10.2-merge is the best kernel branch. Msm-3.10 is our bleeding edge and hopefully will be fully working soon (just got it to build today, so we'll see). The update branch is broken though. Let me know if you want to contribute to our Git so I can add you to the team, or if you have any suggestions on how to make our rom and kernel better.
Sent from my LG-LS970 using xda app-developers app
xboxfanj said:
Nice job. Just one thing: when using our sources, the cm-10.2-merge is the best kernel branch. Msm-3.10 is our bleeding edge and hopefully will be fully working soon (just got it to build today, so we'll see). The update branch is broken though. Let me know if you want to contribute to our Git so I can add you to the team, or if you have any suggestions on how to make our rom and kernel better.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the info, updated quide to reflect.
i have a cherry mobile burst phone its running ics,i a generic phone a clone i dont know where it came from i mean the build i cant find a source or a build repo , i really want to build a rom for my phone cause it seems ics is not compatible for the phone..it only has 512 ram and 1ghz dualcore processor..it could run smoothly i think with gingerbread but i cant find a tutorial to donwgrade it to gingerbread it seems impossible because of lack of support for the device and it came up with ics..i just dont know what to do any more my computer is linux mint 13 2gb ram 1ghz amd anthlon 2 ,70gb hd..i cant build a rom to this computer..
Changing Toolchain
Download a new prebuilt toolchain that you wish to use
Example: Linaro 4.7 toolchain
Copy unziped prebuilt toolchain folder to working-folder/prebuilt/gcc/linux-x86/arm
Open build/envsetup.sh
Find this block of code:
Quote:
# The gcc toolchain does not exists for windows/cygwin. In this case, do not reference it.
export ANDROID_EABI_TOOLCHAIN=
local ARCH=$(get_build_var TARGET_ARCH)
case $ARCH in
x86) toolchaindir=x86/i686-linux-android-$targetgccversion/bin
;;
arm) toolchaindir=arm/android-toolchain-eabi/bin
;;
mips) toolchaindir=mips/mipsel-linux-android-$targetgccversion/bin
;;
*)
echo "Can't find toolchain for unknown architecture: $ARCH"
toolchaindir=xxxxxxxxx
;;
esac
if [ -d "$gccprebuiltdir/$toolchaindir" ]; then
export ANDROID_EABI_TOOLCHAIN=$gccprebuiltdir/$toolchaindir
fi
unset ARM_EABI_TOOLCHAIN ARM_EABI_TOOLCHAIN_PATH
case $ARCH in
arm)
toolchaindir=arm/android-toolchain-eabi/bin
if [ -d "$gccprebuiltdir/$toolchaindir" ]; then
export ARM_EABI_TOOLCHAIN="$gccprebuiltdir/$toolchaindir"
ARM_EABI_TOOLCHAIN_PATH=":$gccprebuiltdir/$toolchaindir"
fi
Replace bold text with your toolchain folder name
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I did what you said and i keep getting this error
"/arm-eabi-gcc: No such file or directory
make[4]: *** [scripts/mod/empty.o] Error 1
make[3]: *** [scripts/mod] Error 2
make[2]: *** [scripts] Error 2
make[2]: *** Waiting for unfinished jobs...."
Here's what my envsetup.sh looks like
# The gcc toolchain does not exists for windows/cygwin. In this case, do not reference it.
export ANDROID_EABI_TOOLCHAIN=
local ARCH=$(get_build_var TARGET_ARCH)
case $ARCH in
x86) toolchaindir=x86/i686-linux-android-$targetgccversion/bin
;;
arm) toolchaindir=arm/arm-eabi-linaro-4.6.2/bin
;;
mips) toolchaindir=mips/mipsel-linux-android-$targetgccversion/bin
;;
*)
echo "Can't find toolchain for unknown architecture: $ARCH"
toolchaindir=xxxxxxxxx
;;
esac
if [ -d "$gccprebuiltdir/$toolchaindir" ]; then
export ANDROID_EABI_TOOLCHAIN=$gccprebuiltdir/$toolchaindir
fi
unset ARM_EABI_TOOLCHAIN ARM_EABI_TOOLCHAIN_PATH
case $ARCH in
arm)
toolchaindir=arm/arm-eabi-linaro-4.6.2/bin
if [ -d "$gccprebuiltdir/$toolchaindir" ]; then
export ARM_EABI_TOOLCHAIN="$gccprebuiltdir/$toolchaindir"
ARM_EABI_TOOLCHAIN_PATH=":$gccprebuiltdir/$toolchaindir"
fi
Click to expand...
Click to collapse
my linaro folder is called "arm-eabi-linaro-4.6.2" and it is placed under "/prebuilts/gcc/linux-x86/arm/arm-eabi-linaro-4.6.2"
what am i doing wrong?
thanks!
ryukiri said:
I did what you said and i keep getting this error
"/arm-eabi-gcc: No such file or directory
make[4]: *** [scripts/mod/empty.o] Error 1
make[3]: *** [scripts/mod] Error 2
make[2]: *** [scripts] Error 2
make[2]: *** Waiting for unfinished jobs...."
Click to expand...
Click to collapse
Where did you get your linaro toolchain from?
go into your linaro directory/bin do you see arm-eabi**** files?
Sounds like it's only the arm-linux-androideabi*** files in there.
Get the prebuilt toolchains right from Linaro It will take a little looking around to find the 4.6. The prebuilt toolchains for each release are in Components>Android>Toolchain Most of them are 4.7 and 4.8 so like I said, it may take some looking around.
I believe(though not 100%) the arm-eabi are used for the kernel, the arm-linux-androideabi for the rom.
The top line you change in envsetup.sh is for the rom toolchain, second place you change is for the kernel toolchain. You can use two different toolchains here. I use sabermod 4.9 for my rom and linaro 4.7 for the kernel
Haze028 said:
Where did you get your linaro toolchain from?
go into your linaro directory/bin do you see arm-eabi**** files?
Sounds like it's only the arm-linux-androideabi*** files in there.
Get the prebuilt toolchains right from Linaro It will take a little looking around to find the 4.6. The prebuilt toolchains for each release are in Components>Android>Toolchain Most of them are 4.7 and 4.8 so like I said, it may take some looking around.
I believe(though not 100%) the arm-eabi are used for the kernel, the arm-linux-androideabi for the rom.
The top line you change in envsetup.sh is for the rom toolchain, second place you change is for the kernel toolchain. You can use two different toolchains here. I use sabermod 4.9 for my rom and linaro 4.7 for the kernel
Click to expand...
Click to collapse
hmm, i forgot where i got it from, i might have gotten it by following this http://forum.xda-developers.com/showthread.php?t=1988315
Can I use 4.7 or 4.8 though?
Ok so inside my linaro directory/bin, i see many arm-eabi**** files (attached screenshot)
Do you think you can link to me the exact toolchains you used so I can start with something that works and then start trying different ones later?
ryukiri said:
Can I use 4.7 or 4.8 though?
Do you think you can link to me the exact toolchains you used so I can start with something that works and then start trying different ones later?
Click to expand...
Click to collapse
I would stick with 4.7 toolchain. 4.6 is quite old, and 4.8 doesn't seem to play very nice. (i'm probably too noob to get it working)
This is the linaro 4.7 toolchain I use.
Hopefully that'll help ya get going.
Haze028 said:
I would stick with 4.7 toolchain. 4.6 is quite old, and 4.8 doesn't seem to play very nice. (i'm probably too noob to get it working)
This is the linaro 4.7 toolchain I use.
Hopefully that'll help ya get going.
Click to expand...
Click to collapse
alright thanks. Ill test it out and report back later
I got the same error.. D:
"/arm-eabi-gcc: No such file or directory
make[4]: *** [scripts/mod/empty.o] Error 1
make[3]: *** [scripts/mod] Error 2
make[2]: *** [scripts] Error 2
make[2]: *** Waiting for unfinished jobs...."
# The gcc toolchain does not exists for windows/cygwin. In this case, do not reference it.
export ANDROID_EABI_TOOLCHAIN=
local ARCH=$(get_build_var TARGET_ARCH)
case $ARCH in
x86) toolchaindir=x86/i686-linux-android-$targetgccversion/bin
;;
arm) toolchaindir=arm/android-toolchain-eabi/bin
;;
mips) toolchaindir=mips/mipsel-linux-android-$targetgccversion/bin
;;
*)
echo "Can't find toolchain for unknown architecture: $ARCH"
toolchaindir=xxxxxxxxx
;;
esac
if [ -d "$gccprebuiltdir/$toolchaindir" ]; then
export ANDROID_EABI_TOOLCHAIN=$gccprebuiltdir/$toolchaindir
fi
unset ARM_EABI_TOOLCHAIN ARM_EABI_TOOLCHAIN_PATH
case $ARCH in
arm)
toolchaindir=arm/android-toolchain-eabi/bin
if [ -d "$gccprebuiltdir/$toolchaindir" ]; then
export ARM_EABI_TOOLCHAIN="$gccprebuiltdir/$toolchaindir"
ARM_EABI_TOOLCHAIN_PATH=":$gccprebuiltdir/$toolchaindir"
fi
Click to expand...
Click to collapse
EDIT: after some research, i found out that all the files in my bin folder are 32 bit executable files. So i believe i need a 64 bit toolchain. Do you know where I could find one?
EDIT2: I found that for linux they need to install "ia32-libs" to run 32bit executables source. But the thing is, I'm using a mac...
EDIT3: nevermind, i got it to work. thanks anyway
aokp build error
Can you point me in the right direction to fix this error http://pastebin.com/GZmteWUu.
Recon Freak said:
Can you point me in the right direction to fix this error http://pastebin.com/GZmteWUu.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=47947423&postcount=175
Try this....
CarbonDev
Coming soon...
.
Click to expand...
Click to collapse
Thanks for the guide so far. Is there an eta for Carbon roms as I'm struggling to get my to build. Or AOSP?
Haze, to change tool chains, you can also set TARGET_TOOLS_PREFIX ?= prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8-linaro/bin/arm-linux-androideabi- in boardconfig (sub in the right path obviously).
Sent from my Optimus G using xda app-developers app
Im trying to compile a module (frandom module) for 2.6.35 Kernel
The make file of the module looks like this
Code:
# Makefile for 2.6 kernels
DHDCFLAGS = -w
KDIR := /home/gakukid991/Desktop/FinalKernel/desire_kernel_35-kitkat
obj-m := frandom.o
PWD := $(shell pwd)
EXTRA_CFLAGS = $(DHDCFLAGS)
default:
$(MAKE) ARCH=arm CROSS_COMPILE=~/android/kernel/arm-linux-gnueabi-linaro_4.9.3-2014.11/bin/arm-eabi- -C $(KDIR) SUBDIRS=$(PWD) modules
clean:
$(MAKE) -C $(KERNEL_DIR) SUBDIRS=$(PWD) clean
Now when i try to compile the file by typing make on terminal it gives me this error
Code:
make ARCH=arm CROSS_COMPILE=~/android/kernel/arm-linux-gnueabi-linaro_4.9.3-2014.11/bin/arm-eabi- -C /home/gakukid991/Desktop/FinalKernel/desire_kernel_35-kitkat SUBDIRS=/home/gakukid991/Desktop/frandomModule/frandom-1.1 modules
make[1]: Entering directory `/home/gakukid991/Desktop/FinalKernel/desire_kernel_35-kitkat'
CC [M] /home/gakukid991/Desktop/frandomModule/frandom-1.1/frandom.o
In file included from include/linux/gfp.h:4:0,
from include/linux/kmod.h:22,
from include/linux/module.h:13,
from /home/gakukid991/Desktop/frandomModule/frandom-1.1/frandom.c:17:
include/linux/mmzone.h:18:30: fatal error: generated/bounds.h: No such file or directory
#include <generated/bounds.h>
^
compilation terminated.
make[2]: *** [/home/gakukid991/Desktop/frandomModule/frandom-1.1/frandom.o] Error 1
make[1]: *** [_module_/home/gakukid991/Desktop/frandomModule/frandom-1.1] Error 2
make[1]: Leaving directory `/home/gakukid991/Desktop/FinalKernel/desire_kernel_35-kitkat'
make: *** [default] Error 2
Ive tried to delete the generated/bounds.h text from mmzone but then it starts giving me other erros (i tryed deleted all of them but seems like its no good , new errors show up after i delete a text from the other one :'( )
Please Help , I want to put this module on my HD2 to make it faster
Thanks
bump
Hi folks,
(New to the forums, tho I've been reading a bit...)
I'm trying to build the Copperhead OS version of Android (marshmallow, for a 2014 Nexus 5) and have run into an issue that I can't seem to get around. Everything seems fine until I get to this:
Code:
target Generated: libv8 <= out/host/linux-x86/bin/v8_mksnapshot.arm
/bin/bash: out/host/linux-x86/bin/v8_mksnapshot.arm: No such file or directory
make: *** [out/target/product/generic/gen/STATIC_LIBRARIES/libv8_intermediates/snapshot_arm.cc] Error 127
...which kills the build. I've been through the makefile in 'external/v8/Android.mksnapshot.mk', which seems to be controlling this part of the build, but as far as I can tell the name of the right src to compile is generated on the fly -- and I don't know enough about this to work past it in a reasonable amount of time. Any hints?
Thanks!
-j
Actually, it looks like the thing that's missing (v8_mksnapshot.arm) is what's used to compile generated source -- the compiler isn't complaining about the generated source itself:
Code:
# Generate snapshot.cc
ifeq ($(ENABLE_V8_SNAPSHOT),true)
SNAP_GEN := $(generated_sources)/snapshot_$(TARGET_ARCH).cc
MKSNAPSHOT := $(HOST_OUT_EXECUTABLES)/v8_mksnapshot.$(TARGET_ARCH)
$(SNAP_GEN): PRIVATE_CUSTOM_TOOL = $(HOST_OUT_EXECUTABLES)/v8_mksnapshot.$(TARGET_ARCH) --log-snapshot-positions --logfile $(dir [email protected])/v8-snapshot_$(TARGET_ARCH).log [email protected]
$(SNAP_GEN): $(MKSNAPSHOT)
$(transform-generated-source)
LOCAL_GENERATED_SOURCES_$(TARGET_ARCH) += $(SNAP_GEN)
...except that 'v8_mksnapshot.arm' is definitely in 'out/host/linux-x86/bin/'. When I try to run that executable:
Code:
[email protected]:/deploy/copperheados-marshmallow-release$ ./out/host/linux-x86/bin/v8_mksnapshot.arm
-bash: ./out/host/linux-x86/bin/v8_mksnapshot.arm: No such file or directory
[email protected]:/deploy/copperheados-marshmallow-release$ ls -l ./out/host/linux-x86/bin/v8_mksnapshot.arm
-rwxr-xr-x 1 admin admin 181048624 Sep 17 15:34 ./out/host/linux-x86/bin/v8_mksnapshot.arm
That usually means some library on which the executable depends is missing.
Sony just posted a guide in their site to build AOSP 9.0 for our devices.
https://developer.sony.com/develop/...build-instructions/build-aosp-android-p-9-0-0
I try to build this next week stay tuned
VinBenzin810 said:
I try to build this next week stay tuned
Click to expand...
Click to collapse
That's great! Thanks a lot!
Sent from my [device_name] using XDA-Developers Legacy app
VinBenzin810 said:
I try to build this next week stay tuned
Click to expand...
Click to collapse
TriboDoP said:
That's great! Thanks a lot!
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm actually trying to build it myself now. It's the first time I'm doing it, but their guide is clear and easy to follow. I just need someone to test it when I'm done, my own device isn't unlocked yet and I kinda don't want to unless the bugs are minor.
I'm at step 4 downloading/syncing it right now. I'll let you know when I'm done & upload it in the OP.
Edit: I'll leave it to someone who knows it better. I got stuck at building it (step 5.3), getting an error at the first 10 seconds.
Redcalibur said:
I'm actually trying to build it myself now. It's the first time I'm doing it, but their guide is clear and easy to follow. I just need someone to test it when I'm done, my own device isn't unlocked yet and I kinda don't want to unless the bugs are minor.
I'm at step 4 downloading/syncing it right now. I'll let you know when I'm done & upload it in the OP.
Edit: I'll leave it to someone who knows it better. I got stuck at building it (step 5.3), getting an error at the first 10 seconds.
Click to expand...
Click to collapse
Thanks for trying anyway! Being new to sony i also don't want to breake the camera (altough thankfully there is a custom kernel + twrp + camera-fix) so i am uncertain if i should wait for official android 9 or AOSP android 9 (customroms would be even better).
On my other devices (samsung,oneplus) i use only customroms but at the moment there is very little choice here.
But i love the xz1 with the 835 it is fast as lightning!
Regards!
Sent from my [device_name] using XDA-Developers Legacy app
Redcalibur said:
I'm actually trying to build it myself now. It's the first time I'm doing it, but their guide is clear and easy to follow. I just need someone to test it when I'm done, my own device isn't unlocked yet and I kinda don't want to unless the bugs are minor.
I'm at step 4 downloading/syncing it right now. I'll let you know when I'm done & upload it in the OP.
Edit: I'll leave it to someone who knows it better. I got stuck at building it (step 5.3), getting an error at the first 10 seconds.
Click to expand...
Click to collapse
Which Error you get ? Write me an pn
VinBenzin810 said:
Which Error you get ? Write me an pn
Click to expand...
Click to collapse
Hi, I sent the PM but couldn't find it in between my "sent messages" folder. I'll just send it here too for future references aswell.
So I tried to reproduce the error after running a ./repo_update.sh, but got another error. This time, it progressed a little further. Here are some screens of my terminal.
https://imgur.com/a/4AdBMrp
Redcalibur said:
Hi, I sent the PM but couldn't find it in between my "sent messages" folder. I'll just send it here too for future references aswell.
So I tried to reproduce the error after running a ./repo_update.sh, but got another error. This time, it progressed a little further. Here are some screens of my terminal.
https://imgur.com/a/4AdBMrp
Click to expand...
Click to collapse
I send you an PM look there
Redcalibur said:
Hi, I sent the PM but couldn't find it in between my "sent messages" folder. I'll just send it here too for future references aswell.
So I tried to reproduce the error after running a ./repo_update.sh, but got another error. This time, it progressed a little further. Here are some screens of my terminal.
https://imgur.com/a/4AdBMrp
Click to expand...
Click to collapse
Except
- repo_update.sh hardware/qcom/gps
- vendor-qcom-opensource-location
Poplar xperiadev pie is "today build-able" but doesn't boot yet; good news are xperiadev moves to kernel 4.9; will probably have to wait for SoftwareBinairies v16 Pie specifics...
Will upload poplar_Pie as soon as it will boot...
btw: I've uploaded latest twrp 3.2.3 with OEM.img flash support (and BusyBox) https://androidfilehost.com/?fid=1322778262903981152
Any news about the build?
Getting below error .. doesn't seem like kernel is syncing. Any ideas?
[ 66% 2/3] glob frameworks/base/core/java/**/*.java
ninja: error: 'kernel/sony/msm-4.9/common-kernel/kernel-dtb-poplar', needed by 'out/target/product/poplar/kernel', missing and no known rule to make it
16:01:44 ninja failed with: exit status 1
#### failed to build some targets (07:25 (mm:ss)) ####
rsabluebulls said:
Getting below error .. doesn't seem like kernel is syncing. Any ideas?
[ 66% 2/3] glob frameworks/base/core/java/**/*.java
ninja: error: 'kernel/sony/msm-4.9/common-kernel/kernel-dtb-poplar', needed by 'out/target/product/poplar/kernel', missing and no known rule to make it
16:01:44 ninja failed with: exit status 1
#### failed to build some targets (07:25 (mm:ss)) ####
Click to expand...
Click to collapse
Just delete kernel/sony/msm-4.9/common-kernel directory and your build will go through a complete rebuild of dbt and kernel.
But without Sony Pie OEm vendor image release, the phone will hang on logo...
Thank you oF2pks - I managed to get further with the compile. This is the next error... any help please?
Copying resources from program jar [/Volumes/Mac_Drive/android-pe/out/target/common/obj/APPS/messaging_intermediates/classes.jar]
[ 60% 52636/87279] build out/target/common/obj/PACKAGING/hiddenapi-light-greylist.txt
uniq: illegal option -- D
usage: uniq [-c | -d | -u] [-i] [-f fields] [-s chars] [input [output]]
[ 60% 52851/87279] build out/target/common/obj/PACKAGING/hiddenapi-dark-greylist.txt
uniq: illegal option -- D
usage: uniq [-c | -d | -u] [-i] [-f fields] [-s chars] [input [output]]
[ 60% 52893/87279] build out/target/common/obj/PACKAGING/hiddenapi-blacklist.txt
uniq: illegal option -- D
usage: uniq [-c | -d | -u] [-i] [-f fields] [-s chars] [input [output]]
[ 60% 52978/87279] Yacc: ss <= external/iproute2/misc/ssfilter.y
external/iproute2/misc/ssfilter.y: conflicts: 35 shift/reduce
[ 61% 53613/87279] target C: libext4 <= out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates/libipt_ECN.c
FAILED: out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates/libipt_ECN.o
/bin/bash -c "prebuilts/misc/darwin-x86/ccache/ccache prebuilts/clang/host/darwin-x86/clang-4691093/bin/clang -I external/iptables/extensions/../include/ -I external/iptables/extensions/.. -I out/target/product/poplar/gen/STATIC_LIBRARIES/libext4_intermediates -I external/iptables/extensions -I external/iptables/extensions -I out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates -I out/target/product/poplar/gen/STATIC_LIBRARIES/libext4_intermediates -I libnativehelper/include_jni \$(cat out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates/import_includes) -I system/core/include -I system/media/audio/include -I hardware/libhardware/include -I hardware/libhardware_legacy/include -I hardware/ril/include -I libnativehelper/include -I frameworks/native/include -I frameworks/native/opengl/include -I frameworks/av/include -isystem out/target/product/poplar/obj/include -isystem kernel/sony/msm-4.9/common-headers/kernel-headers -isystem bionic/libc/include -isystem bionic/libc/kernel/uapi -isystem bionic/libc/kernel/uapi/asm-arm64 -isystem bionic/libc/kernel/android/scsi -isystem bionic/libc/kernel/android/uapi -c -Werror=implicit-function-declaration -DANDROID -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith -no-canonical-prefixes -DNDEBUG -UDEBUG -fno-exceptions -Wno-multichar -O2 -g -fno-strict-aliasing -D__compiler_offsetof=__builtin_offsetof -Werror=int-conversion -Wno-reserved-id-macro -Wno-format-pedantic -Wno-unused-command-line-argument -fcolor-diagnostics -Wno-expansion-to-defined -Wno-zero-as-null-pointer-constant -fdebug-prefix-map=\$PWD/= -ffunction-sections -fdata-sections -fno-short-enums -funwind-tables -fstack-protector-strong -Wa,--noexecstack -D_FORTIFY_SOURCE=2 -Wstrict-aliasing=2 -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Werror=date-time -Werror=format-security -nostdlibinc -march=armv8-a -mcpu=cortex-a53 -target aarch64-linux-android -Bprebuilts/gcc/darwin-x86/aarch64/aarch64-linux-android-4.9/aarch64-linux-android/bin -std=gnu99 -DNO_SHARED_LIBS=1 -DXTABLES_INTERNAL -D_LARGEFILE_SOURCE=1 -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DENABLE_IPV4 -DENABLE_IPV6 -D__ANDROID__ -Wall -Werror -Wno-format -Wno-missing-field-initializers -Wno-pointer-arith -Wno-pointer-bool-conversion -Wno-sign-compare -Wno-tautological-pointer-compare -Wno-unused-parameter -fPIC -D_USING_LIBCXX -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -Werror=address-of-temporary -Werror=return-type -Wno-tautological-constant-compare -Wno-null-pointer-arithmetic -Wno-enum-compare -Wno-enum-compare-switch -MD -MF out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates/libipt_ECN.d -o out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates/libipt_ECN.o out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates/libipt_ECN.c"
In file included from out/target/product/poplar/obj/STATIC_LIBRARIES/libext4_intermediates/libipt_ECN.c:11:
external/iptables/extensions/../include/linux/netfilter_ipv4/ipt_ECN.h:13:10: fatal error: 'linux/netfilter/xt_DSCP.h' file not found
#include <linux/netfilter/xt_DSCP.h>
^~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
[ 61% 53616/87279] target StaticLib: libv8 (out/target/product/poplar/obj/STATIC_LIBRARIES/libv8_intermediates/libv8.a)
ninja: build stopped: subcommand failed.
18:47:24 ninja failed with: exit status 1
#### failed to build some targets (05:24:19 (hh:mm:ss)) ####
rsabluebulls said:
external/iptables/extensions/../include/linux/netfilter_ipv4/ipt_ECN.h:13:10: fatal error: 'linux/netfilter/xt_DSCP.h' file not found
#include <linux/netfilter/xt_DSCP.h>
^~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
[ 61% 53616/87279] target StaticLib: libv8 (out/target/product/poplar/obj/STATIC_LIBRARIES/libv8_intermediates/libv8.a)
ninja: build stopped: subcommand failed.
18:47:24 ninja failed with: exit status 1
#### failed to build some targets (05:24:19 (hh:mm:ss)) ####
Click to expand...
Click to collapse
Noob here. Does this (https://medium.com/@christopherney/building-android-o-with-a-mac-da07e8bd94f9) help?
christopherney said:
If the following error is raised during the Android building process:
external/iptables/extensions/../include/linux/netfilter_ipv4/ipt_ECN.h:13:10: fatal error: 'linux/netfilter/xt_DSCP.h' file not found
#include <linux/netfilter/xt_DSCP.h>
Please check the filename user or lower case. Remember that the Android building process is case-sensitive.
Click to expand...
Click to collapse
Does anyone tried any Android Pie Treble GSI roms on our device? is it working fine?
Anyone able to assist with the missing separator error in Android.mk which I'm receiving now?
many thanks
--------------------------
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=9
TARGET_PRODUCT=aosp_g8341
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=cortex-a73
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=cortex-a73
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=darwin
HOST_OS_EXTRA=Darwin-17.7.0-x86_64-10.13.6
HOST_BUILD_TYPE=release
BUILD_ID=PPR1.180610.009
OUT_DIR=out
============================================
ninja: no work to do.
ninja: no work to do.
wildcard(out/target/product/poplar/clean_steps.mk) was changed, regenerating...
out/build-aosp_g8341.ninja is missing, regenerating...
[2/947] including art/Android.mk ...
art/build/Android.common.mk:50: warning: unsupported HOST_ARCH=x86_64
[119/947] including device/sony/common/Android.mk ...
hardware/qcom/gps/sdm845/android/Android.mk:48: error: missing separator.
19:53:11 ckati failed with: exit status 1
#### failed to build some targets (57 seconds) ####
arslancn said:
Does anyone tried any Android Pie Treble GSI roms on our device? is it working fine?
Click to expand...
Click to collapse
I tested some ROMs, but I will restart them in Sony LOGO. I don't know if anyone is successful. Maybe I still need to flash something.
Anyone come across a StaticLib: libv8src_32 related compiling issue like mine shown in the log below?
Many thanks - got up to 64% clean build...
make[3]: *** Waiting for unfinished jobs....
INSTALL usr/include/scsi/ufs/ (2 files)
INSTALL usr/include/linux/caif/ (2 files)
INSTALL usr/include/linux/byteorder/ (2 files)
INSTALL usr/include/linux/can/ (5 files)
sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
make[4]: *** [usr/include/linux/byteorder/.install] Error 1
make[4]: *** [usr/include/linux/caif/.install] Error 1
make[4]: *** [usr/include/linux/can/.install] Error 1
make[4]: *** [usr/include/scsi/ufs/.install] Error 1
make[3]: *** [can] Error 2
make[3]: *** [caif] Error 2
make[3]: *** [byteorder] Error 2
make[3]: *** [ufs] Error 2
make[2]: *** [linux] Error 2
make[2]: *** [scsi] Error 2
make[1]: *** [headers_install] Error 2
make: *** [sub-make] Error 2
[ 64% 56247/87336] target StaticLib: libv8src_32 (out/target/product/poplar/obj_arm/STATIC_LIBRARIES/libv8src_intermediates/libv8src.a)
ninja: build stopped: subcommand failed.
15:16:21 ninja failed with: exit status 1
#### failed to build some targets (49:07 (mm:ss)) ####
Hi all, anyone perhaps have an idea on the below error or perhaps came across it before? (PS. 8.1 ASOP Sony builds without any issues, latest SEP release), this is for Android Pie latest asop
[ 63% 55359/87336] Building Kernel Headers
FAILED: /Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ/.headers_install_stamp
/bin/bash -c "(if [ ! -z "aosp_yoshino_poplar_defconfig" ]; then rm -f ..//Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ/.config; make -j10 -C kernel/sony/msm-4.9/kernel O=/Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE="/Volumes/Extra/androidp_r06/prebuilts/misc/darwin-x86/ccache/ccache aarch64-linux-android-" aosp_yoshino_poplar_defconfig; make -j10 -C kernel/sony/msm-4.9/kernel O=/Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE="/Volumes/Extra/androidp_r06/prebuilts/misc/darwin-x86/ccache/ccache aarch64-linux-android-" headers_install; fi ) && (if [ "aosp_yoshino_poplar_defconfig" != "aosp_yoshino_poplar_defconfig" ]; then echo "Used a different defconfig for header generation"; rm -f ..//Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ/.config; make -j10 -C kernel/sony/msm-4.9/kernel O=/Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE="/Volumes/Extra/androidp_r06/prebuilts/misc/darwin-x86/ccache/ccache aarch64-linux-android-" aosp_yoshino_poplar_defconfig; fi ) && (if [ ! -z "" ]; then echo "Overriding kernel config with ''"; echo >> /Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ/.config; make -j10 -C kernel/sony/msm-4.9/kernel O=/Volumes/Extra/androidp_r06/out/target/product/poplar/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE="/Volumes/Extra/androidp_r06/prebuilts/misc/darwin-x86/ccache/ccache aarch64-linux-android-" oldconfig; fi )"
GEN ./Makefile
#
# configuration written to .config
#
https://developer.sony.com/file/dow...-for-aosp-pie-android-9-0-kernel-4-9-yoshino/ this link maybe useful for you guys