Hey guys!
So I'm currently experimenting with porting Lineage 15 (don't get your hopes up; I'm just looking for patterns in other device trees and carrying them over to this one) and I'm always getting stuck at this error:
Code:
ninja: error: '/home/alexander/oreo/out/target/product/ether/obj/STATIC_LIBRARIES/libbootloader_message_intermediates/export_includes', needed by '/home/alexander/oreo/out/target/product/ether/obj/EXECUTABLES/init_intermediates/import_includes', missing and no known rule to make it
02:16:32 ninja failed with: exit status 1
It seems that I might be lacking some library that some component is requesting, however I have no idea how to trace these things. Any ideas?
Related
First of all, I would like to tell that this is my first time compiling a rom from source, and so I am very sorry for any silly mistakes I made.
I have been having this issue lately with compiling the latest version of Android (Nougat 7.0) as of now to the Galaxy Nexus. I was able to get everything except the ending part to compile the flashable zip. Here is the error I get on the terminal whenever I try:
______________________________________________________________________________________________________________________________
No private recovery resources for TARGET_DEVICE toro
build/core/binary.mk:664: warning: overriding commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.cc'
build/core/binary.mk:664: warning: ignoring old commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.cc'
build/core/binary.mk:668: warning: overriding commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.h'
build/core/binary.mk:668: warning: ignoring old commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.h'
Starting build with ninja
ninja: Entering directory `.'
ninja: error: 'out/target/product/toro/obj/SHARED_LIBRARIES/libinvensense_hal_intermediates/export_includes', needed by 'out/target/product/toro/obj/SHARED_LIBRARIES/sensors.tuna_intermediates/import_includes', missing and no known rule to make it
build/core/ninja.mk:148: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
#### make failed to build some targets (07:05 (mm:ss)) ####
______________________________________________________________________________________________________________________________
Here are some theories I have about this problem:
- It may have to do something about the "Compiling with jack" on the android website tutorial i don't know about
- I also am thinking that it has to do something with the drivers (Vendor), since I am using the ones from stock Android 4.2.2 for the Galaxy Nexus Toro. I read from another thread saying that you have to "Modify the device tree" for a later version of Android, which I don't know about (Please give me a link or tell how to do that).
I am running Ubuntu 16.04 LTS
Developers, can you please respond as soon as possible. I would greatly appreciate it if you could.
Thanks,
Nrichard7029
Please? Anyone?
nrichard7029 said:
Please? Anyone?
Click to expand...
Click to collapse
They're all busy trying to get it to compile themselves. Lots of stuff has changed with the build system in Nougat, it's going to take a bit to get everything sorted out. Keep an eye on https://github.com/OMAP4-AOSP for the most recent changes relevant for our devices.
nrichard7029 said:
First of all, I would like to tell that this is my first time compiling a rom from source, and so I am very sorry for any silly mistakes I made.
I have been having this issue lately with compiling the latest version of Android (Nougat 7.0) as of now to the Galaxy Nexus. I was able to get everything except the ending part to compile the flashable zip. Here is the error I get on the terminal whenever I try:
______________________________________________________________________________________________________________________________
No private recovery resources for TARGET_DEVICE toro
build/core/binary.mk:664: warning: overriding commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.cc'
build/core/binary.mk:664: warning: ignoring old commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.cc'
build/core/binary.mk:668: warning: overriding commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.h'
build/core/binary.mk:668: warning: ignoring old commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.h'
Starting build with ninja
ninja: Entering directory `.'
ninja: error: 'out/target/product/toro/obj/SHARED_LIBRARIES/libinvensense_hal_intermediates/export_includes', needed by 'out/target/product/toro/obj/SHARED_LIBRARIES/sensors.tuna_intermediates/import_includes', missing and no known rule to make it
build/core/ninja.mk:148: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
#### make failed to build some targets (07:05 (mm:ss)) ####
Click to expand...
Click to collapse
did you solve this ? i am getting similar error instead of ''libinvensense_hal_intermediates'' i have ''libbootloader_message_writer_intermediates''
nrichard7029 said:
First of all, I would like to tell that this is my first time compiling a rom from source, and so I am very sorry for any silly mistakes I made.
I have been having this issue lately with compiling the latest version of Android (Nougat 7.0) as of now to the Galaxy Nexus. I was able to get everything except the ending part to compile the flashable zip. Here is the error I get on the terminal whenever I try:
______________________________________________________________________________________________________________________________
No private recovery resources for TARGET_DEVICE toro
build/core/binary.mk:664: warning: overriding commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.cc'
build/core/binary.mk:664: warning: ignoring old commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.cc'
build/core/binary.mk:668: warning: overriding commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.h'
build/core/binary.mk:668: warning: ignoring old commands for target `out/host/linux-x86/gen/STATIC_LIBRARIES/libaapt2_intermediates/proto/frameworks/base/tools/aapt2/Format.pb.h'
Starting build with ninja
ninja: Entering directory `.'
ninja: error: 'out/target/product/toro/obj/SHARED_LIBRARIES/libinvensense_hal_intermediates/export_includes', needed by 'out/target/product/toro/obj/SHARED_LIBRARIES/sensors.tuna_intermediates/import_includes', missing and no known rule to make it
build/core/ninja.mk:148: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
#### make failed to build some targets (07:05 (mm:ss)) ####
______________________________________________________________________________________________________________________________
Here are some theories I have about this problem:
- It may have to do something about the "Compiling with jack" on the android website tutorial i don't know about
- I also am thinking that it has to do something with the drivers (Vendor), since I am using the ones from stock Android 4.2.2 for the Galaxy Nexus Toro. I read from another thread saying that you have to "Modify the device tree" for a later version of Android, which I don't know about (Please give me a link or tell how to do that).
I am running Ubuntu 16.04 LTS
Developers, can you please respond as soon as possible. I would greatly appreciate it if you could.
Thanks,
Nrichard7029
Click to expand...
Click to collapse
, I know this is quite late, but searching for the same error on google and found your thread:
Just go to file manager, click view, go on "Show Hidden Files", tick it, and open your .bashrc file. At the bottom of it, add "export USE_NINJA=false" . This should fix your error.
Think "tuna" - not "toro"
bablu048 said:
did you solve this ? i am getting similar error instead of ''libinvensense_hal_intermediates'' i have ''libbootloader_message_writer_intermediates''
Click to expand...
Click to collapse
You may want to change your thinking to "tuna" (a unified build) - as opposed to "toro" (device-specific); this is especially true for 6.0 and later. In fact, I've seen fewer and fewer specific builds for tuna-family members (even the GSM-specific maguro, the most commonplace outside the US) - my usual N builds are from a maguro owner that is from (doun't laugh) Japan - we don't even have a language in common. (They don't speak CDMA in Japan - and the builder himself tests on maguro hardware. Me? I run on toro hardware and VZW MVNO Tracfone - no such thing as corndog sushi!
Found the issue - it's in ninja (called by brunch). Any idea if it's even fixable?
Well, new user but old lurker here, no points to post in dev threads and I'm not going to wait 3 months to get them so jumping right into things...
This is a record of my attempts to build AOSP 8.0 Orea for the nex Xperia XZ2 Compact. I'm running into problems and figured I'd document them here, for the betterment of others and to get help if needed.
Main guide: https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/build-aosp-oreo-8-0-kernel-4-4/#tutorial-step-3
Some modification required, as the phone and code are both pretty new, as mentioned by BeNeDeLuX on May 22 the repo was only just uploaded. More to follow.
github links not permitted?!??!?
well according to XDA, outside links are not allowed to be posted until you've replied 10 times... Even if the posts are OBVIOUSLY code-related (e.g. GitHub *cough*cough*)...
Please excuse me while I go spam another thread, or create an intro or something... brb
Step 2
OK, jumping right back into it:
Now we need to add the git repos for tama (platform) and apollo (xz2).
First follow the steps in the main guide up to step 4.3: https://developer.sony.com/develop/.../build-aosp-oreo-8-0-kernel-4-4/
Then clone the following two repositories into the ~/android/devices/sony directory:
Code:
git clone https://github.com/sonyxperiadev/device-sony-tama.git tama
Code:
git clone https://github.com/sonyxperiadev/device-sony-apollo.git apollo
now continue on with the steps in the main guide
There may be errors yet to come...
First error
First error:
Code:
build/core/base_rules.mk:374: warning: ignoring old commands for target
`out/target/product/apollo/vendor/etc/gps.conf'
ninja: error: 'kernel/sony/msm/arch/arm64/configs/aosp_tama_apollo_defconfig',
needed by '/home/anna/android_8-0-0/out/target/product/apollo/obj/KERNEL_OBJ/.config',
missing and no known rule to make it
16:32:12 ninja failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
#### make failed to build some targets (01:40 (mm:ss)) ####
System Info:
Code:
Linux hostname 4.8.0-53-generic #56~16.04.1-Ubuntu SMP Tue May 16 01:18:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Will post any progress as I make it, suggestions are welcome. You can find the full log here
any progress??
I'm back!
[email protected] said:
any progress??
Click to expand...
Click to collapse
Hey yes sorry my real-life job doesn't always allow for much personal time...
So right now the Sony dev repos don't have a pre-built kernel or kernel configuration for the XZ2 Compact.
I've grabbed the current config from /proc/config.gz on my XZ2 Compact running Android 8.0.0, Linux kernel 4.9.65-perf+, posted to gist here: https://gist.github.com/Ifiht/9d0eff34d1f47ecd955b49acd34a14fb
The closest config (based on software/hardware from https://en.wikipedia.org/wiki/Sony_Xperia) in sony repos is the aosp_yoshino_lilac default config, I've started compiling all these resources in a single git repo at https://github.com/Ifiht/sony-xperia-xz2.build.
Will update here with progress once I've got some with the kernel build.
2nd Error
Code:
ninja: error: 'out/target/product/apollo/obj_arm/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by 'out/target/product/apollo/obj_arm/SHARED_LIBRARIES/libOmxVdec_intermediates/import_includes', missing and no known rule to make it
12:58:20 ninja failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
#### make failed to build some targets (03:37 (mm:ss)) ####
So the build failed again using the defconfig listed in my git repo for this project. This time it doesn't even look like a kernel issue, more like a repo conflict given that all the errors are in "out" directory.
Appreciate any guidance from those that have seen this before. Full error copied here: https://gist.github.com/Ifiht/bb4e1dd43b6598ffcf02b83d960cd959
3rd error
Code:
[ 90% 10/11] glob system/core/*/Android.bp
ninja: error: 'device/sony/common-kernel/kernel-dtb-apollo', needed by 'out/target/product/apollo/kernel', missing and no known rule to make it
14:07:36 ninja failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
After upgrading my kernel and local repos to 4.9.6 and re-syncing everything for good measure I'm now getting the above. At least this one seems straightforward, even if it may mean I have to frankenstein together a custom kernel from the flagship source repos currently available from Sony...
Oh well onward and upward!
Build attempt on Mac OSX
Hey,
thank you for documenting your progress, I am playing along trying to get the build to work on my Mac OS 10.13 machine,
nice to see I am not the only one trying
Stuck with the exact same error now btw
Code:
[ 99% 141/142] glob prebuilts/abi-dumps/vndk/current/arm64/source-based/[email protected]
ninja: error: 'device/sony/common-kernel/kernel-dtb-apollo', needed by 'out/target/product/apollo/kernel', missing and no known rule to make it
20:16:48 ninja failed with: exit status 1
best wishes
https://github.com/sonyxperiadev/bug_tracker/issues/169#issuecomment-424278920
PLEASE DON'T FLASH TAMA WITH THE CURRENT KERNEL
My Akari's display got permanently damaged.
I repeat, DO NOT FLASH.
Click to expand...
Click to collapse
The wrong part is like this：
Code:
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/jjut/los/out/target/product/albus/system/vendor/lib/libsensorndkbridge.so'
[ 99% 5741/5742] glob vendor/qcom/opensource/interfaces/wifi/supplicant/2.0/src
ninja: error: '/home/jjut/los/out/target/product/albus/obj_arm/SHARED_LIBRARIES/libqsap_sdk_intermediates/export_includes', needed by '/home/jjut/los/out/target/product/albus/obj_arm/SHARED_LIBRARIES/libqsap_shim_intermediates/import_includes', missing and no known rule to make it
17:09:12 ninja failed with: exit status 1
#### failed to build some targets (02:09 (mm:ss)) ####
I tried to find a good solution on Google or Github. Please help me on the xda developer. Thank you, I wish you a happy life.
help！
You need to declare a prebuilt shared library, atleast i fixed my error (with libminui) during building twrp, but the recovery didn't boot eventually. You need the compiled .so file and follow instructions here https://developer.android.com/ndk/guides/prebuilts
Hi guys!
So I was following this https://wiki.lineageos.org/devices/bacon/build wiki to build a lineageos 18.1 ROM for my one plus one.
Unfortunately, when I get to the step for "breakfast bacon", I get the following errors.
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
build/make/target/product/product_launched_with_k.mk:2: error: _nic.PRODUCTS.[[device/oneplus/bacon/lineage_bacon.mk]]: "device/oppo/msm8974-common/msm8974.mk" does not exist.
22:35:04 dumpvars failed with: exit status 1
Device bacon not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_oneplus_bacon
Default revision: lineage-18.1
Checking branch info
Checking if device/oneplus/bacon is fetched from android_device_oneplus_bacon
LineageOS/android_device_oneplus_bacon already fetched to device/oneplus/bacon
Syncing repository to retrieve project.
sh: 1: repo: not found
Repository synced!
Looking for dependencies in device/oneplus/bacon
Looking for dependencies in device/oppo/msm8974-common
device/oppo/msm8974-common has no additional dependencies.
Looking for dependencies in kernel/oppo/msm8974
kernel/oppo/msm8974 has no additional dependencies.
Done
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
build/make/target/product/product_launched_with_k.mk:2: error: _nic.PRODUCTS.[[device/oneplus/bacon/lineage_bacon.mk]]: "device/oppo/msm8974-common/msm8974.mk" does not exist.
22:35:05 dumpvars failed with: exit status 1
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
build/make/target/product/product_launched_with_k.mk:2: error: _nic.PRODUCTS.[[device/oneplus/bacon/lineage_bacon.mk]]: "device/oppo/msm8974-common/msm8974.mk" does not exist.
22:35:06 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_bacon'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
What am I doing wrong?
p.s. if I do a "breakfast d855", then I get no error.
My utter apologies for being so blind.
It is of course clearly written on that wiki that some devices would fail upon "breakfast" command being called due to the missing vendor files.
Hence one should first run "extract-files.sh" in the device specific folder. And indeed afterwards the breakfast command succeeds for "bacon".
I could be given a little margin for being a noob and also that my other device "d855" does not need extract-files.sh before breakfast.
Also what confused me yesterday was, that the paths contained oppo when infact I was building for bacon. I was sure something is wrong upstream.
My sincere apologies again for starting on xda with such a useless post.
I know development stopped for this phone but I was looking to see how difficult it would be to build my own ROM with PE 12 following this guide and it appears I need some binaries but I have no idea how to get that so I am failing here:
Code:
[email protected]:~/android/pe# source build/envsetup.sh
including vendor/aosp/vendorsetup.sh
[email protected]:~/android/pe# lunch aosp_albus-userdebug
02:35:02 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:02 dumpvars failed with: exit status 1
Device albus not found. Attempting to retrieve device repository from PixelExperience-Devices Github (http://github.com/PixelExperience-Devices).
Found repository: device_motorola_albus
Checking branch info
Calculated revision: twelve
Branch twelve not found
02:35:05 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:05 dumpvars failed with: exit status 1
02:35:07 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:08 dumpvars failed with: exit status 1
** Don't have a product spec for: 'aosp_albus'
** Do you have the right repo manifest?
Any idea how difficult it is to get past this and to get a PE 12 ROM built for this device? I assume once I get the binaries I would also need to modify some code and a bunch of files...
nmajin said:
I know development stopped for this phone but I was looking to see how difficult it would be to build my own ROM with PE 12 following this guide and it appears I need some binaries but I have no idea how to get that so I am failing here:
Code:
[email protected]:~/android/pe# source build/envsetup.sh
including vendor/aosp/vendorsetup.sh
[email protected]:~/android/pe# lunch aosp_albus-userdebug
02:35:02 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:02 dumpvars failed with: exit status 1
Device albus not found. Attempting to retrieve device repository from PixelExperience-Devices Github (http://github.com/PixelExperience-Devices).
Found repository: device_motorola_albus
Checking branch info
Calculated revision: twelve
Branch twelve not found
02:35:05 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:05 dumpvars failed with: exit status 1
02:35:07 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
build/make/core/product_config.mk:160: error: Can not locate config makefile for product "aosp_albus".
02:35:08 dumpvars failed with: exit status 1
** Don't have a product spec for: 'aosp_albus'
** Do you have the right repo manifest?
Any idea how difficult it is to get past this and to get a PE 12 ROM built for this device? I assume once I get the binaries I would also need to modify some code and a bunch of files...
Click to expand...
Click to collapse
You are missing all the trees for the device; as you seem to have no clue i'd recommend you at least start by building A11. A12 won't boot on albus without significant modifications to the rom, which PE has not included in it's upstream.
For building a rom you need:
The rom structure (Duh)
The device tree (usually called device_brand_codename, in this case device_motorola_albus and store in device/motorola/albus to be properly detected)
The kernel tree (which usually inherits the name of the SOC, in this case msm8953 and goes into kernel/msm8953)
Vendor tree (which follows the same naming convention as device tree and goes in vendor/motorola/albus)
marcost22 said:
You are missing all the trees for the device; as you seem to have no clue i'd recommend you at least start by building A11. A12 won't boot on albus without significant modifications to the rom, which PE has not included in it's upstream.
For building a rom you need:
The rom structure (Duh)
The device tree (usually called device_brand_codename, in this case device_motorola_albus and store in device/motorola/albus to be properly detected)
The kernel tree (which usually inherits the name of the SOC, in this case msm8953 and goes into kernel/msm8953)
Vendor tree (which follows the same naming convention as device tree and goes in vendor/motorola/albus)
Click to expand...
Click to collapse
Thanks for the reply, and yea maybe I’ll start with PE 11 then. Would building that provide the trees for the device or how do you go about getting those? I did read about the modifications needed for PE 12 to get around the iptables drop but willing to mess with it and only plan to use this phone for the projector mod.
nmajin said:
Thanks for the reply, and yea maybe I’ll start with PE 11 then. Would building that provide the trees for the device or how do you go about getting those? I did read about the modifications needed for PE 12 to get around the iptables drop but willing to mess with it and only plan to use this phone for the projector mod.
Click to expand...
Click to collapse
Given the fact that this device had official PE 11 support, those trees (for A11) would be hosted on the PE-Device github. The vendor tree however would be hosted in their gitlab (or you can generate it with the device tree, by having the device plugged in and running extract-files