Building for an unofficial device - Android

Hi! I'm trying to build Lineage 15.1 for Vince (Redmi 5 Plus). There are already funtional builds for this device. I synced the repo and put in [vendor/device/kernel]/xiaomi/vince the files that are needed. The problem is when I do "brunch vince", because I get this error: https://pastebin.com/A6h1uzRa
Does anyone know how to solve it or where is the problem?
EDIT: The problem was solved running the following commands. The problem is caused by using zsh:
setopt shwordsplit
export LC_ALL=C

Now the ROM is compiling, but at some point, I have this error:
system/core/init/Android.mk: error: init (EXECUTABLES android-arm64) missing libinit_msm8953 (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.
build/core/main.mk:732: error: exiting from previous errors.
21:11:57 ckati failed with: exit status 1
Anyone knows how to solve it?

Related

relocation R_X86_64_PC32 against protected symbol error building in Ubuntu 16.04LTS

Hi, I am building klte version of CrdroidAndroid ( a LineageOS based ROM) on a ubuntu 16.04 LTS VM.
I am getting the following error. I am not sure what to do here. I have been cleaning the build folder and ccache and trying to build. I keep ending at this error. Any help to solve this issue is greatly appreciated.
----------------------------------
/usr/bin/x86_64-linux-gnu-ld: /home/sadanand/crdroid/android/system/out/host/linux-x86/obj/SHARED_LIBRARIES/libart_intermediates/base/allocator.o: relocation R_X86_64_PC32 against protected symbol `_ZN3art18g_malloc_allocatorE' can not be used when making a shared object
/usr/bin/x86_64-linux-gnu-ld: final link failed: Bad value
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
------------------------------------------
Thanks

Error building AOSP for Hikey970 Android development board

Hi,
I am trying to build bootloader, kernel and AOSP for the new released Hikey970 development board. However, I found errors during the building process which I have no idea how to solve them, here is the error message:
[ 83% 1615/1934] including system/sepolicy/Android.mk ...
system/sepolicy/Android.mk:79: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version
[100% 1934/1934] writing build rules ...
FAILED:
build/make/core/Makefile:28: error: overriding commands for target `out/target/product/hikey970/system/vendor/lib/libc_secshared.so', previously defined at build/make/core/base_rules.mk:418
ckati failed with: exit status 1
I simply followed tutorials online for Hikey970 to successfully build bootloader and kernel. When I execute:
source ./build/envsetup.sh
lunch hikey970-userdebug
make -j16
Then error popped up. Any help will be appreciated, Thanks in advance.
I've faced the same problem as you.
Did you solve this problem?
Thanks in Advance....

Compile lineageos15.1, execute breakfast command failed

Hi,guys.I am a novice. I referred to some documents and tried to prepare Treble for my KIW-TL00H. I downloaded device, vendor and kernel provided in GitHub, called kiwidevs. When I was ready to compile, Lineage automatically downloaded the device in the official repository, and then told me the error, prompting me that I couldn't identify the vendor file. What should I do now?
Use this guide to unpack latest lineage 15.1 ROM and extract necessary file from it:
https://blog.j15h.nu/building-lineageos-15-1-from-source/
whitemouse2005 said:
Hi,guys.I am a novice. I referred to some documents and tried to prepare Treble for my KIW-TL00H. I downloaded device, vendor and kernel provided in GitHub, called kiwidevs. When I was ready to compile, Lineage automatically downloaded the device in the official repository, and then told me the error, prompting me that I couldn't identify the vendor file. What should I do now?
Click to expand...
Click to collapse
You need to create manifest file for your sources and pull all repos (device, kernel, proprietary) from Github, if you don't want to use official Lineage repos.
If you want to use official Lineage repos, add TheMuppets/proprietary_vendor_huawei to your local manifest.
ShadySquirrel said:
You need to create manifest file for your sources and pull all repos (device, kernel, proprietary) from Github, if you don't want to use official Lineage repos.
If you want to use official Lineage repos, add TheMuppets/proprietary_vendor_huawei to your local manifest.
Click to expand...
Click to collapse
I did it. Now I am finish.But I get a new problem.It means:
[1078/1078] including ./vendor/qcom/opensource/rcs-service/Android.mk ...
device/huawei/kiwi/libwcnss_qmi/Android.mk: error: libwcnss_qmi (SHARED_LIBRARIES android-arm64) missing libhuawei_secure (SHARED_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.
device/huawei/kiwi/libwcnss_qmi/Android.mk: error: libwcnss_qmi (SHARED_LIBRARIES android-arm64) missing liboeminfo (SHARED_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.
device/huawei/kiwi/libwcnss_qmi/Android.mk: error: libwcnss_qmi (SHARED_LIBRARIES android-arm) missing libhuawei_secure (SHARED_LIBRARIES android-arm)
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.
device/huawei/kiwi/libwcnss_qmi/Android.mk: error: libwcnss_qmi (SHARED_LIBRARIES android-arm) missing liboeminfo (SHARED_LIBRARIES android-arm)
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.
build/core/main.mk:732: error: exiting from previous errors.
13:02:26 ckati failed with: exit status 1
What should I do?
whitemouse2005 said:
I did it. Now I am finish.But I get a new problem.It means:
[1078/1078] including ./vendor/qcom/opensource/rcs-service/Android.mk ...
device/huawei/kiwi/libwcnss_qmi/Android.mk: error: libwcnss_qmi (SHARED_LIBRARIES android-arm64) missing libhuawei_secure (SHARED_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.
device/huawei/kiwi/libwcnss_qmi/Android.mk: error: libwcnss_qmi (SHARED_LIBRARIES android-arm64) missing liboeminfo (SHARED_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.
device/huawei/kiwi/libwcnss_qmi/Android.mk: error: libwcnss_qmi (SHARED_LIBRARIES android-arm) missing libhuawei_secure (SHARED_LIBRARIES android-arm)
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.
device/huawei/kiwi/libwcnss_qmi/Android.mk: error: libwcnss_qmi (SHARED_LIBRARIES android-arm) missing liboeminfo (SHARED_LIBRARIES android-arm)
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.
build/core/main.mk:732: error: exiting from previous errors.
13:02:26 ckati failed with: exit status 1
What should I do?
Click to expand...
Click to collapse
Have you resynced after you've added your repos to the manifest? It looks like it didn't pull anything from proprietary repo (that file is part of it).

Building kernel for Google Pixel 3 - Syntax error: "(" unexpected

Following theese instructions on the AOSP site "Building Kernels"
repo init -u android.googlesource.com/kernel/manifest -b android-msm-bluecross-4.9-pie-qpr1
repo sync
sh build/build.sh //This command throws an error.
sh build/build.sh
build/build.sh: 97: build/build.sh: Syntax error: "(" unexpected
This is line 97:
function rel_path() {
So it triggers on the parenthesis. Ive googled a little back and forth. And as far as I can tell - this error triggers because of missing shebang line. The document starts with a shebang line:
#!/bin/bash
Not sure whats wrong - Should I roll back to 18.04 or 14.04?
Distributor ID: Ubuntu
Description: Ubuntu 18.10
Release: 18.10
Codename: cosmic
michaelburrow189 said:
Following theese instructions on the AOSP site "Building Kernels"
repo init -u android.googlesource.com/kernel/manifest -b android-msm-bluecross-4.9-pie-qpr1
repo sync
sh build/build.sh //This command throws an error.
sh build/build.sh
build/build.sh: 97: build/build.sh: Syntax error: "(" unexpected
This is line 97:
function rel_path() {
So it triggers on the parenthesis. Ive googled a little back and forth. And as far as I can tell - this error triggers because of missing shebang line. The document starts with a shebang line:
#!/bin/bash
Not sure whats wrong - Should I roll back to 18.04 or 14.04?
Distributor ID: Ubuntu
Description: Ubuntu 18.10
Release: 18.10
Codename: cosmic
Click to expand...
Click to collapse
Welcome to the wonderful world of missing android documentation! rel_path appears to be a deprecated function of realpath. This is all stackexchange knows about it, and the android developer website gives me nothing useful. The only suggested fix I found is to try installing realpath and coreutils again.
Run,
sudo apt-get install coreutils
sudo apt-get install realpath
Then try building again. If you still get an error at the parentheses, then try putting a space between rel_path() so it's rel_path (). If you still get an error after that, then I'm out of ideas. I sincerely wish you luck navigating the horrible mess that is android source code.
Spaceminer said:
Welcome to the wonderful world of missing android documentation! rel_path appears to be a deprecated function of realpath. This is all stackexchange knows about it, and the android developer website gives me nothing useful. The only suggested fix I found is to try installing realpath and coreutils again.
Run,
sudo apt-get install coreutils
sudo apt-get install realpath
Then try building again. If you still get an error at the parentheses, then try putting a space between rel_path() so it's rel_path (). If you still get an error after that, then I'm out of ideas. I sincerely wish you luck navigating the horrible mess that is android source code.
Click to expand...
Click to collapse
Code:
sudo apt-get install realpath
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package realpath is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
manpages-pl manpages-fr-extra
E: Package 'realpath' has no installation candidate
Code:
type -a realpath
realpath is /usr/bin/realpath
Installing manpages-pl and manpages-fr-ekstra did work though.
But it is throwing me the same parenthesis error as before. Thanks though! I thought building the clean kernel would work kind'a smooth.

some problem with cooking lineage rom

i try to build a LOS 17 unofficially for tissot (xiaomi mi a1) phone
after days that i finding missing vendor files finally i try to brunch the ROM
and after 99% i got this error:
[ 99% 478/479] finishing build rules ...
FAILED:
hardware/interfaces/boot/1.0/default/Android.mk: error: "[email protected] (SHARED_LIBRARIES android-arm64) missing bootctrl.msm8953 (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.
build/make/core/main.mk:961: error: exiting from previous errors.
15:16:22 ckati failed with: exit status 1
and i dont know what should i do
try searching about missing bootctrl.msm8953 but nothing
any help or advice that make it easy to me
thanks a lot for attention or help
babakhad said:
i try to build a LOS 17 unofficially for tissot (xiaomi mi a1) phone
after days that i finding missing vendor files finally i try to brunch the ROM
and after 99% i got this error:
[ 99% 478/479] finishing build rules ...
FAILED:
hardware/interfaces/boot/1.0/default/Android.mk: error: "[email protected] (SHARED_LIBRARIES android-arm64) missing bootctrl.msm8953 (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.
build/make/core/main.mk:961: error: exiting from previous errors.
15:16:22 ckati failed with: exit status 1
and i dont know what should i do
try searching about missing bootctrl.msm8953 but nothing
any help or advice that make it easy to me
thanks a lot for attention or help
Click to expand...
Click to collapse
i pass the problem
and now another one apear :
FAILED: ninja: 'out/target/product/tissot/obj/STATIC_LIBRARIES/bootctrl.msm8953_intermediates/export_includes', needed by 'out/target/product/tissot/obj/SHARED_LIBRARIES/[email protected]_intermediates/import_includes', missing and no known rule to make it
12:43:28 ninja failed with: exit status 1
thanks
and any help will be appreciated
0

Categories

Resources