Hello everyone,
I recently decided to try and build DU with Sultans device tree and kernel. The issue here being I just ran into an error dealing with a makefile:
make: *** No rule to make target '/home/rj/android/duonyx/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.internal_intermediates/classes.jack', needed by '/home/rj/android/duonyx/out/target/common/obj/APPS/ConfigPanel_intermediates/with-local/classes.dex'. Stop.
make: *** Waiting for unfinished jobs....
CM stuff is not utilized by DU so I'm unsure as to why it would even show up whence building DU besides the repositories based off of the CM ones modified by Sultan.
My manifest and device tree can be found here:
https://github.com/DU-Onyx
Thanks everyone!
Looks the answer to my question was in the question itself
Not sure what you mean... how was this resolved? Thanks for your time.
Nu Guy said:
Not sure what you mean... how was this resolved? Thanks for your time.
Click to expand...
Click to collapse
This post is a year old??? Why did you necro it? Or at the very least check the date? That makes absolutely no sense. That's coming from someone that can hardly see too
Related
I have an Inspire 4g for my phone and I have been trying to follow the cyanogenmod wiki to get a compiled kernel. I am just trying to get it to build to the defaults at this time before I tweak anything. I am on the android-msm-2.6.35-froyo-stable branch, I also tried the android-msm-2.6.37 branch with same results.
If I pull the config from my working version(CM7) and build using that and accepting all defaults its always fails with this error:
Code:
CC arch/arm/mach-msm/acpuclock-7x30.o
arch/arm/mach-msm/acpuclock-7x30.c:32: error: conflicting types for 'acpuclk_power_collapse'
arch/arm/mach-msm/acpuclock.h:31: note: previous declaration of 'acpuclk_power_collapse' was here
arch/arm/mach-msm/acpuclock-7x30.c:47: error: conflicting types for 'acpuclk_set_rate'
arch/arm/mach-msm/acpuclock.h:30: note: previous declaration of 'acpuclk_set_rate' was here
make[1]: *** [arch/arm/mach-msm/acpuclock-7x30.o] Error 1
make: *** [arch/arm/mach-msm] Error 2
I have also tried setting the CPU speeds to see if that was it but still ends up failing with the same error as above
if I use the exact same config accepting all defaults like above on the HTC-msm branch from cyanogen its compiles just fine. I have tried a couple of the defconfig's and the msm ones compile fine, but the cyanogen_msm_defconfig seems to be for another device by looking at the default options. So is there a premade defconfig that I am not seeing in there that I should be using or why does the .config I pull from the working CM7 not work? I would think accepting the defaults this way it should just build fine since it the same kernel version. Can someone please give me some hints or let me know what default defconfig I should use and start from there. I have followed the wiki to a T as well as a few other guides around always with the same results using cm-kernel. I do have expierence building kernel's and OS's for embedded devices and just cant get what I am missing here, I know its probably something stupid on my part being new to Android.
Thanks for any and all help, info, tips
I had the same problem for DHD
Untill I downloaded appropriate kernel
if you use CM kernel from their git it's not configured for DHD or Inspire 4G...
There are a lot of things to be done before it can compile...
I use 2.6.32 from Kali- and it works wonders..
You must find kernel just for your device
no need to pull the config from your device... Mine didn't work.. I used default config for ACE (dhd)
First:
make cyanogen_ace_defconfig
make menuconfig
if there are no inspire or ace defconfigs in /arch/arm/configs than you can't build the kernel that easily
hope I helped a little.. I've lost 7 days to figure that out
LorD ClockaN said:
hope I helped a little.. I've lost 7 days to figure that out
Click to expand...
Click to collapse
Yes you helped tons it made things clear in my error. I like u spent a long time before asking. Feel dumb for not getting cm-kernel is different than the htc-msm ones. I will have to check out the one u said I just used the cyanogen msm branch today. Thanks again for your time
Sent by miniature turtles using the XDA Android app
HTC Inspire - Cyanogenmod rom
I am attempting to build AOKP from source, mainly just to learn a little more about how it all work so I can get more into development to help out around here rather than just mooch off of the very talented devs in this forum.
I have followed the guide posted here
http://forum.xda-developers.com/showthread.php?t=1552090
and changed what needed to be changed for the AOKP source.
when attempting ./extract-files.sh, i get errors stating that certain files are not on my phone(I am running stephen's AOKP 30.1 Glitched).
When I attempt to build, the first error I get is
make: *** No rule to make target `vendor/samsung/fascinatemtd/proprietary/gps.xml', needed by `out/target/product/fascinatemtd/system/vendor/etc/gps.xml'. Stop.
make: *** Waiting for unfinished jobs....
and then kicks me back to the command prompt.
GPS.xml is one of the files that the ./extract-files.sh does not find.
Please tell me what I am doing wrong?
Should I be on an official build of AOKP to do this? I didn't think stephen changed that much in the ROM. Or should/could I be on stock to pull these files?
Any help is greatly appreciated, I am hoping to get this figured out so I can help dev for some of the devices around here.
thanks,
Kyle
You shouldn't need to run the extract script, the proprietary files are already in the repo. Just sync and build!
What he said... and a little bit better of a tip. Switch Github/AOKP to Github/AOKPSGS and you get our glitched up repo.... be warned I mess around a lot in there...
Sent from my Glitched AOKP Unicorn.
Thanks Stephen, switching the repo now. I think there may a problem with the AOKP github, looking at the fascinatemtd-vendo-blobs.mk file, the one from the AOKP github calls for a few proprietary files like the GPS.xml that are not in the vendor/samsung/fascinatemtd/proprietary folder which was tripping me up. Looking at the one from your AOKPSGS, it doesn't call for it.
I'll wait for this repo to sync and give it another try and report back.
Update:
Worked like a charm! Thanks! Now to start digging around!
I'm relatively new here. I posted a few times last year. Before posting this time I was careful to check for an existing post that answered my question or pointed to an answer. Many apologies if I missed that. So here goes.
After flashing Peter Alfonso's Bugless Beast ROM (4.1.1 JRO03C) on my Galaxy Nexus (maguro) and running it for about a week, I was so impressed I downloaded the source from his developers link and attempted to build it. Unfortunately, shortly after initiating the make it stops with an error. Here's a snippet of the error messages (with some context) when the build stops:
--- begin
Import includes file: out/host/linux-x86/obj/SHARED_LIBRARIES/libdynamic_annotations-host_intermediates/import_includes
Export includes file: external/valgrind/dynamic_annotations/Android.mk -- out/host/linux-x86/obj/SHARED_LIBRARIES/libdynamic_annotations-host_intermediates/export_includes
make: *** No rule to make target `out/target/common/obj/APPS/Gallery2_intermediates/classes.jar', needed by `out/target/common/obj/APPS/CameraTests_intermediates/classes-full-debug.jar'. Stop.
make: *** Waiting for unfinished jobs....
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
--- end
I've read the above error messages many times but I have no idea what to do about it. Maybe it has something to do with Sun Java versus Open Java. My build environment has Sun Java 6 if that helps. I honestly believe the build error has something to do with how my development environment differs from that used by others who have successfully built Bugless Beast Jellybean.
My development environment is 64-bit Ubuntu 10.04 LTS based on Google's instructions in their AOSP documentation web pages. I believe my development environment is good because I have used it many times to successfully build and flash ROMs for my Nexus devices following Google's instructions.
So I am at a loss to say exactly what the problem is or how to fix it. Any help would be greatly appreciated. Anyone of course is welcome to reply, but I would especially like to hear from anyone who has successfully built and flashed their own Bugless Beast Jellybean ROM including the man himself Peter Alfonso - but I know he is swamped and I do not expect to hear from him directly.
This is either too long, unclear, or posted in the wrong place. There's too much talent on XDA for this be neglected.
I will shorten it, make it more direct, and interesting perhaps, and post it again. But where?
Got a tweet from Pete saying to try
Code:
make -j16 otapackage
. It seemed to work for me.
I noticed that there is no current port going or started for ubuntu touch, so today i thought i would start that project.
the first thing i noticed was that ubuntu's documentation for porting is one of the worst things ive ever seen, so this will probably end up being kind of a guide until we get a working image or something.
first thing is you will absolutely need Linux. Im using ubuntu for ease of use, although I do build android on arch.
I set up a directory structure on my pc just for android development. i have ~/android/platforms/ in which i have cm11, ubuntu-touch carbon, etc.
so to summarize how i got this started:
Code:
$ mkdir ~/android/platforms/ubuntu-touch-phablet-4.2.2_r1
$ cd ~/android/platforms/ubuntu-touch-phablet-4.2.2_r1
$ repo init -u git://phablet.ubuntu.com/aosp/platform/manifest.git -b phablet-4.2.2_r1 && repo sync -j16
Now im really hoping that is the correct branch. I tried to follow the "porting guide" and its just full of out dated information that lead me to sync a few repos incorrectly. :silly:
after a few failed builds and some common error logs i finally figured i was on the wrong branch. This attempt shall be on 4.2.2_r1 as that appears to be the latest. (I hope)
anyway the rest is still in progress. My sources will be on github for people to help out.
Device
Kernel
also: im on irc on freenode at #oudhitsquad pressy4pie
[update]
i have a huge problem in the real world, so i will have virtually no time to get this updated for now. I am really sorry, hopefully i can get it going again soon
XDA:DevDB Information
Ubuntu Touch , ROM for the ONEPLUS ONE
Contributors
konnorrigby
Version Information
Status: Testing
Created 2014-09-24
Last Updated 2014-10-13
cool mate! thanks for that...cheers!
Nice. Would love to give a hand here, I'll visit the Ubuntu workshop at devcon this weekend to learn some new fresh information about porting. Maybe I'll give it a try later too.
Good news!
Looking forward to see the first builds getting ready for testing.
:good::highfive:
Mackis said:
Good news!
Looking forward to see the first builds getting ready for testing.
:good::highfive:
Click to expand...
Click to collapse
This will take a while. As you can see in OP, there are problems with the porting guide from Ubuntu. When I get back from devcon, I hope to know more about porting.
So turns out i was in fact syncing the wrong repo again. shame on me for following a ubuntu guide. it appears there is a 4.4_r1 repo also. Syncing again. I have a fairly slow connection. ill see what i can get done on 4.2.2_r1 though in the mean time
I have high hopes...
Would like to a working rom.. Wish you best of luck and hope its smooth sailing...
Thanks for scarifying your time and efforts for us
Couple of month ago I wanted to port it for my lenovo phone, but I gave up (sources limited)
Anyway, to say that I went on the IRC channel to get some support, they are willing to help (even though you have to be patient, it's IRC, hundreds of people connected nobody on their computer.). So they told me that (as you noticed) the porting manual is outdated, and they are now basing their port on AOSP. Tthis should not be a problem to use CM though.
So try to get some help there, they know what you have to do
I could give a hand, I have a good internet connection. Could you post all the command history you ran, so I can try on my side?
cheers
ive got some progress, i think.
ubuntu-touch has rebased to aosp rather than cyanogenmod, which makes things a lot more difficult.
if youve ever tried to build something that is not a nexus device against aosp it is a huge pain in the ass. Bacon has a lot of cm specific parts that need to built so it is difficult to get it to build w/ aosp. but to explain where i am currently, i synced 4.4_r1, and now since aosp doesnt build kernel and bacon requires kernel to be packed up with dtb and stuff, i went to my cm11.0 repo, did my ubuntu-touch modifications to kernel, did
Code:
lunch cm_bacon-userdebug && make -j32 bootimage
which (i think) gives me the correct bootimage. What we need now is the android part. i am building inside the ubuntu-touch-4.4_r1 dir with:
Code:
lunch aosp_bacon-userdebug && make -j32 systemimage
that eventually errors out to:
Code:
make: *** No rule to make target `out/target/common/obj/JAVA_LIBRARIES/core_intermediates/classes.jar', needed by `out/target/common/obj/JAVA_LIBRARIES/qcmediaplayer_intermediates/classes-full-debug.jar'. Stop.
make: *** Waiting for unfinished jobs....
im not sure why because as far as i know, ubuntu-touch shouldnt be building java parts and that is the first part of building the java stuff in a regular android build. ive never ported ubuntu-touch before. so someone let me know if ive messed something up. i dont think there is something in the device makefiles that starts the java build.
any help
just in case, are you using opensources java or oracle one? I am pretty sure it doesn't work with opensource java. But i would expect that you get the error earlier...
I'm not sure if you already have this or not but Oneplus has aosp kernel sources at https://github.com/OnePlusTech/android_kernel_oneplus_one .
konnorrigby said:
ive got some progress, i think.
ubuntu-touch has rebased to aosp rather than cyanogenmod, which makes things a lot more difficult.
if youve ever tried to build something that is not a nexus device against aosp it is a huge pain in the ass. Bacon has a lot of cm specific parts that need to built so it is difficult to get it to build w/ aosp. but to explain where i am currently, i synced 4.4_r1, and now since aosp doesnt build kernel and bacon requires kernel to be packed up with dtb and stuff, i went to my cm11.0 repo, did my ubuntu-touch modifications to kernel, did
Code:
lunch cm_bacon-userdebug && make -j32 bootimage
which (i think) gives me the correct bootimage. What we need now is the android part. i am building inside the ubuntu-touch-4.4_r1 dir with:
Code:
lunch aosp_bacon-userdebug && make -j32 systemimage
that eventually errors out to:
Code:
make: *** No rule to make target `out/target/common/obj/JAVA_LIBRARIES/core_intermediates/classes.jar', needed by `out/target/common/obj/JAVA_LIBRARIES/qcmediaplayer_intermediates/classes-full-debug.jar'. Stop.
make: *** Waiting for unfinished jobs....
im not sure why because as far as i know, ubuntu-touch shouldnt be building java parts and that is the first part of building the java stuff in a regular android build. ive never ported ubuntu-touch before. so someone let me know if ive messed something up. i dont think there is something in the device makefiles that starts the java build.
any help
Click to expand...
Click to collapse
Just post any further errors you'll get here and I'll try to get help at devcon this weekend. Keep it up!
b8e5n said:
just in case, are you using opensources java or oracle one? I am pretty sure it doesn't work with opensource java. But i would expect that you get the error earlier...
Click to expand...
Click to collapse
im using oracle, but that isnt the problem. Ubuntu-touch takes the java out so its not there for a reason but something is causeing it to want to build the java parts..
i think im going to go ahead and fork hammerhead which i know builds, and give it 1+1 parts.
konnorrigby said:
im using oracle, but that isnt the problem. Ubuntu-touch takes the java out so its not there for a reason but something is causeing it to want to build the java parts..
i think im going to go ahead and fork hammerhead which i know builds, and give it 1+1 parts.
Click to expand...
Click to collapse
Good Idea! Let us know
I met @ciwrl at devcon, he'll come here and tell you how to squash that problem.
Great to see someone working on it.
Will bookmark this topic
News?
This is exciting to see, I'd love to try Ubuntu touch on the OPO. I have Ubuntu, but I'm mainly in Linux Mint, or Kali. Let me know if there is anyway I can assist with testing, Web storage/hosting, etc.
@konnorrigby, as @ciwrl suggested at devcon, you should disable the whole java part from the build. Ubuntu doesn't need any of it to build and run.
Wow! I really want to see Ubuntu on my OnePlus one. really Excited. Good luck guys
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.
https://developer.sony.com/develop/open-devices/
Unified 4.4 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Bug tracker
https://github.com/sonyxperiadev/bug_tracker/issues
Hi,
We have updated the project page to reflect the latest progress
http://developer.sonymobile.com/open-devices/
Enjoy
J
I recently got the xperia X, which is an awesome device, and this is good news! Thanks a lot. Developers, please!
Does flashing those ROMS means that they are turned into Nexus?
I assume we will loose the camera software and also the radio?
ykphuah said:
Does flashing those ROMS means that they are turned into Nexus?
Click to expand...
Click to collapse
No
ykphuah said:
Does flashing those ROMS means that they are turned into Nexus?
Click to expand...
Click to collapse
Yes. It turn your phone into 6p. Including your camera quality.
K
Thx
Bye.
Lol, I am sensing a lot of sarcasm here.
I have used Nexus before, and I have used HTC devices that are flashed to AOSP.
So can I confirm that we loose the camera software and also the FM radio if we flash this AOSP? I don't have a better way to describe this other than "make it a nexus".
ykphuah said:
Lol, I am sensing a lot of sarcasm here.
I have used Nexus before, and I have used HTC devices that are flashed to AOSP.
So can I confirm that we loose the camera software and also the FM radio if we flash this AOSP? I don't have a better way to describe this other than "make it a nexus".
Click to expand...
Click to collapse
Forgive me if I am wrong, but last time I used the sony open devices firmware on my previous xperia, we kept the camera quality just with the AOSP app.
@jerpelea when following the commands here, and following them exactly step-by-step based on the guide, I get the following:
[ 4% 2253/50550] host C++: llvm-tblge.../utils/TableGen/CodeGenDAGPatterns.cpp
ninja: build stopped: subcommand failed.
build/core/ninja.mk:148: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
#### make failed to build some targets (03:57 (mm:ss)) ####
Click to expand...
Click to collapse
Anyone else tried to follow the steps?
FYI, FreeXperia has released an experimental Nougat build for the X (suzu), which can be downloaded here.
I presume you can flash it onto your device by using fastboot.
iH8Ecchi said:
FYI, FreeXperia has released an experimental Nougat build for the X (suzu), which can be downloaded here.
I presume you can flash it onto your device by using fastboot.
Click to expand...
Click to collapse
Yeah they're found here and the last one was a week ago.
My reason for posting was I was trying to build myself
jerdog said:
@jerpelea when following the commands here, and following them exactly step-by-step based on the guide, I get the following:
Anyone else tried to follow the steps?
Click to expand...
Click to collapse
since it is a ninja error i suppose that you are on the wrong ubuntu version
please post a full log on the pastebin and pm me
We have moved to a new address!
https://developer.sony.com/develop/open-devices/
Now you can build the latest Android with the latest 4.4 kernel
Vendor v11 is out
https://developer.sony.com/develop/open-devices/latest-updates
jerpelea said:
Now you can build the latest Android with the latest 4.4 kernel
Click to expand...
Click to collapse
Will we see any official ota update from sony with this kernel?
The Open Devices and Official SW are built from different code base which means that the answer is NO
Regards
J
For user security dm-verity and File Based Encryption are enabled by default
Please disable them only if you are developing new features
Regards
J
All build guides are updated with the Security updates
https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
Here is the list of all known bugs. If you find bugs you can always open a ticket in the bug tracker and we will check it ASAP.
https://github.com/sonyxperiadev/bug_tracker/issues