Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem compile aosp car with raspberry pi 5 #128

Open
nairdaweb opened this issue Sep 20, 2024 · 1 comment
Open

Problem compile aosp car with raspberry pi 5 #128

nairdaweb opened this issue Sep 20, 2024 · 1 comment

Comments

@nairdaweb
Copy link

nairdaweb commented Sep 20, 2024

Hello, I am getting the following error during compilation. I have already tried it on Fedora and Debian, but it's always the same. I searched for these libraries and found nothing. I even installed all the SDKs, including Android Studio.

[100% 1156/1156] analyzing Android.bp files and generating ninja file at out/soong/build.aosp_rpi5_car.ninja
FAILED: out/soong/build.aosp_rpi5_car.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"     --soong_variables out/soong/soong.aosp_rpi5_car.variables -o out/soong/build.aosp_rpi5_car.
ninja --globListDir aosp_rpi5_car --globFile out/soong/globs-aosp_rpi5_car.ninja -l out/.module_paths/Android.bp.list --available_env out/soong/soong.env
ironment.available --used_env out/soong/soong.environment.used.aosp_rpi5_car.build Android.bp
Warning: Module 'androidx.wear_wear' depends on non-existing optional_uses_libs 'wear-sdk'
Warning: Module 'androidx.wear.compose_compose-foundation' depends on non-existing optional_uses_libs 'wear-sdk'
09:40:38 soong bootstrap failed with: exit status 1
ninja: build stopped: subcommand failed.

#### failed to build some targets (05:42 (mm:ss)) ####
@KonstaT
Copy link
Member

KonstaT commented Sep 20, 2024

That doesn't actually give much insight why this failed. You'd probably need to dig into soong logs.

One possible reason is you just ran out of memory. Does your build machine meet the hardware requirements (https://source.android.com/docs/setup/start/requirements#hardware-requirements)? You could try adding a swap file or try bulding with a smaller number of parallel jobs (make ... -jX).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants