[Build Help] Omnirom build error - Android Q&A, Help & Troubleshooting

Trying to build Omni Rom for Nexus 6P error is as follows.
[email protected]:~/Omnirom$ . build/envsetup.shincluding device/generic/mini-emulator-arm64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/generic/mini-emulator-mips/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including device/generic/mini-emulator-x86/vendorsetup.sh
including device/huawei/angler/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/Omnirom$ brunch angler
make: *** build/target/board/generic: Is a directory. Stop.
WARNING: Trying to fetch a device that's already there
make: *** build/target/board/generic: Is a directory. Stop.
** Don't have a product spec for: 'omni_angler'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Sources im using are -
https://github.com/Evasii0n/android_device_huawei_angler
https://github.com/Evasii0n/android_kernel_huawei_angler
https://github.com/Evasii0n/vendor_huawei_angler

Related

Building a PAC-Man ROM for an unsupported device

Hi guys!
I hereby state that I am a github and source-building n00b, and i could need your help
The thing is, I want to build a PAC-man ROM for the HTC Sensation. The pacman source is on github: https://github.com/PAC-man
And here is the device specific files, which I forked form the Pyramid CM10 Repo (Just to explore github) : https://github.com/InfinityFTW/android_device_htc_pyramid
And I was wondering, how does one add these files into the ROM, in order to build it properly?
I have searched, but I could not find a solution. I have heard about merging it in with the sources, but i'm not sure what way to go
If someone is familiar with this, please let me know.
Thanks
InfinityFTW said:
Hi guys!
I hereby state that I am a github and source-building n00b, and i could need your help
The thing is, I want to build a PAC-man ROM for the HTC Sensation. The pacman source is on github: https://github.com/PAC-man
And here is the device specific files, which I forked form the Pyramid CM10 Repo (Just to explore github) : https://github.com/InfinityFTW/android_device_htc_pyramid
And I was wondering, how does one add these files into the ROM, in order to build it properly?
I have searched, but I could not find a solution. I have heard about merging it in with the sources, but i'm not sure what way to go
If someone is familiar with this, please let me know.
Thanks
Click to expand...
Click to collapse
You need to clone device tree
Code:
cd android
cd device
mkdir htc
cd htc
git clone git://github.com/InfinityFTW/android_device_htc_pyramid.git -b jellybean pyramid
Then you need extract propietary files
Code:
cd pyramid
./extract-files.sh
And finally type
Code:
. build/envsetup.sh
lunch "select your device"
make -j4
Enviado desde mi X10i
Building error?
I got to the build part, and when i run the commands i got from a tutorial about compiling cm10 for the pyramid, and here is the entire log:
Code:
[email protected]:~/android/system$ . build/envsetup.sh; lunch cm_pyramid-userdebug; mka bacon
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
Device pyramid not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_htc_pyramid
Adding dependency: CyanogenMod/android_device_htc_pyramid -> device/htc/pyramid
Syncing repository to retrieve project.
error: .repo/manifests/: contains uncommitted changes
Repository synced!
Looking for dependencies
Adding dependencies to manifest
Adding dependency: CyanogenMod/android_device_htc_msm8660-common -> device/htc/msm8660-common
Syncing dependencies
error: .repo/manifests/: contains uncommitted changes
Done
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_pyramid'
** Do you have the right repo manifest?
The program 'schedtool' is currently not installed. You can install it by typing:
sudo apt-get install schedtool
What to do?
InfinityFTW said:
I got to the build part, and when i run the commands i got from a tutorial about compiling cm10 for the pyramid, and here is the entire log:
Code:
[email protected]:~/android/system$ . build/envsetup.sh; lunch cm_pyramid-userdebug; mka bacon
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
Device pyramid not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_htc_pyramid
Adding dependency: CyanogenMod/android_device_htc_pyramid -> device/htc/pyramid
Syncing repository to retrieve project.
error: .repo/manifests/: contains uncommitted changes
Repository synced!
Looking for dependencies
Adding dependencies to manifest
Adding dependency: CyanogenMod/android_device_htc_msm8660-common -> device/htc/msm8660-common
Syncing dependencies
error: .repo/manifests/: contains uncommitted changes
Done
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_pyramid'
** Do you have the right repo manifest?
The program 'schedtool' is currently not installed. You can install it by typing:
sudo apt-get install schedtool
What to do?
Click to expand...
Click to collapse
hey im trying to work my way thru the same thing...there is a lot of info out there, it takes forever to sort your way thru it..
so...first off, it helps us figure out problems with its output..do what it says.
sudo apt-get install schedtool
start there, then try again and see what comes up next
InfinityFTW said:
I got to the build part, and when i run the commands i got from a tutorial about compiling cm10 for the pyramid, and here is the entire log:
Code:
[email protected]:~/android/system$ . build/envsetup.sh; lunch cm_pyramid-userdebug; mka bacon
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
Device pyramid not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_htc_pyramid
Adding dependency: CyanogenMod/android_device_htc_pyramid -> device/htc/pyramid
Syncing repository to retrieve project.
error: .repo/manifests/: contains uncommitted changes
Repository synced!
Looking for dependencies
Adding dependencies to manifest
Adding dependency: CyanogenMod/android_device_htc_msm8660-common -> device/htc/msm8660-common
Syncing dependencies
error: .repo/manifests/: contains uncommitted changes
Done
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_pyramid'
** Do you have the right repo manifest?
The program 'schedtool' is currently not installed. You can install it by typing:
sudo apt-get install schedtool
What to do?
Click to expand...
Click to collapse
first of all
HTML:
The program 'schedtool' is currently not installed. You can install it by typing:
sudo apt-get install schedtool
there is a software missing install it next...
HTML:
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
it has found pyramid/cm.mk required for building but your device is configured to use the common config of msm8660 cpu so its looking for
msm8660-common
in device folder
htc
therefore find the common config download it via zip rename the folder containing the files to
msm8660-common
copy and paste it in htc folder then follow the previuos commands... i will subscribe to this thread if you get any more errors post on this thread i will be happy to help
Thanks for everything, guys, and i have now attempted to build
i used otapackage, and it seems to have stopped. Here is the latest output:
Code:
/home/martin/android/system/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/martin/android/system/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/AudioHardware.o: in function android_audio_legacy::AudioHardware::doAudioRouteOrMute(unsigned int):hardware/qcom/audio/msm8660/AudioHardware.cpp:1956: error: undefined reference to 'msm_get_voc_session'
/home/martin/android/system/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/martin/android/system/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/AudioHardware.o: in function android_audio_legacy::AudioHardware::doAudioRouteOrMute(unsigned int):hardware/qcom/audio/msm8660/AudioHardware.cpp:1961: error: undefined reference to 'msm_start_voice_ext'
/home/martin/android/system/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/martin/android/system/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/AudioHardware.o: in function android_audio_legacy::AudioHardware::doAudioRouteOrMute(unsigned int):hardware/qcom/audio/msm8660/AudioHardware.cpp:1962: error: undefined reference to 'msm_set_voice_tx_mute_ext'
/home/martin/android/system/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/martin/android/system/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/AudioHardware.o: in function android_audio_legacy::AudioHardware::doAudioRouteOrMute(unsigned int):hardware/qcom/audio/msm8660/AudioHardware.cpp:1982: error: undefined reference to 'msm_end_voice_ext'
collect2: ld returned 1 exit status
make: *** [/home/martin/android/system/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/LINKED/audio.primary.msm8660.so] Error 1
[email protected]:~/android/system$
just the last few lines wont help post more of what happened before the breaking of the build
Well, on pacmans git, there are instructions on how to build Pac-man, which includes a build-pac.sh script, and it says command not found when i run it. And i forked the htc pyramid device repo into pacmans gerrit, so i will try to do everything again, maybe something went wrong during cloning or syncing
Sent from a muffin inside a muffin using muffintalk.
InfinityFTW said:
Well, on pacmans git, there are instructions on how to build Pac-man, which includes a build-pac.sh script, and it says command not found when i run it. And i forked the htc pyramid device repo into pacmans gerrit, so i will try to do everything again, maybe something went wrong during cloning or syncing
Sent from a muffin inside a muffin using muffintalk.
Click to expand...
Click to collapse
dont use the pac script is the normal way of lunch or brunch...btw have u extracted the vendors?
speed_bot said:
dont use the pac script is the normal way of lunch or brunch...btw have u extracted the vendors?
Click to expand...
Click to collapse
Do you mean propartiary-files.sh?
And btw, i had my local repo cluttered with previous attempts at building PA, so i deleted everything and init'd the repo and synced it again.
you dont need to delete and resync again instead do
PHP:
make clean
and
HTML:
make clobber
to delete all compiled files and if you have modified the source do
HTML:
git checkout
it will remove all local changes that was you can save time and bandwidth ...
---------- Post added at 07:11 AM ---------- Previous post was at 07:10 AM ----------
InfinityFTW said:
Do you mean propartiary-files.sh?
And btw, i had my local repo cluttered with previous attempts at building PA, so i deleted everything and init'd the repo and synced it again.
Click to expand...
Click to collapse
propeitary files and just vendors for the device they cant break the build process///
Did you figure it out? if not let me know and I can help you.. send me a P.M.
Racing19969 said:
Did you figure it out? if not let me know and I can help you.. send me a P.M.
Click to expand...
Click to collapse
When I try to do make clean and make clobber, it says something like: Fatal, not a git repository, so I was unable to start over -.-
Sent from a muffin inside a muffin using muffintalk.
InfinityFTW said:
When I try to do make clean and make clobber, it says something like: Fatal, not a git repository, so I was unable to start over -.-
Sent from a muffin inside a muffin using muffintalk.
Click to expand...
Click to collapse
if thats the error your sources havent synced completely yet
It probably would not build, coz when it gives you to choose you will choose cm_* and it will build cm10.To buil PAC you need to choose pac_*
If I am not right please correct me.
Code:
Erachter system # lunch
You're building on Linux
Breakfast menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. mini_armv7a_neon-userdebug
5. mini_armv7a-userdebug
6. full_panda-userdebug
7. cm_a700-userdebug
8. cm_anzu-userdebug
9. cm_captivatemtd-userdebug
10. cm_crespo-userdebug
11. cm_crespo4g-userdebug
12. cm_coconut-userdebug
13. cm_d2att-userdebug
14. cm_d2mtr-userdebug
15. cm_d2spr-userdebug
16. cm_d2tmo-userdebug
17. cm_d2usc-userdebug
18. cm_d2vzw-userdebug
19. cm_encore-userdebug
20. cm_endeavoru-userdebug
21. cm_epicmtd-userdebug
22. cm_everest-userdebug
23. cm_evita-userdebug
24. cm_fascinatemtd-userdebug
25. cm_galaxysbmtd-userdebug
26. cm_galaxysmtd-userdebug
27. cm_grouper-userdebug
28. cm_haida-userdebug
29. cm_hallon-userdebug
30. cm_hercules-userdebug
31. cm_i777-userdebug
32. cm_i9100-userdebug
33. cm_i9100g-userdebug
34. cm_i9300-userdebug
35. cm_iyokan-userdebug
36. cm_jewel-userdebug
37. cm_maguro-userdebug
38. cm_mako-userdebug
39. mr1-staging
40. cm_mango-userdebug
41. cm_manta-userdebug
42. cm_mesmerizemtd-userdebug
43. cm_mint-userdebug
44. cm_n7000-userdebug
45. cm_n7100-userdebug
46. cm_n8000-userdebug
47. cm_n8013-userdebug
48. cm_p1c-userdebug
49. cm_p1l-userdebug
50. cm_p1n-userdebug
51. cm_p1-userdebug
52. cm_p3-userdebug
53. cm_p3100-userdebug
54. cm_p3110-userdebug
55. cm_p4-userdebug
56. cm_p4tmo-userdebug
57. cm_p4vzw-userdebug
58. cm_p4wifi-userdebug
59. cm_p5100-userdebug
60. cm_p5110-userdebug
61. cm_p930-userdebug
62. cm_p970-userdebug
63. cm_quincyatt-userdebug
64. cm_quincytmo-userdebug
65. cm_satsuma-userdebug
66. cm_skyrocket-userdebug
67. cm_smultron-userdebug
68. cm_stingray-userdebug
69. cm_su640-userdebug
70. cm_t769-userdebug
71. cm_tf101-userdebug
72. cm_tf201-userdebug
73. cm_tf300t-userdebug
74. cm_tf700t-userdebug
75. cm_toroplus-userdebug
76. cm_toro-userdebug
77. cm_urushi-userdebug
78. cm_vibrantmtd-userdebug
79. cm_ville-userdebug
80. cm_wingray-userdebug
81. pac_anzu-userdebug
82. pac_haida-userdebug
83. pac_mango-userdebug
84. pac_mint-userdebug
85. pac_smultron-userdebug
86. pac_urushi-userdebug
87. pac_zeus-userdebug
88. pac_zeusc-userdebug
89. pac_hercules-userdebug
90. pac_i9100-userdebug
91. pac_i9100g-userdebug
92. pac_quincyatt-userdebug
93. pac_skyrocket-userdebug
94. pac_cooper-userdebug
95. pac_grouper-userdebug
96. pa_crespo-userdebug
97. pa_grouper-userdebug
98. pa_maguro-userdebug
99. pa_toro-userdebug
100. pa_toroplus-userdebug
That shouldn't be a prob coz its just configuring hardware to software and pac is based on cm and aokp and aokp is inturn based on cm so I doubt this part causing problems in the future
I got the pac sources synced an all, and i run envsetup, and I breakfast it, and then i rum make -j4, and it seems to build correctly for some thime, until:
Code:
Import includes file: /home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.a2dp.default_intermediates/import_includes
system/core/libpixelflinger/codeflinger/disassem.c:710:1: warning: initialization from incompatible pointer type [enabled by default]
system/core/libpixelflinger/codeflinger/disassem.c:710:1: warning: (near initialization for 'disassemble_di.di_printf') [enabled by default]
target thumb C: libpower <= hardware/libhardware_legacy/power/power.c
target thumb C: audio.primary.default <= hardware/libhardware/modules/audio/audio_hw.c
make: *** No rule to make target `/home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/lib/libaudioalsa.so', needed by `/home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/LINKED/audio.primary.msm8660.so'. Stop.
make: *** Waiting for unfinished jobs....
Import includes file: /home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/import_includes
InfinityFTW said:
I got the pac sources synced an all, and i run envsetup, and I breakfast it, and then i rum make -j4, and it seems to build correctly for some thime, until:
Code:
Import includes file: /home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.a2dp.default_intermediates/import_includes
system/core/libpixelflinger/codeflinger/disassem.c:710:1: warning: initialization from incompatible pointer type [enabled by default]
system/core/libpixelflinger/codeflinger/disassem.c:710:1: warning: (near initialization for 'disassemble_di.di_printf') [enabled by default]
target thumb C: libpower <= hardware/libhardware_legacy/power/power.c
target thumb C: audio.primary.default <= hardware/libhardware/modules/audio/audio_hw.c
make: *** No rule to make target `/home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/lib/libaudioalsa.so', needed by `/home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/LINKED/audio.primary.msm8660.so'. Stop.
make: *** Waiting for unfinished jobs....
Import includes file: /home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/import_includes
Click to expand...
Click to collapse
ok see if the libhardware is working or not means like they patch the hardware to make the rom boot see if anybody has patched it
https://github.com/TheMuppets/proprietary_vendor_htc/tree/jellybean
szl.kiev said:
https://github.com/TheMuppets/proprietary_vendor_htc/tree/jellybean
Click to expand...
Click to collapse
Do I curl it into my device repo?
Sent from my GT-P3113 using Tapatalk 2

