Database Develop

M source has posted for AOSP. Compiling issues.

Has anyone gotten M to build?
Just did an init(1), sync, install binaries(2), lunch, but then make fails after only a few minutes in.
Here are the last few lines before it fails I can't make any sense of it:
Code:
including ./system/media/camera/src/Android.mk ...
including ./system/media/camera/tests/Android.mk ...
including ./system/media/radio/src/Android.mk ...
including ./system/netd/Android.mk ...
including ./system/security/keystore-engine/Android.mk ...
including ./system/security/keystore/Android.mk ...
including ./system/security/softkeymaster/Android.mk ...
including ./system/vold/Android.mk ...
including ./tools/external/fat32lib/Android.mk ...
including ./vendor/lge/hammerhead/proprietary/Android.mk ...
including ./vendor/qcom/hammerhead/proprietary/Android.mk ...
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
PRODUCT_COPY_FILES vendor/broadcom/hammerhead/proprietary/bcm4335c0.hcd:system/vendor/firmware/bcm4335c0.hcd:broadcom ignored.
build/core/Makefile:34: warning: overriding recipe for target 'out/target/product/hammerhead/system/lib/hw/gps.msm8974.so'
build/core/base_rules.mk:559: warning: ignoring old recipe for target 'out/target/product/hammerhead/system/lib/hw/gps.msm8974.so'
build/core/Makefile:34: warning: overriding recipe for target 'out/target/product/hammerhead/system/lib/libgps.utils.so'
build/core/base_rules.mk:559: warning: ignoring old recipe for target 'out/target/product/hammerhead/system/lib/libgps.utils.so'
build/core/Makefile:34: warning: overriding recipe for target 'out/target/product/hammerhead/system/lib/libloc_core.so'
build/core/base_rules.mk:559: warning: ignoring old recipe for target 'out/target/product/hammerhead/system/lib/libloc_core.so'
build/core/Makefile:34: warning: overriding recipe for target 'out/target/product/hammerhead/system/lib/libloc_eng.so'
build/core/base_rules.mk:559: warning: ignoring old recipe for target 'out/target/product/hammerhead/system/lib/libloc_eng.so'
No private recovery resources for TARGET_DEVICE hammerhead
Import includes file: out/host/linux-x86/obj/EXECUTABLES/validatekeymaps_intermediates/import_includes
host C: libcompiler_rt-extras <= external/compiler-rt/lib/builtins/mulodi4.c
Import includes file: out/host/linux-x86/obj/STATIC_LIBRARIES/libc++_static_intermediates/import_includes
prebuilts/clang/linux-x86/host/3.6/bin/clang: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
build/core/binary.mk:801: recipe for target 'out/host/linux-x86/obj/STATIC_LIBRARIES/libcompiler_rt-extras_intermediates/lib/builtins/mulodi4.o' failed
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/libcompiler_rt-extras_intermediates/lib/builtins/mulodi4.o] Error 127
make: *** Waiting for unfinished jobs....
host C++: libc++abi <= external/libcxxabi/src/abort_message.cpp
prebuilts/clang/linux-x86/host/3.6/bin/clang++: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
build/core/binary.mk:706: recipe for target 'out/host/linux-x86/obj/STATIC_LIBRARIES/libc++abi_intermediates/src/abort_message.o' failed
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/libc++abi_intermediates/src/abort_message.o] Error 127
#### make failed to build some targets (01:08 (mm:ss)) ####
1. repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.0_r1
2. https://developers.google.com/android/nexus/drivers#hammerheadmra58k

I built yesterday on opensuse without issues.
Go with the master branch, they merged it with the 6.0.0_r1 tag:
https://groups.google.com/d/topic/android-building/KuVIYWOcXMo/discussion

ezio84 said:
I built yesterday on opensuse without issues.
Go with the master branch, they merged it with the 6.0.0_r1 tag:
https://groups.google.com/d/topic/android-building/KuVIYWOcXMo/discussion
Click to expand...
Click to collapse
So you're telling me this error didn't occur with openSuse? Damn it. Might be time to ditch Arch and join the club. Oh, it's almost the same error as the op. Any thoughts I'm all ears.
Code:
prebuilts/clang/linux-x86/host/3.6/bin/clang++ -fno-exceptions -Wno-multichar -m64 -Wa,--noexecstack -fPIC -no-canonical-prefixes -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector -D__STDC_FORMAT_MACROS -D__STDC_CONSTANT_MACROS -DANDROID -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith -O2 -g -fno-strict-aliasing -DNDEBUG -UDEBUG -D__compiler_offsetof=__builtin_offsetof -Werror=int-conversion -Wno-reserved-id-macro -Wno-format-pedantic -Wno-unused-command-line-argument -fcolor-diagnostics --gcc-toolchain=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 --gcc-toolchain=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 --sysroot=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/sysroot -target x86_64-linux-gnu -Wsign-promo -Wno-inconsistent-missing-override --gcc-toolchain=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 --sysroot=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/sysroot -isystem prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8 -isystem prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8/x86_64-linux -isystem prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8/backward -target x86_64-linux-gnu -c -std=c++11 -g -W -Wall -MMD -MP -O -DNOLOG -o out/host/linux-x86/obj/EXECUTABLES/ckati_intermediates/command.o build/kati/command.cc
prebuilts/clang/linux-x86/host/3.6/bin/clang++: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
build/kati/Makefile.ckati:82: recipe for target 'out/host/linux-x86/obj/EXECUTABLES/ckati_intermediates/command.o' failed
make: *** [out/host/linux-x86/obj/EXECUTABLES/ckati_intermediates/command.o] Error 127

