Database Users

[Q] Help needed with a compilation problem

Hi all.
I have run into a little problem while compiling from source. The following error is given while attempting to compile the libgps.so file:
Code:
make: *** No rule to make target `out/target/product/leo/obj/lib/librpc.so', needed by `out/target/product/leo/obj/SHARED_LIBRARIES/libgps_intermediates/LINKED/libgps.so'. Stop.
I have got all the proprietary files needed. If I remove the gps library from compilation, then it builds without any errors.
Any ideas?
MrP.

Firefox OS Porting to Motorola G

I and my friend are trying to port Firefox OS on Motorola G device. Because of our lack of experience in the field, we are stuck. Mozilla's documentation is not that helpful and we don't know at the moment how to continue.
What we did:
- created manifest xml for the device, based on unofficial cyanogenmod for Moto G.
- synced all sources
- added manually prebuilt kernel.
- tried to build everything but it doesn't build, of course, we don't know why.
The error seem to be:
Code:
make: *** No rule to make target `out/target/product/xt1032/obj/SHARED_LIBRARIES/libwpa_client_intermediates/export_includes', needed by `out/target/product/xt1032/obj/SHARED_LIBRARIES/libhardware_legacy_intermediates/import_includes'. Stop.

Welcome to the forums !
coldSense said:
I and my friend are trying to port Firefox OS on Motorola G device. Because of our lack of experience in the field, we are stuck. Mozilla's documentation is not that helpful and we don't know at the moment how to continue.
What we did:
- created manifest xml for the device, based on unofficial cyanogenmod for Moto G.
- synced all sources
- added manually prebuilt kernel.
- tried to build everything but it doesn't build, of course, we don't know why.
The error seem to be:
Code:
make: *** No rule to make target `out/target/product/xt1032/obj/SHARED_LIBRARIES/libwpa_client_intermediates/export_includes', needed by `out/target/product/xt1032/obj/SHARED_LIBRARIES/libhardware_legacy_intermediates/import_includes'. Stop.
Click to expand...
Click to collapse
Now I haven't been on these forums long but I'd like to say congrats on ur first post ! ;0 That error
Code:
make: *** No rule to make target `out/target/product/xt1032/obj/SHARED_LIBRARIES/libwpa_client_intermediates/export_includes', needed by `out/target/product/xt1032/obj/SHARED_LIBRARIES/libhardware_legacy_intermediates/import_includes'. Stop.
means there is no target to build the path. I need more info. What compiler are you using. Or are you just using the command prompt?What's the custom kernel, you could try using CM #2 Unoffical However that'd only work if ur Moto G is currently running android with CWM (to flash the kernel when u build it) Can u link to the mozilla post, I didn't bookmark it and I can be bothered to google it Can u send me what you've done so far pls. Thanks

Or are you just using the command prompt?
Click to expand...
Click to collapse
Yes, I'm using terminal to compile everything. Actually a specialized script for that purpose. Environment versions are:
g++ - 4.6
gcc - 4.6
Actually I'm using this guide .
Yes, I use Clockwork but before that there is building problem. Anyway, the link for porting is this.
The kernel I got is from here.

Admittedly, I know jack **** about android development, but I was under the impression that Firefox OS was based on an ICS kernel? I don't think the CM11 kernel works.

coldSense said:
Yes, I'm using terminal to compile everything. Actually a specialized script for that purpose. Environment versions are:
g++ - 4.6
gcc - 4.6
Actually I'm using this guide .
Yes, I use Clockwork but before that there is building problem. Anyway, the link for porting is this.
The kernel I got is from here.
Click to expand...
Click to collapse
Never seen that error before. Know wat it means tho. Have u tried complieing with Xcode (mac) or another 3rd part app ?

Apph3x said:
Never seen that error before. Know wat it means tho. Have u tried complieing with Xcode (mac) or another 3rd part app ?
Click to expand...
Click to collapse
No. I don't have and don't use mac computers, at least for now. I did this in Linux. It seems that it just doesn't read kernel/ directory or just ignores it.

Yeah
coldSense said:
No. I don't have and don't use mac computers, at least for now. I did this in Linux. It seems that it just doesn't read kernel/ directory or just ignores it.
Click to expand...
Click to collapse
It's like its invisible....