[Q] How to fix config makefile error

So I have been plagued by this error for the last day or so. I'm trying to build the latest Dirty Unicorns (v5.0) for the T-Mobile Samsung Vibrant (vibrantmtd). I cloned the device tree and extracted the proprietary files from the device.
I am trying to use the "breakfast" command but I keep getting this error.
Code:
@ubuntu:~/du$ . build/envsetup.sh
including device/samsung/jfltevzw/vendorsetup.sh
including device/samsung/t0lte/vendorsetup.sh
including device/samsung/p3100/vendorsetup.sh
including device/samsung/l900/vendorsetup.sh
including device/samsung/jflteatt/vendorsetup.sh
including device/samsung/vibrantmtd/vendorsetup.sh
including device/samsung/p3110/vendorsetup.sh
including device/samsung/jfltespr/vendorsetup.sh
including device/samsung/manta/vendorsetup.sh
including device/lge/hammerhead/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including vendor/du/vendorsetup.sh
including sdk/bash_completion/adb.bash
@ubuntu:~/du$ breakfast vibrantmtd
including vendor/du/vendorsetup.sh
build/core/product_config.mk:222: *** Can not locate config makefile for product "du_vibrantmtd". Stop.
** Don't have a product spec for: 'du_vibrantmtd'
** Do you have the right repo manifest?
I have checked multiple times and have even edited the du_vibrantmtd.mk file. I created that file by using the cm.mk file that was cloned via the local manifest. Can someone please help me build the rom?
theabnormalguy said:
So I have been plagued by this error for the last day or so. I'm trying to build the latest Dirty Unicorns (v5.0) for the T-Mobile Samsung Vibrant (vibrantmtd). I cloned the device tree and extracted the proprietary files from the device.
I am trying to use the "breakfast" command but I keep getting this error.
Code:
[email protected]:~/du$ . build/envsetup.sh
including device/samsung/jfltevzw/vendorsetup.sh
including device/samsung/t0lte/vendorsetup.sh
including device/samsung/p3100/vendorsetup.sh
including device/samsung/l900/vendorsetup.sh
including device/samsung/jflteatt/vendorsetup.sh
including device/samsung/vibrantmtd/vendorsetup.sh
including device/samsung/p3110/vendorsetup.sh
including device/samsung/jfltespr/vendorsetup.sh
including device/samsung/manta/vendorsetup.sh
including device/lge/hammerhead/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including vendor/du/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/du$ breakfast vibrantmtd
including vendor/du/vendorsetup.sh
build/core/product_config.mk:222: *** Can not locate config makefile for product "du_vibrantmtd". Stop.
** Don't have a product spec for: 'du_vibrantmtd'
** Do you have the right repo manifest?
I have checked multiple times and have even edited the du_vibrantmtd.mk file. I created that file by using the cm.mk file that was cloned via the local manifest. Can someone please help me build the rom?
Click to expand...
Click to collapse
Same here for the Galaxy s5...