theesotericone said:
So you're telling me this error didn't occur with openSuse? Damn it. Might be time to ditch Arch and join the club. Oh, it's almost the same error as the op. Any thoughts I'm all ears.
Code:
prebuilts/clang/linux-x86/host/3.6/bin/clang++ -fno-exceptions -Wno-multichar -m64 -Wa,--noexecstack -fPIC -no-canonical-prefixes -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector -D__STDC_FORMAT_MACROS -D__STDC_CONSTANT_MACROS -DANDROID -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith -O2 -g -fno-strict-aliasing -DNDEBUG -UDEBUG -D__compiler_offsetof=__builtin_offsetof -Werror=int-conversion -Wno-reserved-id-macro -Wno-format-pedantic -Wno-unused-command-line-argument -fcolor-diagnostics --gcc-toolchain=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 --gcc-toolchain=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 --sysroot=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/sysroot -target x86_64-linux-gnu -Wsign-promo -Wno-inconsistent-missing-override --gcc-toolchain=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 --sysroot=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/sysroot -isystem prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8 -isystem prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8/x86_64-linux -isystem prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8/backward -target x86_64-linux-gnu -c -std=c++11 -g -W -Wall -MMD -MP -O -DNOLOG -o out/host/linux-x86/obj/EXECUTABLES/ckati_intermediates/command.o build/kati/command.cc
prebuilts/clang/linux-x86/host/3.6/bin/clang++: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
build/kati/Makefile.ckati:82: recipe for target 'out/host/linux-x86/obj/EXECUTABLES/ckati_intermediates/command.o' failed
make: *** [out/host/linux-x86/obj/EXECUTABLES/ckati_intermediates/command.o] Error 127
Click to expand...
Click to collapse
If it can help, i have these package versions:
- libncurses 5 5.9-52.2.3
- glibc 2.19-16.15.1

Sorry for OT, but anyone pushed hammerhead blobs to github? Would like to give a build a testdrive, but running lollipop on my device still
Thank you very much

Sick1 said:
Sorry for OT, but anyone pushed hammerhead blobs to github? Would like to give a build a testdrive, but running lollipop on my device still
Thank you very much
Click to expand...
Click to collapse
Extracted some days ago and pushed here:
https://github.com/ezio84/
in these trees (mm6.0 branch):
proprietary_vendor_qcom
proprietary_vendor_lge
proprietary_vendor_broadcom

I was able to get it to build on a Debian machine. Something is missing on my main build machine (Gentoo) that I'll have to track down. It took almost 3 hours on my debian machine. 5.1 builds took about 45 minutes on my gentoo machine.
Edit: looks like Gentoo was missing the libtinfo libraries. This is a USE option for the ncurses package. Recompiling with the "tinfo" USE flag got me the necessary libraries and it now compiles fine on my Gentoo machine.

ezio84 said:
If it can help, i have these package versions:
- libncurses 5 5.9-52.2.3
- glibc 2.19-16.15.1
Click to expand...
Click to collapse
Oh, it helped all right. Here's a funny story for you.
Two nights ago I did an upgrade on my Arch install. It crashed my whole system. As in I couldn't even boot a live cd and chroot into my drive. Lost tons of unimportant stuff in the process. So, now I'm more pissed at Arch then I ever have been in the three years I've been using it. What do you do when you're not happy with your current distro? You nuke it. Except, in this case, Arch did that for me.
I looked into openSUSE mainly because of your and @letmedanz success with it. Plus I really like the direction they've taken it over the last few years. So, I begrudgingly used my wifes MAC to make a bootable USB of openSUSU 13.2. During the install I checked EVERY dev package group that it offered. It did it's magic and I was left to explore the openSUSE universe while I was repo syncing AOSP. It's a really nice distro man. I can see why you use it.
So, after sync and with installing ZERO extra packages for building, I hit up the old make otapackage. It started to build. I waited for an error. Than I waited some more. Then I gave up and went and had some coffee. When I got back I was amazed to see it completed. First build on the new distro was a success. That does not happen often. So thanks for the help man.
Oh I did change java to openjdk7 before building but that was the only system change I made.