I solved (apparently) that problem by modifying variable TARGET_KERNEL_SOURCE (device/motorola/msm8226-common/BoardConfigCommon.mk) to be absolute path but now I have another error
Code:
make: *** No rule to make target `out/host/linux-x86/bin/acp', needed by `out/debug/host/linux-x86/bin/validatekeymaps'. Stop.

@coldSense
Try this way please
Code:
rm -rf out
rm -rf objdir-gecko
./build.sh gecko
then run
Code:
./build.sh gaia
and copy file from <build_path>/gaia/profile/webapps to <build_path>/out/project/<device_name>/system/b2g/webapps
Then replace all file from out/target/<product>/system to /system of AOSP ROM
then edit ramdisk follow https://developer.mozilla.org/en-US/Firefox_OS/Porting
and flash boot.img and /system you were edit to your Motolola G
Try this way please

Any luck with this? I might try myself, but curious if you can update.

Hi everyone !
I'm currently tryaing to build Firefox OS on own device.
I have this error :
Code:
$ 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. cm_falcon-userdebug
6. mini_armv7a_neon-userdebug
Which would you like? [aosp_arm-eng] full_falcon
build/core/product_config.mk:222: *** Can not locate config makefile for product "falcon". Arrêt.
** Don't have a product spec for: 'full_falcon'
** Do you have the right repo manifest?
Could someone help me ?
Thanks a lot !

feherneoh said:
try full_falcon instead
Click to expand...
Click to collapse
Code:
$ 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. cm_falcon-userdebug
6. mini_armv7a_neon-userdebug
Which would you like? [aosp_arm-eng] full_falcon
Invalid lunch combo: full_falcon
OR
Code:
$ ./build.sh full_falcon
including device/motorola/falcon/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
build/core/product_config.mk:222: *** Can not locate config makefile for product "full_flo". Arrêt.
** Don't have a product spec for: 'full_flo'
** Do you have the right repo manifest?
> Build failed! <
Build with |./build.sh -j1| for better messages
If all else fails, use |rm -rf objdir-gecko| to clobber gecko and |rm -rf out| to clobber everything else.
A modification in device/motorola/falcon/vendorsetup.sh maybe ?
UPDATE :
Modifying vendorsetup.sh like this
add_lunch_combo full_falcon-eng

Can somebody explain me how to use a prebuilt kernel to build that please ?
Thank You
I have this error ... (in french)
Code:
No private recovery resources for TARGET_DEVICE falcon
make: *** Pas de règle pour fabriquer la cible « out/target/product/falcon/kernel », nécessaire pour « prebuilt ». Arrêt.
make: *** Attente des tâches non terminées....

h2o64 said:
Can somebody explain me how to use a prebuilt kernel to build that please ?
Thank You
I have this error ... (in french)
Code:
No private recovery resources for TARGET_DEVICE falcon
make: *** Pas de règle pour fabriquer la cible « out/target/product/falcon/kernel », nécessaire pour « prebuilt ». Arrêt.
make: *** Attente des tâches non terminées....
Click to expand...
Click to collapse
You can try to create the folder falcon-kernel inside device/motorola/ and put into it your kernel image.
In device/motorola/(your model) create the file AndroidBoard.mk and put inside:
ifeq ($(TARGET_PREBUILT_KERNEL),)
TARGET_PREBUILT_KERNEL := device/motorola/falcon-kernel/kernel
endif
Than try to rebuild.

[EXPERIMENT] Building CM11 on Cygwin