[Q] nexus 5 building cm problem

im using this
http://wiki.cyanogenmod.org/w/Build_for_hammerhead#Install_the_SDK
i have reached the step where i have to type $ breakfast hammerhead
i have tryed a couple of time but it keeps saying
Code:
[email protected]:~/android/system$ breakfast hammerhead
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/hammerhead/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_hammerhead". Stop.
Device hammerhead not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_lge_hammerhead
Default revision: cm-10.2
Checking branch info
Default revision cm-10.2 not found in android_device_lge_hammerhead. Bailing.
Branches found:
cm-11.0
stable/cm-11.0
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
ls: cannot access device/*/hammerhead/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_hammerhead". Stop.
** Don't have a product spec for: 'cm_hammerhead'
** Do you have the right repo manifest?
[email protected]:~/android/system$
i have no idea what to do now, i have just finished the repo sync!

Porting UT to Sensation

Hi Sorry if it's wrong section for this question.
I started to port UT to Sensation, based on CM11. I've synced all required repositories:
device_htc_sensation
device_htc_msm8660-common
kernel_htc_msm8660
+ pyramid vendor.
Then I run those commands:
Code:
$ . build/envsetup.sh
including device/generic/x86/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/lge/mako/vendorsetup.sh
including device/lge/hammerhead/vendorsetup.sh
including device/htc/pyramid/vendorsetup.sh
including device/asus/flo/vendorsetup.sh
including device/asus/deb/vendorsetup.sh
including device/asus/tilapia/vendorsetup.sh
including device/asus/grouper/vendorsetup.sh
including device/samsung/manta/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_x86-eng
3. aosp_mips-eng
4. vbox_x86-eng
5. mini_x86-userdebug
6. mini_armv7a_neon-userdebug
7. aosp_mako-userdebug
8. aosp_hammerhead-userdebug
9. cm_pyramid-userdebug
[...]
Which would you like? [aosp_arm-eng] 9
build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_pyramid". Stop.
** Don't have a product spec for: 'cm_pyramid'
** Do you have the right repo manifest?
I've checked AndroidProducts.mk etc. and everything looks fine. I have no idea what to do more to fix this.
Could someone help me?
Thanks in advance!

Getting Errors while Building AOSPA

Respected Developers,
I am learning to build Rom from Source. So, I wanted to build a rom from the AOSPA Source. Source was completely downloaded but when I am trying to build the output. I am getting the following errors. Can anyone help me please.
Building AOSPA 5.0 for DEVICE
Start time: Wed Jul 8 22:49:52 IST 2015
Setting up the environment
including device/generic/mini-emulator-x86/vendorsetup.sh
including device/generic/mini-emulator-mips/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/generic/mini-emulator-arm64/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
Lunching DEVICE (Including dependencies sync)
ls: cannot access vendor/pa/products/pa_DEVICE.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "pa_DEVICE". Stop.
your device can't be found in device sources...
Traceback (most recent call last):
File "build/tools/roomservice.py", line 317, in <module>
fetch_dependencies(device)
File "build/tools/roomservice.py", line 270, in fetch_dependencies
raise Exception("ERROR: could not find your device "
Exception: ERROR: could not find your device folder location, bailing out
** Don't have a product spec for: 'pa_DEVICE'
** Do you have the right repo manifest?
Starting compilation
ls: cannot access vendor/pa/products/pa_DEVICE.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "aosp_x86_64". Stop.
Total time elapsed: 0 minutes (2.299871122 seconds)
Click to expand...
Click to collapse

Categories

Resources