I am trying to compile the Android L preview branch from AOSP for the Nexus 7 (flo), I get this error:
hardware/qcom/wlan/qcwcn/wpa_supplicant_8_lib/driver_cmd_nl80211.c:65: error: undefined reference to 'os_strncpy'
collect2: error: ld returned 1 exit status
make: *** [out/target/product/flo/obj/EXECUTABLES/hostapd_intermediates/LINKED/hostapd] Error 1
make: *** Waiting for unfinished jobs....
Click to expand...
Click to collapse
I have the preview binaries installed from the official page. I can confirm I have sub-folders in vendor named flo and it contains the binaries.
I have executed make clobber as well before building it again.
Are the preview binaries only for the master branch and not for the l-preview branch?
zettez said:
I am trying to compile the Android L preview branch from AOSP for the Nexus 7 (flo), I get this error:
I have the preview binaries installed from the official page. I can confirm I have sub-folders in vendor named flo and it contains the binaries.
I have executed make clobber as well before building it again.
Are the preview binaries only for the master branch and not for the l-preview branch?
Click to expand...
Click to collapse
As far as I know the sources are not complete and cannot be compiled.
lets_zock said:
As far as I know the sources are not complete and cannot be compiled.
Click to expand...
Click to collapse
Thank you, now I got it confirmed.
Related
I'm downloaded the sources of cm and cloned @artas182x source (kernel, device and vendor) for compile CWM 6.0.4.7, but i have this error:
Code:
make: *** No rule to make target «/home/eric/source_cm11/out/target/product/p760/obj/KERNEL_OBJ/usr», necessary for «/home/eric/source_cm11/out/target/product/p760/obj/STATIC_LIBRARIES/libminui_intermediates/events.o». Stop.
How to fix this error?
Polloos said:
I'm downloaded the sources of cm and cloned @artas182x source (kernel, device and vendor) for compile CWM 6.0.4.7, but i have this error:
Code:
make: *** No rule to make target «/home/eric/source_cm11/out/target/product/p760/obj/KERNEL_OBJ/usr», necessary for «/home/eric/source_cm11/out/target/product/p760/obj/STATIC_LIBRARIES/libminui_intermediates/events.o». Stop.
How to fix this error?
Click to expand...
Click to collapse
I have the error when i build cm11. what should i do?
Hey guys, I have device tree from dianlujitao, hardware from codeaurora, Vendor and kernel source from official huawei, and try to compile cm11 for my device(HUAWEI honor 4X), but when making hardware/qcom/audio-caf/hal/audio_extn/ssr.c, I got this error message: no such header file "surround_filters_interface.h".
I search all of sync of source, google, github. still cant find header file "surround_filters_interface.h".
if guys can help, i would be grateful.
Code:
target arm C: audio.primary.msm8916 <= hardware/qcom/audio-caf/hal/audio_extn/ssr.c
hardware/qcom/audio-caf/hal/audio_extn/ssr.c:34:40: fatal error: surround_filters_interface.h: No such file or directory
compilation terminated.
make: *** [/android/cm11/out/target/product/c8817d/obj/SHARED_LIBRARIES/audio.primary.msm8916_intermediates/audio_extn/ssr.o] Error 1
make: leaving directory “/android/cm11”
[email protected]:/android/cm11#
You probably have AUDIO_FEATURE_ENABLED_SSR defined in your device, but audio-caf doesn't contain it. Look for and try to remove this in your BoardConfig.mk file in device tree.
mrjabol61 said:
You probably have AUDIO_FEATURE_ENABLED_SSR defined in your device, but audio-caf doesn't contain it. Look for and try to remove this in your BoardConfig.mk file in device tree.
Click to expand...
Click to collapse
It works, thank you!
Maybe I shouldn't change audio-caf.
Sometimes it's necessary to change something in repos, if you can't get it working.
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Now you have the opportunity to win Sony devices every 2 months
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/hero-open-source-developers/
Happy cooking
SGP712 comilation of 28.0.A.7.251 fails
@jerpelea
Code:
CC drivers/input/touchscreen/maxim_sti.o
drivers/input/touchscreen/maxim_sti.c: In function 'maxim_parse_dt':
drivers/input/touchscreen/maxim_sti.c:1133:7: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
pdata->stylus_support = (u16)val;
^
drivers/input/touchscreen/maxim_sti.c: In function 'nl_process_driver_msg':
drivers/input/touchscreen/maxim_sti.c:1602:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
if (pdata->stylus_support &&
^
drivers/input/touchscreen/maxim_sti.c:1632:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
if (pdata->stylus_support &&
^
scripts/Makefile.build:308: recipe for target 'drivers/input/touchscreen/maxim_sti.o' failed
make[3]: *** [drivers/input/touchscreen/maxim_sti.o] Error 1
scripts/Makefile.build:455: recipe for target 'drivers/input/touchscreen' failed
make[2]: *** [drivers/input/touchscreen] Error 2
scripts/Makefile.build:455: recipe for target 'drivers/input' failed
make[1]: *** [drivers/input] Error 2
Makefile:815: recipe for target 'drivers' failed
make: *** [drivers] Error 2
I will revert your stylus (really?) patches to version .31
Or please update a declaration struct maxim_sti_pdata at the proper location.
EDIT: I added
Code:
u32 stylus_support;
to 28.0.A.7.251/kernel/include/linux/maxim_sti.h
EDIT2:
I flashed the DE 28.0.A.7.251 - works.
I can not get the kernel compiled here to boot! .27 and .31 are fine with there ROMS and even last a few minutes with the rest of .251
It always (even with default configuration) bootloops.
I tried (via flashtool on linux and Windows 7) to decompress the ORIGINAL kernel.sin from the DE FTF and build a boot image via mkbootimg -> bootloop
EDIT3:
more info, AOSP also a desaster:
http://forum.xda-developers.com/showpost.php?p=62785131&postcount=58
DHGE said:
@jerpelea
Code:
CC drivers/input/touchscreen/maxim_sti.o
drivers/input/touchscreen/maxim_sti.c: In function 'maxim_parse_dt':
drivers/input/touchscreen/maxim_sti.c:1133:7: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
pdata->stylus_support = (u16)val;
^
drivers/input/touchscreen/maxim_sti.c: In function 'nl_process_driver_msg':
drivers/input/touchscreen/maxim_sti.c:1602:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
if (pdata->stylus_support &&
^
drivers/input/touchscreen/maxim_sti.c:1632:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
if (pdata->stylus_support &&
^
scripts/Makefile.build:308: recipe for target 'drivers/input/touchscreen/maxim_sti.o' failed
make[3]: *** [drivers/input/touchscreen/maxim_sti.o] Error 1
scripts/Makefile.build:455: recipe for target 'drivers/input/touchscreen' failed
make[2]: *** [drivers/input/touchscreen] Error 2
scripts/Makefile.build:455: recipe for target 'drivers/input' failed
make[1]: *** [drivers/input] Error 2
Makefile:815: recipe for target 'drivers' failed
make: *** [drivers] Error 2
I will revert your stylus (really?) patches to version .31
Or please update a declaration struct maxim_sti_pdata at the proper location.
EDIT: I added
Code:
u32 stylus_support;
to 28.0.A.7.251/kernel/include/linux/maxim_sti.h
EDIT2:
I flashed the DE 28.0.A.7.251 - works.
I can not get the kernel compiled here to boot! .27 and .31 are fine with there ROMS and even last a few minutes with the rest of .251
It always (even with default configuration) bootloops.
I tried (via flashtool on linux and Windows 7) to decompress the ORIGINAL kernel.sin from the DE FTF and build a boot image via mkbootimg -> bootloop
EDIT3:
more info, AOSP also a desaster:
http://forum.xda-developers.com/showpost.php?p=62785131&postcount=58
Click to expand...
Click to collapse
28.0.A.8.251 compiles and boots first time for me on Z3+. EDIT: seems to perform better too, with Antutu benchmark score going up from 47,800 to ~53,000
28.0.A.8.251 compiles and boots first time for me on Z3+
Click to expand...
Click to collapse
I hope they tested the source on this device.
Maybe they do not test all kitakami devices e.g. SGP712
DHGE said:
I hope they tested the source on this device.
Maybe they do not test all kitakami devices e.g. SGP712
Click to expand...
Click to collapse
Seems ok for now. I'm running it at the moment on a custom rom that has xposed installed and it's so far stable. This is the kernel in the current firmware, so I'm sure it's been tested.
AOSP uses a different kernel source
https://github.com/sonyxperiadev/kernel
please clarify
@jerpelea
All I write on compiling applies to my SGP712.
AOSP uses a different kernel source
Click to expand...
Click to collapse
Than what?
The latest kernel/include/linux/maxim_sti.h I could find in that repository on GitHub is ancient and without the stylus variable:
@kholkkholk on 29 May input: TS: Add Maxim SmartTouch Imager driver
Click to expand...
Click to collapse
I think that is OK for karin_windy.
I just followed your writeup on SONY Developer!
The last time I complained you added the fastboot flash -S hint for 2015 devices...
I just did a repo sync and added the revised binary drivers which left me first time with a booting device but without touch (today: "hard" bootloop).
Not AOSP:
The kernel for 28.A.0.8.251 you posted on SONY Developer does not compile here without the change in the kernel/include/linux/maxim_sti.h header file.
Flashing the compiled boot.img results in bootloops whatever I tried.
btw: # CONFIG_DM_VERITY is not set
Hi
i have recompiled the kernel
https://github.com/sonyxperiadev/kernel
i have tested karin_windy here with same V11 archive and flashed all 3 partitions
i have touch screen and device working fine
br
J
DHGE said:
@jerpelea
All I write on compiling applies to my SGP712.
Than what?
The latest kernel/include/linux/maxim_sti.h I could find in that repository on GitHub is ancient and without the stylus variable:
I think that is OK for karin_windy.
I just followed your writeup on SONY Developer!
The last time I complained you added the fastboot flash -S hint for 2015 devices...
I just did a repo sync and added the revised binary drivers which left me first time with a booting device but without touch (today: "hard" bootloop).
Not AOSP:
The kernel for 28.A.0.8.251 you posted on SONY Developer does not compile here without the change in the kernel/include/linux/maxim_sti.h header file.
Flashing the compiled boot.img results in bootloops whatever I tried.
btw: # CONFIG_DM_VERITY is not set
Click to expand...
Click to collapse
Thanks @jerpelea for the update!
I am mostly interested in the stagefright patches.
I do not find them in my repo synced AOSP tree.
The (compiled) patches are in ROM 28.0.A.8.251 though and last week I finally managed to get this rooted and running on my karin_windy.
I will try AOSP again if I have more time.
How is the AOSP source for the Z4, does it build yet? Looks like things are building towards a TWRP/AOSP release.
Sent from my SGP712 using Tapatalk
Is there a news on a ASOP build for the Z4?
Sent from my SGP771 using Tapatalk
FreeXperia has AOSP builds for "karin". Will they also work on "karin windy"?
streilu said:
FreeXperia has AOSP builds for "karin". Will they also work on "karin windy"?
Click to expand...
Click to collapse
FreeXperia has "karin windy" builds too.
Look here: http://fxpblog.co/aosp/aosp-5-1/ and choose the first of the 2 possible mirror providers (different sets of files are offered at each), scroll to the buttom and the latest ASOP for the Z4 is there. I have yet to try and install it as the download consistently fails and then forces me to wait for 24 hours.
http://developer.sonymobile.com/201...-camera-available-for-experienced-developers/
enjoy
J
Is anybody able to download any of the ASOP builds from http://fxpblog.co/ ?
Could they be mirrored, at a more "normal" file host?
I can upload it later today to your preferred hoster if you tell me.
streilu said:
I can upload it later today to your preferred hoster if you tell me.
Click to expand...
Click to collapse
How about https://www.androidfilehost.com/ that would seem appropriate. But frankly any host which does not force you to pay for downloads.
Got no dev account on AFH, sorry.
Hope this is ok: https://mega.nz/#!aEZlnZJS
@HotBlack77 please tell me how AOSP feels on the Z4 tab. I'm unsure about the BL unlock thing.
Gesendet von meinem SGP712 mit Tapatalk
Hi all
We have published a new snapshot, zip v14, with camera update (improved quality and stability)
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Enjoy
J
hey guys! I'm doing a test compile of CM, just trying to get it running on the Raspberry Pi 2 for kicks, and I ran into a compile issue:
Code:
Install: /out/host/linux-x86/bin/apicheck
Checking API: checkpublicapi-last
Checking API: checkpublicapi-current
Docs droiddoc: /out/target/common/docs/system-api-stubs
DroidDoc took 14 sec. to write docs to /out/target/common/docs/system-api-stubs
Checking API: checksystemapi-last
Checking API: checksystemapi-current
make: *** No rule to make target '/.txt', needed by '/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
it's very vague, so I'm wondering if anyone could provide some insight.
using sources:
https://github.com/peyo-hd/device_brcm_rpi2
https://github.com/peyo-hd/local_manifests
Device?
Edited OP with more info*
Oh lol exotic.
Device tree an all other device specific files please.
Trafalgar Square said:
Oh lol exotic.
Device tree an all other device specific files please.
Click to expand...
Click to collapse
added sources to OP
I'm having the same issue compiling CM-13.0 for GT-P5210. Any update? Thank you.
Im having the exact same error:
Code:
Export includes file: system/core/libsparse/Android.mk -- /mnt/raid5/Other/development/CM-13-0/android/system/out/host/linux-x86/obj/EXECUTABLES/simg2img_host_intermediates/export_includes
make: *** No rule to make target `prebuilts/cmsdk/api/.txt', needed by `/mnt/raid5/Other/development/CM-13-0/android/system/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
make: *** Waiting for unfinished jobs....
Starting language-specific parse...
Processing types...
C++ analysis...
Generating wrappers...
make: Leaving directory `/mnt/raid5/Other/development/CM-13-0/android/system'
#### make failed to build some targets (13:18 (mm:ss)) ####
trying to build CyanogenMod R7Plus
latest repo sync for -b CM-13.0
used breakfast to get the https://github.com/cyanogenmod/android_device_oppo_r7plus
extracted blobs using the script and a nightly.zip
Update:
to those who come here and have the ".txt" file error seen above.
this is what i did to fix it:
Code:
1. I deleted the whole source
2. i run this script "build-environment-setup.sh" get it here: https://github.com/akhilnarang/scripts
3. I initiated the repo again "repo init -u https://github.com/CyanogenMod/android.git -b "cm-13.0""
4. synced the repo using "repo sync -j4 --force-sync -f --no-tags --no-clone-bundle --no-repo-verify"
from here on continue like in the guides.
I have that error since March and had it temporarily resolved via switching to the stable branch.
Thanks to @celoxocis I finally built the cm13 nightly, although I followed only the second step from his guide.
make: *** No rule to make target '/-1.txt', needed by '/home/android/y300/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
Click to expand...
Click to collapse
Same problem on Huawei Y300 / u8833, AICP MM6.0 sourcecode. After "lunch full_u8833-userdebug" and after "make -j2" got error.
guys how solved this issue could help me anyone ???
here log ...
http://www.hastebin.com/wekudopujo.rb
---------- Post added at 10:36 PM ---------- Previous post was at 10:35 PM ----------
adeii said:
Same problem on Huawei Y300 / u8833, AICP MM6.0 sourcecode. After "lunch full_u8833-userdebug" and after "make -j2" got error.
Click to expand...
Click to collapse
umaturman said:
I have that error since March and had it temporarily resolved via switching to the stable branch.
Thanks to @celoxocis I finally built the cm13 nightly, although I followed only the second step from his guide.
Click to expand...
Click to collapse
celoxocis said:
Im having the exact same error:
Code:
Export includes file: system/core/libsparse/Android.mk -- /mnt/raid5/Other/development/CM-13-0/android/system/out/host/linux-x86/obj/EXECUTABLES/simg2img_host_intermediates/export_includes
make: *** No rule to make target `prebuilts/cmsdk/api/.txt', needed by `/mnt/raid5/Other/development/CM-13-0/android/system/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
make: *** Waiting for unfinished jobs....
Starting language-specific parse...
Processing types...
C++ analysis...
Generating wrappers...
make: Leaving directory `/mnt/raid5/Other/development/CM-13-0/android/system'
#### make failed to build some targets (13:18 (mm:ss)) ####
trying to build CyanogenMod R7Plus
latest repo sync for -b CM-13.0
used breakfast to get the https://github.com/cyanogenmod/android_device_oppo_r7plus
extracted blobs using the script and a nightly.zip
Click to expand...
Click to collapse
guys how solved this issue could help me anyone ???
here log ...
http://www.hastebin.com/wekudopujo.rb
metrixx02 said:
guys how solved this issue could help me anyone ???
here log ...
http://www.hastebin.com/wekudopujo.rb
Click to expand...
Click to collapse
Use build-environment-setup.sh from the guide. The error is gone when I installed some dependencies.
Does anyone know how to fix this damn error on Opensuse.
Afaik, all distros apart from ones based on ubuntu/debian have this error.
Silesh.Nair said:
Does anyone know how to fix this damn error on Opensuse.
Afaik, all distros apart from ones based on ubuntu/debian have this error.
Click to expand...
Click to collapse
Did you try this guide?
That's not it. It just works fine on debian, Ubuntu or mint. But never on Suse.
Sent from my Moto G (4) using Tapatalk
kronflux said:
hey guys! I'm doing a test compile of CM, just trying to get it running on the Raspberry Pi 2 for kicks, and I ran into a compile issue:
Code:
Install: /out/host/linux-x86/bin/apicheck
Checking API: checkpublicapi-last
Checking API: checkpublicapi-current
Docs droiddoc: /out/target/common/docs/system-api-stubs
DroidDoc took 14 sec. to write docs to /out/target/common/docs/system-api-stubs
Checking API: checksystemapi-last
Checking API: checksystemapi-current
make: *** No rule to make target '/.txt', needed by '/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
it's very vague, so I'm wondering if anyone could provide some insight.
using sources:
https://github.com/peyo-hd/device_brcm_rpi2
https://github.com/peyo-hd/local_manifests
Click to expand...
Click to collapse
Use
Code:
make update-api && make -j4
adityaupreti said:
it's very vague, so I'm wondering if anyone could provide some insight.
using sources:
https://github.com/peyo-hd/device_brcm_rpi2
https://github.com/peyo-hd/local_manifests
Use
Click to expand...
Click to collapse
Check my post (post #8) I'm this thread for how to fix it. You are missing an dependency. Also make sure you use Java 7 for compile Java 8 is not recommended yet.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
Silesh.Nair said:
That's not it. It just works fine on debian, Ubuntu or mint. But never on Suse.
Click to expand...
Click to collapse
I have no Idea about Suse but it works on Ubuntu.
I suggest to look at the scripts code:
https://github.com/akhilnarang/scripts
Looks at the packages being installed for Ubuntu and Arch (the arch script). Find the equivalent package names for Suse.
Or just switch to Ubuntu. Even OEM use Ubuntu for Stock compilation.
Also make sure you use Java 7 for compilation as Java 8 is not recommended yet.
celoxocis said:
Check my post (post #8) I'm this thread for how to fix it. You are missing an dependency. Also make sure you use Java 7 for compile Java 8 is not recommended yet.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
I have no Idea about Suse but it works on Ubuntu.
I suggest to look at the scripts code:
https://github.com/akhilnarang/scripts
Looks at the packages being installed for Ubuntu and Arch (the arch script). Find the equivalent package names for Suse.
Or just switch to Ubuntu. Even OEM use Ubuntu for Stock compilation.
Also make sure you use Java 7 for compilation as Java 8 is not recommended yet.
Click to expand...
Click to collapse
Haha why ur telling to me tell that guy who have error
adityaupreti said:
Haha why ur telling to me tell that guy who have error
Click to expand...
Click to collapse
Ah well scrolled down thought your post was his (due to huge quote) and replied. He will get it when he checks the thread.
Code:
make: *** No rule to make target '/.txt', needed by '/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
Try installing the bc program.
I have a custom android ROM which I have built from source. I now want to build either CWM or TWRP. However, I am having a few problems:
Where do I find the TWRP and CWM source? All I could find is CyanogenMod/android_bootable_recovery on Github for CWM and omnirom/android_bootable_recovery on Github for TWRP, but these do not look like the official repositories.
From what I can make out, the recovery partition must be built along with the custom ROM, rather than as a standalone thing. How do I set up the android source to build a different recovery source when "make recoveryimage" is run?
Set this in your device's BoardConfig.mk:
Code:
RECOVERY_VARIANT := twrp
Now it will build the sources in the folder bootable/recovery-twrp.
https://github.com/TeamWin/Team-Win-Recovery-Project
That is the official repository for TWRP, you can clone it on bootable/recovery-twrp
nagalun said:
Set this in your device's BoardConfig.mk:
Code:
RECOVERY_VARIANT := twrp
Now it will build the sources in the folder bootable/recovery-twrp.
That is the official repository for TWRP, you can clone it on bootable/recovery-twrp
Click to expand...
Click to collapse
Thanks for the quick reply.
It looks like the ROM I am using does not support the RECOVERY_VARIANT variable, so I just deleted bootable/recovery and put TWRP in its place. However, when running "make recoveryimage" I get the following error:
make: *** No rule to make target `out/target/product/EM8611_EMMC/system/xbin/busybox', needed by `out/target/product/EM8611_EMMC/obj/SHARED_LIBRARIES/libbmlutils_intermediates/teamwin'. Stop.
Any ideas how I can fix this?
cameron-martin said:
Thanks for the quick reply.
It looks like the ROM I am using does not support the RECOVERY_VARIANT variable, so I just deleted bootable/recovery and put TWRP in its place. However, when running "make recoveryimage" I get the following error:
make: *** No rule to make target `out/target/product/EM8611_EMMC/system/xbin/busybox', needed by `out/target/product/EM8611_EMMC/obj/SHARED_LIBRARIES/libbmlutils_intermediates/teamwin'. Stop.
Any ideas how I can fix this?
Click to expand...
Click to collapse
Do you have the cm13/Marshmallow sources?
If so, it doesn't include busybox, you have to download it:
Code:
git clone https://github.com/CyanogenMod/android_external_busybox external/busybox -b cm-13.0