I've managed to solve a few errors (or so I think) by further editing mk files.
make: *** No rule to make target `out/target/product/gio5660M/obj/lib/libaudio.so', needed by `out/target/product/gio5660M/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/LINKED/libaudioflinger.so'. Stop.
But so far I've been mostly feeling my way around...
Are there any more systematic ways to approach this error?
Thanks in advance,
Darkshado
Idk if it's available for download through the repositories by the name of audioflinger
sudo apt-get install audioflinger
If not then just search the file. It may fix the problem to just download it.
I searched some more, and it really is an integral part of Android's libaudio files.
However I might have found another way to get it to build, it's running right now.
I modified the mk files to build from the /hardware/msm7k/ folder instead of files I copied over in /device/
Well that's good. At least you're getting it to work. Sorry I couldn't have been of more help.
Unfortunately its back to the drawing board as it aborts with the same fatal error, only in a different place it seems.
sudo apt-get install libaudio-dev
Possibly?
Also, I've read this might work.
adb pull /system/lib/libaudio.so proprietary/libaudio.so
I had this problem with the OGDroid. Turns out I had the files in vendor/motorola/sholes/sholes/ instead of just vendor/motorola/sholes/, where it should have been.
Not sure if that's the case for you, but it fixed things for me.
Related
So I'm trying to use the MIUI radio (which functions on the latest Defy-based build for the DX) on CM7. I figure it should work given a little trickery. I resigned the APK, pushed it to /system/app, set the permissions, and rebooted, but it didn't work. I checked the logcat and this is the relevant line:
W/AssetRedirectionManager( 1718): Unable to attach target package assets for com.miui.fmradio
I don't know what that means. I was hoping someone could help me out? I've seen similar logcats on these forums, but never directly addressed by the thread topic. Attached is the full logcat from boot.
Any insight, either on my specific problem or general APK/assets/resource knowledge would be greatly appreciated.
Hey!
I'm trying to build an ICS version for my p990 from the VorkTeam's repos. I'm getting an error in the build process that I haven't been able to solve though.
I've extracted the files from my current CM7 ROM with the ./extract-files.sh script so all the files should be in place and they are located under vendor/lge/p990/proprietary/.
Could someone more knowable then me help me figure out what this error could be due to, that would be awesome. I can't really figure out what "rule to make target" could be missing. According to at least one of the members on the VorkTeam they have not seen this error and their source should build fine.
make: *** No rule to make target `out/target/product/p990/obj/lib/libnvdispmgr_d.so', needed by `out/target/product/p990/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/LINKED/libsurfaceflinger.so'. Stop.
Any help or pointers is greatly appreciated.
Thanks.
Im building cyanogenmod 11 for the htc dna, this is my first attemt into building my own rom however I seemed unable to get a bootable zip until now.
I captured a screen.log to scan for any errors later (NO clue what im looking for in here)
So I searched the log for "waiting for unfinished jobs" because this is always what seems to happen to me and this time i was ready to find the errors. Well lucky for me every job finished so what I am wondering is does this mean that my build compiled correctly even though i have warnings like crazy in the 140000+ lines of the screen.log
as for the second question. Is there any easier eay to scan a screen.log for where the build errors are or do i just have to run through all the line blind because im not exactly sure what to look for yet (one day i plane to have more of an understanding this is just early in my rom building career.)
EDIT~!~!~!~!~!~!~
Okay new problem. When i originally synced my repo to cm11 i was on python 2.7.4 and thats how i tried the first build on this ubuntu and it failed. I updated to python 2.7.6 because every time i grabbed 2.7.5 i kept getting unsuspected End Of File errors. So I installed 2.7.6 with (sudo make install) instead of (sudo make altinstall) like some guides read (This is because when i used altinstall brunch always gets to waiting for unfinished jobs.)
What i was getting at was now that im on python 2.7.6 when i try to initialize another repo to another folder I receive this error.
fatal: Cannot get https://gerrit.googlesource.com/git-repo/clone.bundle
fatal: error unknown url type: https
Click to expand...
Click to collapse
However I can repo sync my cm11 repo still just can not initialize a new repo to another directory
Any help is appreciated
hipsh0t said:
Im building cyanogenmod 11 for the htc dna, this is my first attemt into building my own rom however I seemed unable to get a bootable zip until now.
I captured a screen.log to scan for any errors later (NO clue what im looking for in here)
So I searched the log for "waiting for unfinished jobs" because this is always what seems to happen to me and this time i was ready to find the errors. Well lucky for me every job finished so what I am wondering is does this mean that my build compiled correctly even though i have warnings like crazy in the 140000+ lines of the screen.log
as for the second question. Is there any easier eay to scan a screen.log for where the build errors are or do i just have to run through all the line blind because im not exactly sure what to look for yet (one day i plane to have more of an understanding this is just early in my rom building career.)
Click to expand...
Click to collapse
There are a ton of warnings, one error (failing to build modules, which you can ignore). The last thing printed is the path to the zip. If it printed that, the build completed successfully.
To find the errors, try searching from the end for Error (capital E).
@crpalmer
Yea I just found the zip its booting as we speak.
Thanks
So excited this is finally working I been messing with Ubuntu for like 2 weeks
hipsh0t said:
Okay new problem. When i originally synced my repo to cm11 i was on python 2.7.4 and thats how i tried the first build on this ubuntu and it failed. I updated to python 2.7.6 because every time i grabbed 2.7.5 i kept getting unsuspected End Of File errors. So I installed 2.7.6 with (sudo make install) instead of (sudo make altinstall) like some guides read (This is because when i used altinstall brunch always gets to waiting for unfinished jobs.)
What i was getting at was now that im on python 2.7.6 when i try to initialize another repo to another folder I receive this error.
However I can repo sync my cm11 repo still just can not initialize a new repo to another directory
Click to expand...
Click to collapse
I'm not expert so crpalmer or someone may be able to tell you more directly. But here is a few things:
Did you install SSL for python?
Code:
$ sudo apt-get install libssl1.0.0=1.0.1-4ubuntu5.3
$ sudo apt-get install libssl-dev
Try reinstalling Python. I installed it the simple way and its working fine for my builds.
Code:
$ sudo apt-get install python
What repo were you trying to initialize?
tes4p00ner said:
I'm not expert so crpalmer or someone may be able to tell you more directly. But here is a few things:
Did you install SSL for python?
Code:
$ sudo apt-get install libssl1.0.0=1.0.1-4ubuntu5.3
$ sudo apt-get install libssl-dev
Try reinstalling Python. I installed it the simple way and its working fine for my builds.
Code:
$ sudo apt-get install python
What repo were you trying to initialize?
Click to expand...
Click to collapse
It was every repo and I tried the normal way I must have started from a fresh Ubuntu install once every few days figuring out where I went wrong. I'm going to check on the ssl for Python. So far this is the furthest I've made it. One built cm11 rom and I'm only learning more every day I research
EDIT------------
[email protected]:~$ sudo apt-get install libssl1.0.0=1.0.1-4ubuntu5.3
[sudo] password for jk:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '1.0.1-4ubuntu5.3' for 'libssl1.0.0' was not found
Click to expand...
Click to collapse
Im trying to make sure my precise repos are in place for apt-get however im still getting this message.
okay so trying to build from source FFOS for the ZTE Open C and keep getting the same error even tried switching Ubuntu Distro to 14.04.1 from 14.10 tried google and didnt come up with much of anything on the subject short of many people experiance this issue it seems but nobody gets it resolved and if they do they dont post on how they did it
Pulling "trace_util"
cp: cannot stat ‘../../../backup-flame/system/bin/trace_util’: No such file or directory
Failed to pull trace_util. Giving up.
> Build failed! <
above is the error i get any help is appreciated
Franzferdinan51 said:
okay so trying to build from source FFOS for the ZTE Open C and keep getting the same error even tried switching Ubuntu Distro to 14.04.1 from 14.10 tried google and didnt come up with much of anything on the subject short of many people experiance this issue it seems but nobody gets it resolved and if they do they dont post on how they did it
Pulling "trace_util"
cp: cannot stat ‘../../../backup-flame/system/bin/trace_util’: No such file or directory
Failed to pull trace_util. Giving up.
> Build failed! <
above is the error i get any help is appreciated
Click to expand...
Click to collapse
Follow up to this ive did a little searching my self and included in the init.target.rc is a NFC area that seems to be the "Root" of the problem but unfortunatly thats all the information ive come across so please anyone that has information how to bypass this error or fix it , i whould be very greatful
fixxed but still issues
Franzferdinan51 said:
Follow up to this ive did a little searching my self and included in the init.target.rc is a NFC area that seems to be the "Root" of the problem but unfortunatly thats all the information ive come across so please anyone that has information how to bypass this error or fix it , i whould be very greatful
Click to expand...
Click to collapse
okay so for those of you who ever run into this issue this is how to bypass unforunatly after flashing i still run into errors on ./flash.sh fails to erase userdata but well start from the top and leave that for others since im almost positive that error is due to me not doing something correct
okay so basically its pretty simple go too the link and copy openc.xml at the link below and attached for easy access
https://bugzilla.mozilla.org/attachment.cgi?id=8429932
https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C
then follow the directions listed but to keep it simple for those of you whom dont want to look to far
Clean up the B2G directory, removing the unneeded directories:
rm -rf objdir-gecko/ out/ backup-flame/
Now configure Firefox OS with the following command: (Note that the path cannot contain spaces, otherwise it won't work).
./config.sh flame /PATH/TO/openc.xml
You can then build the Gecko component and Flash it to your phone using the following:
./build.sh gecko
./flash.sh gecko
You should now upgrade Gaia as well, so the upgraded version of Gecko works with the version of Gaia on the device:
cd gaia
make reset-gaia
and thats how i fixxed it unfortunatly like i said when i got to ./flash.sh the whole build it fails at user data
but once again pretty sure thats only me if anyone has information on this let me know please
all credit from this goes to mozilla i just decided to post it in an easy location for everyone who runs into this
thank you mozilla developers
I've been using CM12.1 for couple of months, love it. Found some bugs and waited a few nightlies (few weeks per "nightly") and after that tried to make a bug report.... not accepted, because CM12.1 is not developed anymore. CM13 is not available for Z2, so I tried to build CM13 myself, following the guide found on cyanogenmod site. Sorry, as a new member, can't link that URL here... It fails... I have gone past that point to extract the proprietary "blobs" from my phone (running the mentioned CM12.1) and tried again the breakfast sirius command. I'm unable to paste results here, because being a new member... look the result from pastebin com with /mwBfxHEL behind the URL...
The reason seems obvious, missing that msm8974-common-vendor.mk file. Can't find it on my computer using "locate". Can't find it using google. Don't know how to fix this or get past this... Any help appreciated!
Nobody has build CM13 for Z2???
The issue you are describing likely results from the blob extraction for msm8974-common not operating correcty: Please execute (or re-execute) the extraction scrip in this folder of the device tree as well (should be device/sony/msm8974-common). Could you paste the output after running that script, please?
Diewi said:
The issue you are describing likely results from the blob extraction for msm8974-common not operating correcty: Please execute (or re-execute) the extraction scrip in this folder of the device tree as well (should be device/sony/msm8974-common). Could you paste the output after running that script, please?
Click to expand...
Click to collapse
OK, that advice helped. Tried 'breakfast sirius' again, it went longer, complained about something missing in shinano-common folder. Used your approach again and got past that one too. After that, 'breakfast sirius' succeeded. I tried 'brunch sirius' and it failed. Tried it again, it got longer before failing again... did "while [ $? -ne 0 ]; do !! done" to try building until it succeeds. After quite a while, I stopped it, ran brunch sirius command and copied the output to pastebin.
Take a look at pastebin.com/Qz4hq1aZ
Something about libta.so?
Flexy75 said:
OK, that advice helped. Tried 'breakfast sirius' again, it went longer, complained about something missing in shinano-common folder. Used your approach again and got past that one too. After that, 'breakfast sirius' succeeded. I tried 'brunch sirius' and it failed. Tried it again, it got longer before failing again... did "while [ $? -ne 0 ]; do !! done" to try building until it succeeds. After quite a while, I stopped it, ran brunch sirius command and copied the output to pastebin.
Take a look at pastebin.com/Qz4hq1aZ
Something about libta.so?
Click to expand...
Click to collapse
Should I extract the blobs from a Z2 with OEM firmware? I vaguely remember that TA refers to something to do with DRMs that you lose when you unlock the phone to be able to install other firmwares...
Sorry for the delay.
This is an issue with the vendor files. I think that th extrction scripts are somewhat outdated, or didn't the extraction script didn't find some files. There should be a repo on github which should provide you with the needed files. Another possibility would be to extract and mount the system image of a stock and let the script process these files (there is a cmdline switch for pointing the script to it: please have a look into this script for the according switch).
Hope this helps.
Diewi said:
Sorry for the delay.
This is an issue with the vendor files. I think that th extrction scripts are somewhat outdated, or didn't the extraction script didn't find some files. There should be a repo on github which should provide you with the needed files. Another possibility would be to extract and mount the system image of a stock and let the script process these files (there is a cmdline switch for pointing the script to it: please have a look into this script for the according switch).
Hope this helps.
Click to expand...
Click to collapse
OK, found the repo. Got all the files, got the build to succeed! Thank you very much! Just few more questions... There is not just one zip file in the directory... which one to install? How do I install the zip file the build created? Perhaps via booting to recovery and installing it from there? And how does it behave? Like a upgrade, or a clean install?