Error compiling rom - Android Q&A, Help & Troubleshooting

Friends, I'm following all the current tutorial, but at the moment of giving the command "LUNCH", this error is appearing to me. I do not know what else to do...
I'm trying to compile the RR for the MOTOZPLAY (addison)
Thank you very much
:crying:
Code:
build/core/product_config.mk:252: *** Product "lineage_addison" ambiguous: matches device/motorola/addison/lineage.mk device/addison/lineage.mk. Pare.
Device addison not found. Attempting to retrieve device repository from lineageos Github (http://github.com/LineageOS).
Found repository: android_device_motorola_addison
Default revision: cm-14.1
Checking branch info
Checking if device/motorola/addison is fetched from android_device_motorola_addison
LineageOS/android_device_motorola_addison already fetched to device/motorola/addison
Syncing repository to retrieve project.
sh: 1: repo: not found
Repository synced!
Looking for dependencies in device/motorola/addison
Looking for dependencies in device/qcom/common
Dependencies file not found, bailing out.
Done
build/core/product_config.mk:252: *** Product "lineage_addison" ambiguous: matches device/motorola/addison/lineage.mk device/addison/lineage.mk. Pare.
build/core/product_config.mk:252: *** Product "lineage_addison" ambiguous: matches device/motorola/addison/lineage.mk device/addison/lineage.mk. Pare.
** Don't have a product spec for: 'lineage_addison'
** Do you have the right repo manifest?

Did you clone your own device tree or let lineage clone it for you?

Yuvch122 said:
Did you clone your own device tree or let lineage clone it for you?
Click to expand...
Click to collapse
I iam compile RR using kernel LineageOS... Using tutorial

Ahh that method
---------- Post added at 07:34 AM ---------- Previous post was at 07:33 AM ----------
What device model do you use? An officially supported one or not bg lineage

Related

Unable to build CM 10.1 with Android 4.2.2

Hi to all.
I'm trying to build the latest version of CyanogenMod, with android 4.2.2. I sync the repo with
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
and now I'm in the breakfast phase. The result is:
Code:
[email protected]:~/cyanogen_p4/system$ breakfast p4
including vendor/cm/vendorsetup.sh
ls: impossibile accedere a device/*/p4/cm.mk: File o directory non esistente
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_p4". Arresto.
Device p4 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_p4
Default revision: cm-10.1
Checking branch info
CyanogenMod/android_device_samsung_p4 already exists
Syncing repository to retrieve project.
error: project device/samsung/p4 not found
Repository synced!
Looking for dependencies
Dependencies file not found, bailing out.
Done
ls: impossibile accedere a device/*/p4/cm.mk: File o directory non esistente
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_p4". Arresto.
** Don't have a product spec for: 'cm_p4'
** Do you have the right repo manifest?
I have a nightly build installed with Android 4.2.2, so I think that build the newest android version for samsung p4 is possible.
What is wrong?
I think that there is something broken in the build system for P4 device. I tried also to git-clone manually the android_device_samsung_p4 project and android_device_samsung_p4-common project in the right path (/device/samsung/) but the breakfast give me another error.
Sorry but my poor knowledge of CM build system does not help me
Has anybody build from scratch a cyanogenmod with android 4.2.2?
(BTW ...I don't understand why my topic was moved here...)
Update
Hey sarbyn,
I stumbled upon the same error today. Did you find any fixes or further information about that?
Best regards
el manu
elmanuel said:
Hey sarbyn,
I stumbled upon the same error today. Did you find any fixes or further information about that?
Best regards
el manu
Click to expand...
Click to collapse
Sorry but I don't remember how I fixed it. The last time I did a build for P4 was in february...if I remember correctly it was only a temporary issue, after some days a simple "repo sync" fixed it

CM10.1 build error

I am having trouble building a new checkout of the CM10.1 sources. I built CM10 successfully some months ago, but somehow, things have changed... I've checked out a completely fresh copy from git, into a fresh VM, just to eliminate chances I could've borked things on the previous CM build VM.
Code:
ls: cannot access device/*/i9100/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_i9100". Stop.
Device i9100 not found. Attempting to retrieve device repository from CyanogenMod Github (...).
Found repository: android_device_samsung_i9100
Default revision: cm-10.1
Checking branch info
CyanogenMod/android_device_samsung_i9100 already exists
Syncing repository to retrieve project.
error: project device/samsung/i9100 not found
Repository synced!
Looking for dependencies
Dependencies file not found, bailing out.
Done
ls: cannot access device/*/i9100/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_i9100". Stop.
** Don't have a product spec for: 'cm_i9100'
** Do you have the right repo manifest?
since i saw other guys (in the dev forum, where i can't post to at the moment) having the exact same issue:
do a "repo selfupdate" before you run breakfast!
after the selfupdate, do "repo sync"... and then try again with breakfast, all will be well

How to use cyanogen's device trees in clean aosp

Hi, i have a problem with android device trees. I want to flash aosp from source to my zte blade 3. Kernel and source code is ready. Also i find a device tree but it is based on cyanogenmod. I copied tree under
HTML:
aosp/device/zte/atlas40
.
with
HTML:
source build/envsetup.sh
i can see device name. But when i call
HTML:
lunch
There is a huge error like this
HTML:
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_atlas40". Stop.
** Don't have a product spec for: 'cm_atlas40'
** Do you have the right repo manifest?
Can anyone help, how can i import a device tree from cyanogen to aosp.
thank you.

Please help me with porting CM13 to my LGE L65 (w55n)

I tried to port Cyanogenmod 13 to my LGE L65. Everything worked fine, till I tried to download specifications with breakfast. Device was unsupported so I had to made file roomservice.xml with links to Github kernel. I tried but I haven't helped. Then I tried this way, but of course with CM 13: "android_device_lge_w55n"(link to github but XDA blocked it). In description is instruction. Even when folder /device/lge/w55n exsisted still I had the same error: "Device w55n not found. Attempting to retrieve device repository from CyanogenMod Github (link here but XDA blocked it).
Repository for w55n not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/envsetup.mk:90: *** Unable to determine HOST_ARCH from uname -sm: Linux i686!. Stop.
** Don't have a product spec for: 'cm_w55n'
** Do you have the right repo manifest?
"
Can you help me? PLEASE:crying:

Compiling Ressurection Remix Marshmallow for SM-G313H

Hello everybody!
I need help from people, who knows how to build OS from sources
So, I tried to build RR and had such error
Code:
Building Resurrection Remix OS now!
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/vivalto3gvn/cm.mk]]: "device/samsung/sprd-common/common.mk" does not exist. Останов.
Device vivalto3gvn not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for vivalto3gvn not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/vivalto3gvn/cm.mk]]: "device/samsung/sprd-common/common.mk" does not exist. Останов.
** Don't have a product spec for: 'cm_vivalto3gvn'
** Do you have the right repo manifest?
Build failed, check the log at vivalto3gvn-20161019.log
After that I put vivalto3gvn.xml from ngoquang2708's repository (https://github.com/ngoquang2708/android_device_samsung_vivalto3gvn/tree/cm-13.0) into ./.repo/local_manifests folder and again got an error on 'repo sync'
Code:
fatal: remove-project element specifies non-existent project: CyanogenMod/android_build
P.S.: I'm using sources from repo I mentioned above
device/samsung/sprd-common/common.mk" does not exis
I'm getting the same error while building Lineage os for mint2g
Did you solved your problem????
---------- Post added at 09:17 PM ---------- Previous post was at 09:16 PM ----------
Arti42000 said:
Hello everybody!
I need help from people, who knows how to build OS from sources
So, I tried to build RR and had such error
Code:
Building Resurrection Remix OS now!
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/vivalto3gvn/cm.mk]]: "device/samsung/sprd-common/common.mk" does not exist. Останов.
Device vivalto3gvn not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for vivalto3gvn not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/vivalto3gvn/cm.mk]]: "device/samsung/sprd-common/common.mk" does not exist. Останов.
** Don't have a product spec for: 'cm_vivalto3gvn'
** Do you have the right repo manifest?
Build failed, check the log at vivalto3gvn-20161019.log
After that I put vivalto3gvn.xml from ngoquang2708's repository (https://github.com/ngoquang2708/android_device_samsung_vivalto3gvn/tree/cm-13.0) into ./.repo/local_manifests folder and again got an error on 'repo sync'
Code:
fatal: remove-project element specifies non-existent project: CyanogenMod/android_build
P.S.: I'm using sources from repo I mentioned above
Click to expand...
Click to collapse
Did you solved your problem???? How?? Please tell

Categories

Resources