problems building lineageos - OnePlus 7 Pro Questions & Answers

i have an issue building lineage 18.1 for oneplus 7 pro, after running brunch guacemole, the soong build.ninja fails with the following error:
FAILED: out/soong/build.ninja
out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android.bp.list -b out/soong -n out -d out/s
oong/build.ninja.d -globFile out/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja Android.bp
error: android_hardware_oneplus/aidl/vibrator/Android.bp:22:1: "vendor.qti.hardware.vibrator.service.onep
lus" depends on undefined module "android.hardware.vibrator-V1-ndk_platform"
error: hardware/oneplus/aidl/vibrator/Android.bp:4:1: "vendor.qti.hardware.vibrator.impl.oneplus" depends
on undefined module "android.hardware.vibrator-V1-ndk_platform"
05:02:02 soong bootstrap failed with: exit status 1
#### failed to build some targets (24 seconds) ####
does anyone know the solution (I have tried resyncing the repo but that does not help)

Related

error trying to exec 'cc1': execvp: No such file or directory?

If I use the cm-11.0
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
repo sync
then do `make otatools`, it works fine. I can also build recoveryimg without problem.
However, if I use the cm-9.1.0
Code:
repo init -b cm-9.1.0
repo sync
it will switch to android-4.0.4_r2.1.
Now, if I do make otatools It will raise an error:
Code:
prebuilt/linux-x86/ccache/ccache prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/arm-linux-androideabi-gcc -mthumb-interwork -Ibionic/libc/private -DCRT_LEGACY_WORKAROUND -Ibionic/libc/private -o out/target/product/generic/obj/lib/crtend_so.o -c bionic/libc/arch-arm/bionic/crtend_so.S
arm-linux-androideabi-gcc: error trying to exec 'cc1': execvp: No such file or directory
however I do find this cc1:
Code:
./prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/libexec/gcc/arm-linux-androideabi/4.4.3/cc1
and it also executable
Code:
$ stat -c %a ./prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/libexec/gcc/arm-linux-androideabi/4.4.3/cc1
775
How can I fix this problem?

Error while building RedWolf recovery: cp does not take correct arguments

I am currently compiling a Red Wolf custom recovery for Xiaomi Mi A2 lite (daisy). Sources are synced, device tree etc. all set up correctly. Now I am facing a rather banal-looking error during build. cp refuses to copy a directory, because -r is not specified in the build file.
I obviously tried to find the build file (rw_recovery/out/build_omni_daisy.ninja) and add the -r argument, but it seems to be regenerated at the beginning of every build process, as the process still fails and the previously changed line appears unchanged when opening the file after the attempted build.
These are the build steps:
Code:
. build/envsetup.sh
lunch omni_daisy-eng #config for the device
mka bootimage #device uses boot.img as recovery
This command leaves me with the following error:
Code:
[ 99% 6883/6884] Prebuilt (rw_recovery/out/target/product/daisy/kernel)
FAILED: rw_recovery/out/target/product/daisy/kernel
/bin/bash -c "(rm -f /home/luca/rw_recovery/out/target/product/daisy/kernel) && (cp rw_recovery/out/target/product/daisy/obj/KERNEL_OBJ/arch/arm64/boot/ rw_recovery/out/target/product/daisy/kernel )"
cp: -r not specified; omitting directory 'rw_recovery/out/target/product/daisy/obj/KERNEL_OBJ/arch/arm64/boot/'
ninja: build stopped: subcommand failed.
17:13:06 ninja failed with: exit status 1
I would love to hear any suggestions about how to force ninja to execute the command with -r. Alternatively, suggestions about where to find the file from which the above mentioned build file is recreated after executing mka command are much welcomed as well.

Android build error

I'm trying to build android from the Google AOSP source code, but I get this error. Somebody please help
```
[100% 1/1] out/host/linux-x86/bin/soong_build out/soong/build.ninja
FAILED: out/soong/build.ninja
cd "$(dirname "out/host/linux-x86/bin/soong_build")" && BUILDER="$PWD/$(basename "out/host/linux-x86/bin/soong_build")" && cd / && env -i "$BUILDER" --top "$TOP" --soong_out "out/soong" --out "out" -o out/soong/build.ninja --globListDir build --globFile out/soong/globs-build.ninja -t -l out/.module_paths/Android.bp.list --available_env out/soong/soong.environment.available --used_env out/soong/soong.environment.used.build Android.bp
error: test/vts-testcase/vndk/Android.bp:19:1: "vts_vndk_utils" depends on undefined module "vndk_lib_lists"
10:45:14 soong bootstrap failed with: exit status 1
#### failed to build some targets (25 seconds) ####
```

Problem building android

Hello,
I was recently trying to build CorvusOS for my samsung galaxy a7 2017 a7y17lte and when I did brunch a7y17lte everything was going well until I got: config file:
[100% 183/183] /home/user/corvusos/out/soong/.bootstrap/bin/soong_build /home/user/corvusos/out/soong/build.ninja
FAILED: /home/user/corvusos/out/soong/build.ninja
/home/user/corvusos/out/soong/.bootstrap/bin/soong_build -t -l /home/user/corv
usos/out/.module_paths/Android.bp.list -b /home/user/corvusos/out/soong -n /hom
e/user/corvusos/out -d /home/user/corvusos/out/soong/build.ninja.d -globFile /
home/user/corvusos/out/soong/.bootstrap/build-globs.ninja -o /home/user/corvus
os/out/soong/build.ninja Android.bp
config file: /home/user/corvusos/out/soong/soong.variables did not parse correc
tly: invalid character ',' looking for beginning of value
21:36:59 soong bootstrap failed with: exit status 1
Is there any way to fix this?
Thanks in advance!

[GKI] [android13-5.10] [Bazel] build failed Differences between ksymtab and symbol list detected!

I following this instruction:https://source.android.com/docs/setup/build/building-kernels
I initialized repo and synced
Using Bazel to build (with build/build.sh same error)
Using this command:tools/bazel run --lto=none //common:kernel_aarch64_dist -- --dist_dir=out/android13-5.10/dist
And get this error:
ERROR: /home/aaron/Builds/android-kernel/common/BUILD.bazel:26:22: Checking for kmi_symbol_list_
strict_mode //common:kernel_aarch64 failed: (Exit 1): bash failed: error executing command (from
target //common:kernel_aarch64) /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root f
or debugging
ERROR: Differences between ksymtab and symbol list detected!
Symbols missing from ksymtab:
- __cfi_slowpath
Symbols missing from symbol list:
Target //common:kernel_aarch64_dist failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 3572,647s, Critical Path: 3535,69s
INFO: 7 processes: 3 internal, 4 linux-sandbox.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully
Hello, I also encountered this problem, how did you solve it?

Categories

Resources