Unable to build CM 10.1 with Android 4.2.2

Search This thread

sarbyn

Member
Dec 4, 2010
33
1
Castano Primo
www.sarbyn.com
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:
sarbyn@ZOIDBERG:~/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?
 

sarbyn

Member
Dec 4, 2010
33
1
Castano Primo
www.sarbyn.com
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...)
 

elmanuel

New member
Oct 15, 2013
2
0
Update

Hey sarbyn,

I stumbled upon the same error today. Did you find any fixes or further information about that?

Best regards

el manu