I know, I know. I'm probably gonna get a lot of "it can't be done and this is why" if what I've googled is any indication. However, difficult does not equate to impossible.
Firstly, one of the big messages I encountered online was that windows is not case sensitive, thus it can't be done even if you had a toolchain. However, it's entirely possible to turn windows 100% case sensitive (i've got cygwin mkdir Abc and aBc to prove it)
So to do this, go to control panel / programs / turn windows features on or off.
When opened, check the box that says "subsystem for UNIX-based applications" and hit okay.
Now open a browser window. Download This.
Install it, and on options near the beginning of the install check EVERYTHING.
Reboot at the end of the installation. Windows is now fully case-sensitive.
So now, after repo sync and running through the motions (get-prebuilts, breakfast, extract-files, etc)
I now encounter problem number two. Javac: command not found.
So to get around this, download an unofficial build of openjdk-1.7.0 and manually drop it in cygwin.
So after this, I type brunch d2lte
I now encounter problem number three. Build info comes up but ends abruptly at
bash: schedtool: command not found
or something like that anyway. Googling schedtool reveals information about what it does. So, to get rid of the error message, I create a dummy schedtool binary and drop it in cygwin's bin folder. Doesn't fix the build, but makes that nasty error go away.
So now, both brunch and mka will display build info then return you promptly to the command line with no error. However, what does work is the "make" command.
So, I type make bootimage.
Here comes problem number 4.
I get an error message for build/core/java.mk on line 23, saying my target SDK is invalid (here's my version), (here's available)
or something like that.
So to fix, open build/core/java.mk in notepad++, navigate to line 23, and remove the following
Code:
$(error $(LOCAL_PATH): Invalid LOCAL_SDK_VERSION '$(LOCAL_SDK_VERSION)' \
Choices are: $(TARGET_AVAILABLE_SDK_VERSIONS))
else
After which, your build will move forward to..... error number 5
Code:
make: *** No rule to make target '/home/Swisgaar/android/system/out/host/windows-x86/bin/mkbootimg.exe', needed by '/home/Swisgaar/android/system/out/target/product/d2lte/boot.img'. Stop.
Which i fixed, by downloading a .exe version of mkbootimg and dropping it in system/out/host/windows-x86/bin manually, which you can get from here.
After which, moving on to the next error, and the one i'm currently stuck on,
Code:
make[1]: Entering directory '/home/Swisgaar/android/system/kernel/samsung/d2'
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:327: /home/Swisgaar/android/system/kernel/samsung/d2/scripts/Kbuild.include: No such file or directory
make: *** empty variable name. Stop.
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:416: recipe for target 'scripts_basic' failed
make[2]: *** [scripts_basic] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/Swisgaar/android/system/kernel/samsung/d2'
build/core/tasks/kernel.mk:169: recipe for target '/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config' failed
make: *** [/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config] Error 2
Currently working on a fix. Any help is appreciated.
This experiment really isn't necessary, but it's just that, an experiment. I figure, this is my hobby, so why not.

Restl3ss said:
I know, I know. I'm probably gonna get a lot of "it can't be done and this is why" if what I've googled is any indication. However, difficult does not equate to impossible.
Firstly, one of the big messages I encountered online was that windows is not case sensitive, thus it can't be done even if you had a toolchain. However, it's entirely possible to turn windows 100% case sensitive (i've got cygwin mkdir Abc and aBc to prove it)
So to do this, go to control panel / programs / turn windows features on or off.
When opened, check the box that says "subsystem for UNIX-based applications" and hit okay.
Now open a browser window. Download This.
Install it, and on options near the beginning of the install check EVERYTHING.
Reboot at the end of the installation. Windows is now fully case-sensitive.
So now, after repo sync and running through the motions (get-prebuilts, breakfast, extract-files, etc)
I now encounter problem number two. Javac: command not found.
So to get around this, download an unofficial build of openjdk-1.7.0 and manually drop it in cygwin.
So after this, I type brunch d2lte
I now encounter problem number three. Build info comes up but ends abruptly at
bash: schedtool: command not found
or something like that anyway. Googling schedtool reveals information about what it does. So, to get rid of the error message, I create a dummy schedtool binary and drop it in cygwin's bin folder. Doesn't fix the build, but makes that nasty error go away.
So now, both brunch and mka will display build info then return you promptly to the command line with no error. However, what does work is the "make" command.
So, I type make bootimage.
Here comes problem number 4.
I get an error message for build/core/java.mk on line 23, saying my target SDK is invalid (here's my version), (here's available)
or something like that.
So to fix, open build/core/java.mk in notepad++, navigate to line 23, and remove the following
Code:
$(error $(LOCAL_PATH): Invalid LOCAL_SDK_VERSION '$(LOCAL_SDK_VERSION)' \
Choices are: $(TARGET_AVAILABLE_SDK_VERSIONS))
else
After which, your build will move forward to..... error number 5
Code:
make: *** No rule to make target '/home/Swisgaar/android/system/out/host/windows-x86/bin/mkbootimg.exe', needed by '/home/Swisgaar/android/system/out/target/product/d2lte/boot.img'. Stop.
Which i fixed, by downloading a .exe version of mkbootimg and dropping it in system/out/host/windows-x86/bin manually, which you can get from here.
After which, moving on to the next error, and the one i'm currently stuck on,
Code:
make[1]: Entering directory '/home/Swisgaar/android/system/kernel/samsung/d2'
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:327: /home/Swisgaar/android/system/kernel/samsung/d2/scripts/Kbuild.include: No such file or directory
make: *** empty variable name. Stop.
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:416: recipe for target 'scripts_basic' failed
make[2]: *** [scripts_basic] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/Swisgaar/android/system/kernel/samsung/d2'
build/core/tasks/kernel.mk:169: recipe for target '/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config' failed
make: *** [/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config] Error 2
Currently working on a fix. Any help is appreciated.
This experiment really isn't necessary, but it's just that, an experiment. I figure, this is my hobby, so why not.
Click to expand...
Click to collapse
Hey bro you are doing such a good thing for developers so please continue this thread and make some thing new
All the best :good:

[LOLLIPOP] Xperia AOSP Project

hi all
we have included this device in open devices project
you can check news about project on
http://developer.sonymobile.com/know.../open-devices/
feel free to fork, build, fix and push back
Br
J

Wohooo! Finally! [emoji106] [emoji2] [emoji3]

Excellent! An AOSP ROM is the only thing I can think is missing from an otherwise perfect device.
GCC here we come..

Andoroid L (5.0) code, binaries and guides are published

No working camera or modem, looks like we've still got awhile guys...

great news,thankss

nice

I'm syncing it now. I'm going to do a blind build (not changing anything just going with what's already there) because I have yet to unlock my bootloader and won't until they can figure out a way so at least the camera and noise cancellation don't get messed up when unlocking (if I go back to a sony stock rom I know it won't matter on AOSP)

graffixnyc said:
I'm syncing it now.
Click to expand...
Click to collapse
Preparing to build as well. Like you, I haven't BL unlocked and won't until the DRM issues are resolved.

jerpelea said:
Andoroid L (5.0) code, binaries and guides are published
Click to expand...
Click to collapse
Your work is really appreciated. FYI, I convinced a friend to buy a Z3C in large part due to your AOSP commitment. [emoji106]

Guessing we'll need to reverse engineer the camera and modem binaries? Is that right?

illogic6 said:
Guessing we'll need to reverse engineer the camera and modem binaries? Is that right?
Click to expand...
Click to collapse
no

Reverse Engeneering
In other words - SONY will deliver the required drivers or better all required driver will be there in a while...

I get compile error:
Code:
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c: In function 'bta_av_audio_sink_getconfig':
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: error: 'p_sink' undeclared (first use in this function)
if (bta_av_co_audio_sink_has_scmst(p_sink))
^
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: note: each undeclared identifier is reported only once for each function it appears in
make: *** [out/target/product/aries/obj/SHARED_LIBRARIES/bluetooth.default_intermediates/../btif/co/bta_av_co.o] Error 1
make: *** Waiting for unfinished jobs....
help appreciated

m0d said:
I get compile error:
Code:
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c: In function 'bta_av_audio_sink_getconfig':
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: error: 'p_sink' undeclared (first use in this function)
if (bta_av_co_audio_sink_has_scmst(p_sink))
^
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: note: each undeclared identifier is reported only once for each function it appears in
make: *** [out/target/product/aries/obj/SHARED_LIBRARIES/bluetooth.default_intermediates/../btif/co/bta_av_co.o] Error 1
make: *** Waiting for unfinished jobs....
help appreciated
Click to expand...
Click to collapse
just re sync your tree and fix is there

That inform you in: <insert the cpu thread number of your computer> ??? Please

I got a build to finish. I'll post the boot and system img for someone to try.. I'm not going to go through the trouble yet to make a flashable zip until we at least know it boots. I'll upload the images now

Posted the images: http://forum.xda-developers.com/z3-compact/development/img-aosp-5-0-boot-imgs-t2940499

So @NisseGurra flashed the build I made yesterday here is what he found to be broken:
no wifi, no network, some reboots, no usb storage, no external sd, no sound or camera
But its very snappy, looking forward to a functional aosp

Thank you for the guides,
I was able to compile AOSP for D5803 successfully.
A couple of issues,
First,
Has the Cherry-Pick for external/libnfc-nci/ that is provided in the guide been merged?
As I get the following error,
Code:
/external/libnfc-nci $ git cherry-pick 83cf98d0a5018e023eb9cc8b4e394957f9a6989f
fatal: bad object 83cf98d0a5018e023eb9cc8b4e394957f9a6989f
(Updated on blog to correspond with Shinano Issue.)
Second,
I get the following error when I try to output zipped package,
Code:
[B]No private recovery resources for TARGET_DEVICE aries
No recovery.fstab for TARGET_DEVICE aries[/B]
make: *** no rule to make target `otapackage'. stop.
Does this have anything to do with: TARGET_BOOTLOADER_BOARD_NAME := D5803
or that it is called aosp_d5803 (aosp_d5803.mk)
UPDATE: otatools seems to work, [" . build/envsetup.sh && time lunch aosp_d5803-userdebug && make otatools "].
But I can not find the output / output directory for package
Oh,
Is there supposed to be a userdata.img too?
Looking around a different sources mention it, however there is no userdata.img when I compiled it.
Thank you for your time

Building stock kernel for Huawei Y5II CUN-L01

Hello guys, first of all thanks for all the hard work you do for us noobs
So to begin, i am trying to build a simple kernel without any modifications (for now) using source code provided by Huawei on their official website (You will need to select Y5II(CUN-L01) to get something downloadable).
consumer*huawei*com/en/support/phones/y5ii/
(New user external url block)
DOWNLOADS
Y5II Open Source(CUN-LXX,Android5.1,kernel,en) | 2016-04-14 | 140.76 MB
Click to expand...
Click to collapse
I've tried at least 5 different toolchains, I've followed many tutorials for building kernels including the mediatek specific guides but without luck. I would be grateful if someone could point me in the right direction and tell me if I am the one doing something wrong or is the source code broken ?
From many tutorials i've followed i've come to some usual steps i do:
1.
export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=/home/mita/toolchain/bin/arm-eabi-
2.
I create a .config using predefined config
make hq6735_35u_b1n_l1_defconfig
3.
I try to do a make clean - i get an error
4.
I try to do a make mrproper - also an error
5.
I try just make and make -j4 - also errors
I can post the errors i am receiving, i have experience with android application development but i can't figure out a way to track down errors like i did in Eclipse and Android Studio.
CLEAN .
CLEAN arch/arm/kernel
"CONFIG_TRUSTONIC_TEE_SUPPORT = "
scripts/Makefile.clean:17: /home/mita/Kernel_Development/kernel-3.10/drivers/misc/mediatek/cpu_stress/Makefile: No such file or directory
make[4]: *** No rule to make target '/home/mita/Kernel_Development/kernel-3.10/drivers/misc/mediatek/cpu_stress/Makefile'. Stop.
scripts/Makefile.clean:94: recipe for target 'drivers/misc/mediatek/cpu_stress' failed
make[3]: *** [drivers/misc/mediatek/cpu_stress] Error 2
scripts/Makefile.clean:94: recipe for target 'drivers/misc/mediatek' failed
make[2]: *** [drivers/misc/mediatek] Error 2
scripts/Makefile.clean:94: recipe for target 'drivers/misc' failed
make[1]: *** [drivers/misc] Error 2
Makefile:1040: recipe for target '_clean_drivers' failed
make: *** [_clean_drivers] Error 2
Click to expand...
Click to collapse
Edit 1:
I forgot to mention i tried building on multiple OS’s: Ubuntu 32bit and 64bit, Lubuntu 32bit and 64bit, Kali Linux 64bit, and even on Raspberry Pi (i know it’s low spec but i had to try building on arm device just to rule it out) - Raspbian Stretch.
Thanks in advance for all the help

Bump
Before bumping i’ve read the rules “Once every 24h bumping”
I just not sure if there is a button to bump or is post like this required, sorry in advance if there is a bump button.

Once again a bump...
I would really be grateful if someone could tell me if source is broken or not so i can know my next steps.