theesotericone said:
Oh, it helped all right. Here's a funny story for you.
Two nights ago I did an upgrade on my Arch install. It crashed my whole system. As in I couldn't even boot a live cd and chroot into my drive. Lost tons of unimportant stuff in the process. So, now I'm more pissed at Arch then I ever have been in the three years I've been using it. What do you do when you're not happy with your current distro? You nuke it. Except, in this case, Arch did that for me.
I looked into openSUSE mainly because of your and @letmedanz success with it. Plus I really like the direction they've taken it over the last few years. So, I begrudgingly used my wifes MAC to make a bootable USB of openSUSU 13.2. During the install I checked EVERY dev package group that it offered. It did it's magic and I was left to explore the openSUSE universe while I was repo syncing AOSP. It's a really nice distro man. I can see why you use it.
So, after sync and with installing ZERO extra packages for building, I hit up the old make otapackage. It started to build. I waited for an error. Than I waited some more. Then I gave up and went and had some coffee. When I got back I was amazed to see it completed. First build on the new distro was a success. That does not happen often. So thanks for the help man.
Oh I did change java to openjdk7 before building but that was the only system change I made.
Click to expand...
Click to collapse
Indeed, i love it. I'm also curious to see the new incoming "Leap" release, it will be developed by their Enterprise stuff too
PS: run this command too (after "su"):
Code:
ln -s /usr/sbin/schedtool /usr/bin/schedtool
so the build process can access the schedtool bin (it's needed to handle cpu cores) without root privileges.

theesotericone said:
Oh, it helped all right. Here's a funny story for you.
Two nights ago I did an upgrade on my Arch install. It crashed my whole system. As in I couldn't even boot a live cd and chroot into my drive. Lost tons of unimportant stuff in the process. So, now I'm more pissed at Arch then I ever have been in the three years I've been using it. What do you do when you're not happy with your current distro? You nuke it. Except, in this case, Arch did that for me.
I looked into openSUSE mainly because of your and @letmedanz success with it. Plus I really like the direction they've taken it over the last few years. So, I begrudgingly used my wifes MAC to make a bootable USB of openSUSU 13.2. During the install I checked EVERY dev package group that it offered. It did it's magic and I was left to explore the openSUSE universe while I was repo syncing AOSP. It's a really nice distro man. I can see why you use it.
So, after sync and with installing ZERO extra packages for building, I hit up the old make otapackage. It started to build. I waited for an error. Than I waited some more. Then I gave up and went and had some coffee. When I got back I was amazed to see it completed. First build on the new distro was a success. That does not happen often. So thanks for the help man.
Oh I did change java to openjdk7 before building but that was the only system change I made.
Click to expand...
Click to collapse
Wise choice
Better late than ever eh? LOL
Never had any issues with opensuse, except of course some hardware compatibility with certain aspects of the apple hardware, but that's pretty minimal.
Am sure you'll like it as you use it
good luck :good:

I was able to build M for my Nexus 5 last night (took 3 hours). And I found a work around fix for getting rid of the google play services fcs.

Gene Poole said:
Has anyone gotten M to build?
Just did an init(1), sync, install binaries(2), lunch, but then make fails after only a few minutes in.
Here are the last few lines before it fails I can't make any sense of it:
Code:
prebuilts/clang/linux-x86/host/3.6/bin/clang: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
1. repo init -u [url]https://android.googlesource.com/platform/manifest[/url] -b android-6.0.0_r1
2. [url]https://developers.google.com/android/nexus/drivers#hammerheadmra58k[/url][/QUOTE]
For the record (i know I'm a bit late), you were missing libtinfo. That happens mostly on arch Linux, you have to install it from AUR. Other than that you might need other package for ncurse that is compatible with v5. The package is available on AUR as well.
Hope it helps future builders with arch
Click to expand...
Click to collapse

I'm on Arch as well, you need ncurses5-compat-libs from the AUR to fix the build.

possible solution compiling in Archlinux
I saw you had problems compiling it in archlinux, I managed to build the LineageOS in arch and was having the same problem as you. I solved it by installing lib32-libtinfo libtinfo5 and then creating a symlink
Code:
yaourt lib32-libtinfo libtinfo5
ln -sf /usr/lib/libncurses.so.5 /usr/lib/libtinfo.so.5

[SCRIPT] Compile kernel source for the Zenwatch3

DEPRECATED because I don't have the watch anymore. Might still work, might also not. Feel free to just try and iterate on my work.
To port over TWRP, I needed a prebuilt kernel. With a little reading around the web, I managed to compile the kernel source for the Zenwatch3 from the Asus website.
Now, to make things easier for others, I created a script which handles the setup and compilation.
You can clone the script from GitHub: https://github.com/Maxr1998/asus_swift_tools
To continue, follow the instructions from the README.
Huge thanks to @joeykrim and @T10NAZ for their work in their Zenwatch2 thread, from which I got the ASUS_SW_VER fix for the Makefile and general directions.

Maxr1998 said:
To port over TWRP, I needed a prebuilt kernel. With a little reading around the web, I managed to compile the kernel source for the Zenwatch3 from the Asus website.
Now, to make things easier for others, I created a script which handles the setup and compilation.
You can clone the script from GitHub: https://github.com/Maxr1998/asus_swift_tools
To continue, follow the instructions from the README.
Huge thanks to @joeykrim and @T10NAZ for their work in their Zenwatch2 thread, from which I got the ASUS_SW_VER fix for the Makefile and general directions.
Click to expand...
Click to collapse
Thanks for the recovery and instructions.
I faces the following issue when trying to compile. Any tips to avoid this issue. thanks in advance.
drivers/staging/prima/CORE/HDD/src/wlan_hdd_assoc.c: In function 'hdd_RoamIbssIndicationHandler':
drivers/staging/prima/CORE/HDD/src/wlan_hdd_assoc.c:2170:13: warning: passing argument 3 of 'cfg80211_ibss_joined' makes pointer from integer without a cast [enabled by default]
error, forbidden warning: wlan_hdd_assoc.c:2170
/home/toffyjan/android/Test/kernel/scripts/Makefile.build:257: recipe for target 'drivers/staging/prima/CORE/HDD/src/wlan_hdd_assoc.o' failed
make[3]: *** [drivers/staging/prima/CORE/HDD/src/wlan_hdd_assoc.o] Error 1
/home/toffyjan/android/Test/kernel/scripts/Makefile.build:402: recipe for target 'drivers/staging/prima' failed
make[2]: *** [drivers/staging/prima] Error 2
/home/toffyjan/android/Test/kernel/scripts/Makefile.build:402: recipe for target 'drivers/staging' failed
make[1]: *** [drivers/staging] Error 2
Makefile:820: recipe for target 'drivers' failed
make: *** [drivers] Error 2
make: *** Waiting for unfinished jobs....
CC net/key/af_key.o
CC net/ipv6/ip6_input.o
LD net/wireless/built-in.o
LD net/built-in.o
[email protected]:~/android/Test/kernel$

janjan said:
Thanks for the recovery and instructions.
I faces the following issue when trying to compile. Any tips to avoid this issue. thanks in advance.
drivers/staging/prima/CORE/HDD/src/wlan_hdd_assoc.c: In function 'hdd_RoamIbssIndicationHandler':
drivers/staging/prima/CORE/HDD/src/wlan_hdd_assoc.c:2170:13: warning: passing argument 3 of 'cfg80211_ibss_joined' makes pointer from integer without a cast [enabled by default]
error, forbidden warning: wlan_hdd_assoc.c:2170
/home/toffyjan/android/Test/kernel/scripts/Makefile.build:257: recipe for target 'drivers/staging/prima/CORE/HDD/src/wlan_hdd_assoc.o' failed
make[3]: *** [drivers/staging/prima/CORE/HDD/src/wlan_hdd_assoc.o] Error 1
/home/toffyjan/android/Test/kernel/scripts/Makefile.build:402: recipe for target 'drivers/staging/prima' failed
make[2]: *** [drivers/staging/prima] Error 2
/home/toffyjan/android/Test/kernel/scripts/Makefile.build:402: recipe for target 'drivers/staging' failed
make[1]: *** [drivers/staging] Error 2
Makefile:820: recipe for target 'drivers' failed
make: *** [drivers] Error 2
make: *** Waiting for unfinished jobs....
CC net/key/af_key.o
CC net/ipv6/ip6_input.o
LD net/wireless/built-in.o
LD net/built-in.o
[email protected]:~/android/Test/kernel$
Click to expand...
Click to collapse
Weird. Are you using the same toolchain I use?

Maxr1998 said:
Weird. Are you using the same toolchain I use?
Click to expand...
Click to collapse
Yes I did. I using arm-eabi-4.8. I replaced the Makefile with one you linked. Then followed by.
export PATH=~/android/arm-eabi-4.8/bin:$PATH
export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=arm-eabi-
make swift_defconfig
make -j `getconf _NPROCESSORS_ONLN`
Error due to 'drivers/staging/prima/CORE/HDD/src/wlan_hdd_assoc.o' failed anf stopped.

janjan said:
Yes I did. I using arm-eabi-4.8. I replaced the Makefile with one you linked. Then followed by.
export PATH=~/android/arm-eabi-4.8/bin:$PATH
export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=arm-eabi-
make swift_defconfig
make -j `getconf _NPROCESSORS_ONLN`
Error due to 'drivers/staging/prima/CORE/HDD/src/wlan_hdd_assoc.o' failed anf stopped.
Click to expand...
Click to collapse
That explains it. You shouldn't replace the Makefile, but keep the default one, it gets patched with the fix automatically

Maxr1998 said:
That explains it. You shouldn't replace the Makefile, but keep the default one, it gets patched with the fix automatically
Click to expand...
Click to collapse
I can't get the patch to work. It seems it does not patched the makefile. It trying to patch but nothing happen.
~/android/Test/test111$ sudo ./build.sh
[sudo] password for toffyjan:
Welcome!
Extracting files..
Archive: WI503Q_kernel_5_8_0_54.zip
inflating: ASUS_Swift-5.8.0.54-kernel-src.tar
Press any key to continue, Ctrl + C to cancel.
Compiling kernel
Trying to patch Makefile..
--------------------------------------
I edit your script like following.
#!/bin/bash
ARCH=arm CROSS_COMPILE=/home/toffyjan/android/arm-eabi-4.8/bin/arm-eabi-
echo "Welcome!"
##################
# Setup
##################
if [ ! -d kernel ]; then
echo "Extracting files.."
unzip "WI503Q_kernel_*.zip"
tar -xf ASUS_Swift-*-kernel-src.tar
fi
echo "Press any key to continue, Ctrl + C to cancel."
read
##################
# Compile kernel
##################
echo "Compiling kernel"
cd kernel
# Patch Makefile
echo "Trying to patch Makefile.."
patch -N -r /home/toffyjan/android/Test/test111/Patch-Makefile.patch
# Exports
export ARCH=arm
export CROSS_COMPILE=/home/toffyjan/android/arm-eabi-4.8/bin/arm-eabi-
# Make
echo "Starting compilation.."
make clean
make swift_defconfig
make -j3
# Copy kernel
cp "arch/arm/boot/zImage-dtb" ../zImage-dtb
---
I can't get your point here..
OMNI_TREE="/home/max/Development/Android/TWRP" # Enter path of your Omni tree with the toolchain here ? Do I need OMNI_TREE? Is it necessary?

janjan said:
I can't get the patch to work. It seems it does not patched the makefile. It trying to patch but nothing happen.
~/android/Test/test111$ sudo ./build.sh
[sudo] password for toffyjan:
Welcome!
Extracting files..
Archive: WI503Q_kernel_5_8_0_54.zip
inflating: ASUS_Swift-5.8.0.54-kernel-src.tar
Press any key to continue, Ctrl + C to cancel.
Compiling kernel
Trying to patch Makefile..
--------------------------------------
I edit your script like following.
...
I can't get your point here..
OMNI_TREE="/home/max/Development/Android/TWRP" # Enter path of your Omni tree with the toolchain here ? Do I need OMNI_TREE? Is it necessary?
Click to expand...
Click to collapse
Does applying the patch manually from Terminal work?
You don't really need the whole omni tree for compiling the kernel, I only use it for the CROSS_COMPILE/toolchain. Maybe I'll update the script.
Btw, you normally don't need to run this with sudo.

Maxr1998 said:
Does applying the patch manually from Terminal work?
You don't really need the whole omni tree for compiling the kernel, I only use it for the CROSS_COMPILE/toolchain. Maybe I'll update the script.
Btw, you normally don't need to run this with sudo.
Click to expand...
Click to collapse
It seems it is working now at least the patch. Let me see if it finish compiling without error. I will report when it finish. Thanks. I edited like
#!/bin/bash
CROSS_COMPILE=/home/xxxxx/android/arm-eabi-4.8/bin/arm-eabi- # PLACE YOUR CROSS_COMPILE HERE
echo "Welcome!"
##################
# Setup
##################
if [ ! -d kernel ]; then
echo "Extracting files.."
unzip "WI503Q_kernel_*.zip"
tar -xf ASUS_Swift-*-kernel-src.tar
fi
echo "Press any key to continue, Ctrl + C to cancel."
read
##################
# Compile kernel
##################
echo "Compiling kernel"
cd kernel
# Patch Makefile
echo "Trying to patch Makefile.."
patch -N -r /home/xxxxx/android/asus_swift_tools-master/null Makefile ../Patch-Makefile.patch
# Exports
export PATH=~/android/arm-eabi-4.8/bin:$PATH
export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=arm-eabi-
export CROSS_COMPILE=/home/xxxxx/android/arm-eabi-4.8/bin/arm-eabi-
# Make
echo "Starting compilation.."
make clean
make swift_defconfig
make -j `getconf _NPROCESSORS_ONLN`
# Copy kernel
cp "arch/arm/boot/zImage-dtb" ../zImage-dtb
Edit: YES It complete the compiling without any issue. Seems good. Thanks a lot. Now we need to compile a boot.img to try it out. OR maybe use AnyKernel2 Ramdisk Mod Script. The best and the safe way to try by making a boot.img and then try by fastboot boot boot.img It should not hurt the device.

Do you mind to share the stock boot.img? Thanks

janjan said:
Do you mind to share the stock boot.img? Thanks
Click to expand...
Click to collapse
I currently don't have my watch with me, but I will extract it for you tomorrow.
Don't know why my script doesn't work for you :/

Maxr1998 said:
I currently don't have my watch with me, but I will extract it for you tomorrow.
Don't know why my script doesn't work for you :/
Click to expand...
Click to collapse
Sounds good. Thank you very much. It works with a bit edit. Happy new

janjan said:
Sounds good. Thank you very much. It works with a bit edit. Happy new
Click to expand...
Click to collapse
I think that my current paths setup still needs some tweaking
Happy new year!

Maxr1998 said:
I think that my current paths setup still needs some tweaking
Happy new year!
Click to expand...
Click to collapse
We can always add tweaking afterward as long we are able to build. Really appreciate your work for script and custom recovery :good:

janjan said:
Sounds good. Thank you very much. It works with a bit edit. Happy new
Click to expand...
Click to collapse
Here you are. A little later than I wanted, but I hope it's ok

Maxr1998 said:
Here you are. A little later than I wanted, but I hope it's ok
EDIT: mirrored to Dropbox, since attachments are broken right now in XDA.
Click to expand...
Click to collapse
Thank you so much. I will play with the kernel in coming days. :good:

Hello Maxr1998.
Edit.
I tried your custom kernel. It seems everything is working fine. Backup, Restore, flash boot.img and flash zips. Great work there. Really appreciate your work. :good:

Can anyone post a quick list of what commands I would need to enter to get all the required packages/toolchain stuff? I'm fine with plugging commands in to the shell, but I don't really know what I need to get started. Was gonna give this a try to see if it fixes my problem with rebooting when I try to charge.

jobarr said:
Can anyone post a quick list of what commands I would need to enter to get all the required packages/toolchain stuff? I'm fine with plugging commands in to the shell, but I don't really know what I need to get started. Was gonna give this a try to see if it fixes my problem with rebooting when I try to charge.
Click to expand...
Click to collapse
I will upload my kernel soon. Need to upload the source first. You can try my build if you want.

janjan said:
I will upload my kernel soon. Need to upload the source first. You can try my build if you want.
Click to expand...
Click to collapse
Really looking forward to it!
I am quite interested in what the tweaks/changes are

Maxr1998 said:
Really looking forward to it!
I am quite interested in what the tweaks/changes are
Click to expand...
Click to collapse
Nothing so much now. I will add tweaks later. I disabled dm-verity and forced encryption. Possibility to modify system partition and ability to add BusyBox and SuperSu. I will play with other tweaks later. I am a bit busy with exams etc. Did you also build a kernel ?

a530_zap-pro.b00 Missing - Trying to build Lineage OS 15.1

I was following the official guide to building Lineage OS 15.1 for Oneplus 3T but when I executed "extract-files.sh" I got error with some files being missing.Ignoring that, when I ran brunch oneplus3 I got:
Code:
[1060/1060] including ./vendor/qcom/opensource/rcs-service/Android.mk ...
ninja: error: 'vendor/oneplus/oneplus3/proprietary/vendor/firmware/a530_zap-pro.b00', needed by '/home/user/Desktop/lineage/out/target/product/oneplus3/system/vendor/firmware/a530_zap-pro.b00', missing and no known rule to make it
20:25:42 ninja failed with: exit status 1
but I have checked with Root Browser and can say for sure that "a530_zap-pro.b00" file does not exist Anyone who has compiled Lineage OS before can you please tell how did you get it to work as the files don't exist. I'm currently on Oxygen OS Open Beta 24 with Magisk 16.3.

DelicatePanda said:
I was following the official guide to building Lineage OS 15.1 for Oneplus 3T but when I executed "extract-files.sh" I got error with some files being missing.Ignoring that, when I ran brunch oneplus3 I got:
Code:
[1060/1060] including ./vendor/qcom/opensource/rcs-service/Android.mk ...
ninja: error: 'vendor/oneplus/oneplus3/proprietary/vendor/firmware/a530_zap-pro.b00', needed by '/home/user/Desktop/lineage/out/target/product/oneplus3/system/vendor/firmware/a530_zap-pro.b00', missing and no known rule to make it
20:25:42 ninja failed with: exit status 1
but I have checked with Root Browser and can say for sure that "a530_zap-pro.b00" file does not exist Anyone who has compiled Lineage OS before can you please tell how did you get it to work as the files don't exist. I'm currently on Oxygen OS Open Beta 24 with Magisk 16.3.
Click to expand...
Click to collapse
Put this in your local_manifest/roomservice.xml file :
<project path="vendor/oneplus" name="TheMuppet/proprietary_vendor_oneplus" revision="lineage=15.1" />
Click to expand...
Click to collapse
and then do a `repo sync`. This repo wll add all mandatory files (files which are extracted by the `extract-files.sh' tool) to your build tree.

casual_kikoo said:
Put this in your local_manifest/roomservice.xml file :
and then do a `repo sync`. This repo wll add all mandatory files (files which are extracted by the `extract-files.sh' tool) to your build tree.
Click to expand...
Click to collapse
Thank you for that but I was curious about how those files were obtained. And now I'm having another error:
Code:
make[1]: Leaving directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
make: Leaving directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
Building DTBs
make: Entering directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
make[1]: Entering directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
CHK include/config/kernel.release
GEN ./Makefile
CHK include/generated/uapi/linux/version.h
Using /home/user/Desktop/lineage/kernel/oneplus/msm8996 as source for kernel
CHK include/generated/utsrelease.h
CALL /home/user/Desktop/lineage/kernel/oneplus/msm8996/scripts/checksyscalls.sh
make[2]: 'include/generated/vdso-offsets.h' is up to date.
make[1]: Leaving directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
make: Leaving directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
ninja: build stopped: subcommand failed.
20:21:02 ninja failed with: exit status 1

DelicatePanda said:
Thank you for that but I was curious about how those files were obtained. And now I'm having another error:
Code:
make[1]: Leaving directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
make: Leaving directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
Building DTBs
make: Entering directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
make[1]: Entering directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
CHK include/config/kernel.release
GEN ./Makefile
CHK include/generated/uapi/linux/version.h
Using /home/user/Desktop/lineage/kernel/oneplus/msm8996 as source for kernel
CHK include/generated/utsrelease.h
CALL /home/user/Desktop/lineage/kernel/oneplus/msm8996/scripts/checksyscalls.sh
make[2]: 'include/generated/vdso-offsets.h' is up to date.
make[1]: Leaving directory '/home/user/Desktop/lineage/out/target/product/oneplus3/obj/KERNEL_OBJ'
make: Leaving directory '/home/user/Desktop/lineage/kernel/oneplus/msm8996'
ninja: build stopped: subcommand failed.
20:21:02 ninja failed with: exit status 1
Click to expand...
Click to collapse
Your output is missing some information, there is no error in this, except
Code:
ninja: build stopped : subcommand failed

casual_kikoo said:
Your output is missing some information, there is no error in this, except
Code:
ninja: build stopped : subcommand failed
Click to expand...
Click to collapse
Sorry for the delay I am attaching the output of entire "brunch oneplus3" command to this and could you please tell me from where the files in the repo were obtained. Thanks for the help:highfive:

DelicatePanda said:
Sorry for the delay I am attaching the output of entire "brunch oneplus3" command to this and could you please tell me from where the files in the repo were obtained. Thanks for the help:highfive:
Click to expand...
Click to collapse
You have some problem with jack-server :
FAILED: setup-jack-server
/bin/bash -c "(prebuilts/sdk/tools/jack-admin install-server prebuilts/sdk/tools/jack-launcher.jar prebuilts/sdk/tools/jack-server-4.11.ALPHA.jar 2>&1 || (exit 0) ) && (JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx2G" prebuilts/sdk/tools/jack-admin start-server 2>&1 || exit 0 ) && (prebuilts/sdk/tools/jack-admin update server prebuilts/sdk/tools/jack-server-4.11.ALPHA.jar 4.11.ALPHA 2>&1 || exit 0 ) && (prebuilts/sdk/tools/jack-admin update jack prebuilts/sdk/tools/jacks/jack-4.32.CANDIDATE.jar 4.32.CANDIDATE || exit 47 )"
Jack server already installed in "/home/user/.jack-server"
Launching Jack server java -XX:MaxJavaStackTraceDepth=-1 -Djava.io.tmpdir=/tmp -Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx2G -cp /home/user/.jack-server/launcher.jar com.android.jack.launcher.ServerLauncher
Jack server failed to (re)start, try 'jack-diagnose' or see Jack server log
No Jack server running. Try 'jack-admin start-server'
No Jack server running. Try 'jack-admin start-server'
Click to expand...
Click to collapse
In the root of your Android build directory
Code:
prebuilts/sdk/tools/jack-admin start-server
and then, straight after starting jack-server, relaunch your build process.
Also, judging from the log, jack-server is launching with 2G of RAM, which is very low IMO. If you have a low end PC, check this XDA thread, which explains you how to use Google Cloud for free to build ROM.
If you still have issues with jack-server, check this build guide by @nathanchance : there is a part about jack-server memory's problem (Ctrl + F -> "Jack issues").
Also, check a look at this Google Groups thread, this might help you.
Concerning TheMuppets : to be honest with you, I don't know exactly where files come from, BUT looking at commit messages on their Github, you can see, among others, that fourkbomb is pushing to this organization; a quick Google Search, you find his Github profile, he's a member of LineageOS. Also, you'll find a lot of ROMs builders TheMuppet' repo, so nothing to worry about (their repos are on Github, so you can check by yourself ).

[help][building rom][error]

I got this error
Code:
FAILED: /datadrive/xtended/out/soong/.intermediates/external/libjpeg-turbo/libjpeg/android_arm64_armv8-a_kryo_vendor_shared/libjpeg.so.abidiff
(prebuilts/clang-tools/linux-x86/bin/header-abi-diff -allow-unreferenced-changes -allow-unreferenced-elf-symbol-changes -lib libjpeg -arch arm64 -o /datadrive/xtended/out/soong/.intermediates/external/libjpeg-turbo/libjpeg/android_arm64_armv8-a_kryo_vendor_shared/libjpeg.so.abidiff -new /datadrive/xtended/out/soong/.intermediates/external/libjpeg-turbo/libjpeg/android_arm64_armv8-a_kryo_vendor_shared/libjpeg.so.lsdump -old /datadrive/xtended/out/soong/.intermediates/external/libjpeg-turbo/libjpeg/android_arm64_armv8-a_kryo_vendor_shared/libjpeg.so_ref.lsdump)|| (echo ' ---- Please update abi references by running platform/development/vndk/tools/header-checker/utils/create_reference_dumps.py -l libjpeg ----' && exit 1)
******************************************************
error: VNDK library: libjpeg's ABI has INCOMPATIBLE CHANGES Please check compatiblity report at : /datadrive/xtended/out/soong/.intermediates/external/libjpeg-turbo/libjpeg/android_arm64_armv8-a_kryo_vendor_shared/libjpeg.so.abidiff
******************************************************
---- Please update abi references by running platform/development/vndk/tools/header-checker/utils/create_reference_dumps.py -l libjpeg ----
[ 79% 83569/104537] //external/libjpeg-turbo:libjpeg clang jidctint.c [arm]
ninja: build stopped: subcommand failed.
02:38:48 ninja failed with: exit status 1
After i execute command
Code:
development/vndk/tools/header-checker/utils/create_reference_dumps.py -l libjpeg
The output is
Code:
[email protected]:/datadrive/xtended# development/vndk/tools/header-checker/utils/create_reference_dumps.py -l libjpeg
Traceback (most recent call last):
File "development/vndk/tools/header-checker/utils/create_reference_dumps.py", line 224, in <module>
main()
File "development/vndk/tools/header-checker/utils/create_reference_dumps.py", line 210, in main
targets = [Target(True, product), Target(False, product)]
File "development/vndk/tools/header-checker/utils/create_reference_dumps.py", line 29, in __init__
self.arch = build_vars[1]
IndexError: list index out of range

MirRooted said:
I got this error
After i execute command
The output is
Click to expand...
Click to collapse
After I updated RR 7.0 source (august security patch), I get this kind of error too with libsoftkeymasterdevice
Same output for the mentioned python script, although values are defined in https://github.com/pix106/android_d...0ce646cafd1b934bd3ed4d/BoardConfig.mk#L35-L46
There was no change in the device tree which was building with RR-7.0 source a few days ago : https://github.com/pix106/android_device_xiaomi_lavender
I don't quite understand what the error is, did you solve it ?

delete

to avoid these checks, i read on telegram : export SKIP_ABI_CHECKS=true
Test build in progress...
Edit : it worked

pix106 said:
to avoid these checks, i read on telegram : export SKIP_ABI_CHECKS=true
Test build in progress...
Edit : it worked
Click to expand...
Click to collapse
Worked for me too but it's not solution... at least not for me. Sorry that I jumped into thread, found it on google

stane1983 said:
Worked for me too but it's not solution... at least not for me. Sorry that I jumped into thread, found it on google
Click to expand...
Click to collapse
It's been fixed in rom source since then, it was indeed a temporary workaround

Building devices flame and coral for pixeldust

I'm having a problem building the device flame and I keep running into this issue on pixeldust
does anyone know how to solve this error?
Spoiler: flame error
bootable/recovery/Android.mk: error: "librecovery_ui_ext (SHARED_LIBRARIES android-arm64) missing librecovery_ui_pixel (STATIC_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build
and this problem on coral, I have a feeling it's using python3 rather than python2 but idk how I should go about solving that error.
Spoiler: coral error
FAILED: /android/pd/out/target/common/obj/all-event-log-tags.txt
/bin/bash -c "build/make/tools/merge-event-log-tags.py -o /android/pd/out/target/common/obj/all-event-l
og-tags.txt frameworks/av/media/utils/EventLogTags.logtags frameworks/base/core/java/android/app/EventLogTags.logtag
s frameworks/base/core/java/android/app/admin/SecurityLogTags.logtags frameworks/base/core/java/android/content/Even
tLogTags.logtags frameworks/base/core/java/android/net/EventLogTags.logtags frameworks/base/core/java/android/os/Eve
ntLogTags.logtags frameworks/base/core/java/android/speech/tts/EventLogTags.logtags frameworks/base/core/java/androi
d/webkit/EventLogTags.logtags frameworks/base/core/java/com/android/internal/app/EventLogTags.logtags frameworks/bas
e/core/java/com/android/internal/logging/EventLogTags.logtags frameworks/base/core/java/com/android/server/DropboxLo
gTags.logtags frameworks/base/core/java/org/chromium/arc/EventLogTags.logtags frameworks/base/packages/SystemUI/src/
com/android/systemui/EventLogTags.logtags frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
frameworks/base/services/core/java/com/android/server/am/EventLogTags.logtags frameworks/base/services/core/java/co
m/android/server/policy/EventLogTags.logtags frameworks/base/services/core/java/com/android/server/wm/EventLogTags.l
ogtags frameworks/ex/common/java/com/android/common/GoogleLogTags.logtags frameworks/native/services/surfaceflinger/
EventLog/EventLogTags.logtags frameworks/opt/telephony/src/java/com/android/internal/telephony/EventLogTags.logtags
packages/apps/Settings/src/com/android/settings/EventLogTags.logtags packages/apps/TimeZoneUpdater/src/main/com/andr
oid/timezone/updater/EventLogTags.logtags packages/services/Car/car-internal-lib/src/com/android/internal/car/EventL
ogTags.logtags packages/services/Car/tests/CarDeveloperOptions/src/com/android/car/developeroptions/EventLogTags.log
tags system/bt/EventLogTags.logtags system/core/liblog/event.logtags system/core/libsysutils/EventLogTags.logtags sy
stem/core/logcat/event.logtags system/core/logd/event.logtags system/core/storaged/EventLogTags.logtags system/memor
y/lmkd/event.logtags vendor/qcom/opensource/commonsys/system/bt/EventLogTags.logtags"
File "/android/pd/build/make/tools/merge-event-log-tags.py", line 51
except getopt.GetoptError, err:
^
SyntaxError: invalid syntax
13:44:43 ninja failed with: exit status 1
Also, has anyone here tried building shapeshift os yet?