03-01-2012 08:14 AM
339 12345 ...
tools
  1. bigsupersquid's Avatar
    How are things squid? keep us in the know it helps noob builders like me and people who google these problems.
    I'll keep posting errors and possible solutions as I run into them.
    Right now the build is still running... I'm using a 1.7GHz 2GB RAM laptop, which is compiling about 5X as fast as my last desktop. Should be testable within a couple more hours.

    for what it's worth, system/core/debuggerd/vfp.S did compile after the patch (the patch is a major improvement over commenting out 90% of the file which is what I did to get it to build the first time, which bootlooped)

    For more speed, I'll have to come up with a couple of hundred bucks to buy a newer computer somehow or find a faster one dumped on the curb like my last couple desktops.

    BobZhome is making much better progress at this point. I couldn't clone his thunderc device folder due to net connection problems, so I've gone back to poking around with the generic builds for the moment trying to get a full boot.

    I'm kind of a noob builder myself, unless you count assembly language and BASIC like 20 years ago and a little foray recently into kernel building. Anything up-to-date (C, J2ME, HTML) I'm still just piddling around.

    But, I do recognize syntax errors pretty well from that past experience. And these high-level languages are relatively easy to pick apart compared to 8-bit assembly language.

    Don't worry, I'll keep you all posted, and Asadullah, Jerry, and Bob have all been throwing out tons of useful info too! This thread has grown pretty fast considering the relative scarcity of ETA requests.


    edit: that vfp.S patch looks cleaner but did not fix the bootloop I'm getting.
    It still loops at the same point, whether armv5te-vfp or armv6k-vfp.
    Guess I'll have to take the easier way out and take a day to pull down Bob's repo after all...
    Anonymo and bdfull3r like this.
    11-27-2011 08:09 PM
  2. JerryScript's Avatar
    Cyanogen finally merged a commit Blarf made a while back for the apns-conf.xml file to include Virgin Mobile US, but the mcc and mnc are not correct, use the values from IHO or BobZhome's repo till we can submit a fix for it.

    I'm afraid to comment on the commit after my last attempt.
    bigsupersquid likes this.
    11-27-2011 08:43 PM
  3. konspiracy's Avatar
    Cyanogen finally merged a commit Blarf made a while back for the apns-conf.xml file to include Virgin Mobile US, but the mcc and mnc are not correct, use the values from IHO or BobZhome's repo till we can submit a fix for it.

    I'm afraid to comment on the commit after my last attempt.
    I hear ya. I made a comment on google + about that optimus s variant having cyanogenmod preinstalled and I said its funny that the optimus line isnt even supported by cyanogen and yet the first phone to come with it is an optimus s. I really hope they can eventually back us up.
    11-27-2011 10:29 PM
  4. pergerson6's Avatar
    I hear ya. I made a comment on google + about that optimus s variant having cyanogenmod preinstalled and I said its funny that the optimus line isnt even supported by cyanogen and yet the first phone to come with it is an optimus s. I really hope they can eventually back us up.
    We have IHO backing us up! That's good enough for me.

    Sent from my LS670 using Tapatalk
    11-27-2011 11:31 PM
  5. JerryScript's Avatar
    @BobZhome: I took a shot at building from your repo once the relatives finally left. I almost immediately got this error:
    Code:
    make: *** No rule to make target `out/target/product/thunderc/kernel', needed by `out/target/product/thunderc/boot.img'.  Stop.
    make: *** Waiting for unfinished jobs....
    I see the kernel in device/lge/thunderc, and it's in device/lge/thunderc/files/kernel/VM670 along with the modules, but I don't know if they are the same kernel images, or how to point to the proper one.
    bdfull3r likes this.
    11-28-2011 12:46 AM
  6. redhat#AC's Avatar
    if anyone wants to pay for my internetz i can set up my computer as an ubuntu server and you can build ics via remote its an i7 920 4 core 8 thread cpu overclocked to 3.2ghz 12GB of ram and 1TB hd im sure that will be enough to build ics in about an hour or two
    or i can sell it for a few hundred
    also if any one needs an extra optimus i have one of them aswell
    11-28-2011 04:07 AM
  7. BobZhome's Avatar
    The problem I'm having is the copying over.
    If you copy the kernel to 'out/target/product/thunderc/', it will build with out an more stops or errors.
    JerryScript likes this.
    11-28-2011 04:09 AM
  8. JerryScript's Avatar
    The problem I'm having is the copying over.
    If you copy the kernel to 'out/target/product/thunderc/', it will build with out an more stops or errors.
    Blarf doesn't watch this thread much, but I know he's interested, shoot him an email and I'll bet he can help with where to do the copying properly.
    11-28-2011 04:27 AM
  9. konspiracy's Avatar
    if anyone wants to pay for my internetz i can set up my computer as an ubuntu server and you can build ics via remote its an i7 920 4 core 8 thread cpu overclocked to 3.2ghz 12GB of ram and 1TB hd im sure that will be enough to build ics in about an hour or two
    or i can sell it for a few hundred
    also if any one needs an extra optimus i have one of them aswell

    I have a six core thuban at 3.7ghz and I would let them build on my computer for free.
    The fact is between the internet speeds and transfer time they would be almost better off compiling for themselves.
    11-28-2011 08:47 AM
  10. bigsupersquid's Avatar
    I got an answer about making the kernel as part of the build.
    I don't like it, because I'm supposed to download at least 1/2 GB to look at the source files referenced (which will take me until tomorrow to finish syncing, probably,) but at least it's an answer of some kind.
    Hopefully it's not just a copy of a pre-built kernel he's referring to, but even if it is it should help with the copy problem in BobZhome's ics build.
    In a nutshell, ALL_PREBUILT is a private variable of the core build
    system, and the core build system now defends itself when random
    makefiles modify that specific variable, as that causes confusion down
    the line.

    Check how the kernel is installed with PRODUCT_COPY_FILES in device/samsung/tuna

    JBQ
    I'll be asking there for alternative methods if my theory about tuna using a prebuilt kernel is correct. I won't know until I can successfully sync the stupid bloated tuna/maguro device folders in my personal copy of the repo. I deliberately took that cruft out of the manifest to give the repo a better chance of downloading over my slow connection.

    edit: oooh, nevermind my cursing! CM has the tuna and maguro devices on github, so I can just browse that junk.
    the appropriate part of device.mk:
    Code:
    ifeq ($(TARGET_PREBUILT_KERNEL),)
    LOCAL_KERNEL := device/samsung/tuna/kernel
    else
    LOCAL_KERNEL := $(TARGET_PREBUILT_KERNEL)
    endif
    Looks like it'll handle either prebuilt or build it as part of the product if I can figure out how to set TARGET_PREBUILT_KERNEL correctly. Too bad I have to request again the specific information I thought I asked for clearly in the first post there...
    bdfull3r likes this.
    11-28-2011 03:24 PM
  11. JerryScript's Avatar
    I got an answer about making the kernel as part of the build.
    I don't like it, because I'm supposed to download at least 1/2 GB to look at the source files referenced (which will take me until tomorrow to finish syncing, probably,) but at least it's an answer of some kind.
    Hopefully it's not just a copy of a pre-built kernel he's referring to, but even if it is it should help with the copy problem in BobZhome's ics build.

    I'll be asking there for alternative methods if my theory about tuna using a prebuilt kernel is correct. I won't know until I can successfully sync the stupid bloated tuna/maguro device folders in my personal copy of the repo. I deliberately took that cruft out of the manifest to give the repo a better chance of downloading over my slow connection.

    edit: oooh, nevermind my cursing! CM has the tuna and maguro devices on github, so I can just browse that junk.
    the appropriate part of device.mk:
    Code:
    ifeq ($(TARGET_PREBUILT_KERNEL),)
    LOCAL_KERNEL := device/samsung/tuna/kernel
    else
    LOCAL_KERNEL := $(TARGET_PREBUILT_KERNEL)
    endif
    Looks like it'll handle either prebuilt or build it as part of the product if I can figure out how to set TARGET_PREBUILT_KERNEL correctly. Too bad I have to request again the specific information I thought I asked for clearly in the first post there...
    There is a device folder in /build/tools that has some templates to follow that I think may help, though I haven't tested yet. The BoardConfig.mk.template shows that you can add the following to /build/target/board/<generic_armv5>/BoardConfig.mk (or whichever you are using):
    Code:
    TARGET_PREBUILT_KERNEL := device/__MANUFACTURER__/__DEVICE__/kernel
    bigsupersquid likes this.
    11-28-2011 04:44 PM
  12. bigsupersquid's Avatar
    There is a device folder in /build/tools that has some templates to follow that I think may help, though I haven't tested yet. The BoardConfig.mk.template shows that you can add the following to /build/target/board/<generic_armv5>/BoardConfig.mk (or whichever you are using):
    Code:
    TARGET_PREBUILT_KERNEL := device/__MANUFACTURER__/__DEVICE__/kernel
    funny thing is that they put the kernel copy command in device.mk for tuna.
    maybe I'll fiddle with TARGET_PREBUILT_KERNEL := device/__MANUFACTURER__/__DEVICE__/kernel and try to get it to build.
    As that line stands it looks like it's just set to copy a prebuilt kernel, like they did with tuna... or it'd be
    TARGET_PREBUILT_KERNEL := kernel
    since that's where the kernel source is supposed to live, not in the device folder. I'm gonna try that real quick and see if it errors.
    thanks much for the pointer to the templates and the code there.

    edit: a quick response from JBQ this time:
    Ah, sorry I missed that part. There's no mechanism in the build system
    to build the kernel "live" (it's not portable enough and not scalable
    enough), and all Android work at Google has always been done with
    prebuilt kernels (or at least as far as I can remember).

    You might need to add support for what you're trying to do directly in
    the core build system.

    JBQ
    So what I want to do is unsupported, like my choice of operating system
    I bet it can work somehow though. I tried TARGET_PREBUILT_KERNEL := kernel in BoardConfig.mk, and, while it didn't crash with an error, it didn't try to build the kernel either. Usually it does that first, so I'm guessing it won't work like I want without some major tweaking. Ah, well.
    Billzilla, bdfull3r and mustafu like this.
    11-28-2011 04:59 PM
  13. BobZhome's Avatar
    touchscreen and accelerometer fixes for ics[/URL] (thanks vienti) into the kernel so it needs to be rebuilt anyway.
    edit: I submitted it to Android Building | Google Groups to see if someone knows of a solution, since ICS is too new for me to get many relevant search results to oddball problems. First post there, hopefully I'm not eaten alive for overlooking something stupid!
    I built a kernel with that touchscreen and accelerometer fix last night. I just tested it and I could get off the lock screen, the IHO kernel runs better.
    ---------------------------------------------------------------------------
    EDIT: I have 'TARGET_PREBUILT_KERNEL := device/lge/thunderc/files/kernel/VM670/kernel' in BoardConfig.mk...line 79 here: https://github.com/BobZhome/android_...BoardConfig.mk
    I also have
    ifeq ($(TARGET_PREBUILT_KERNEL),)
    LOCAL_KERNEL := device/lge/thunderc/kernel
    else
    LOCAL_KERNEL := $(TARGET_PREBUILT_KERNEL)
    endif

    # These are the hardware-specific features

    PRODUCT_COPY_FILES := \
    $(LOCAL_KERNEL):kernel
    in device.mk lines 21-30 here: https://github.com/BobZhome/android_.../ics/device.mk
    I purposely used no kernel folder here just in case it was messing things up.
    11-28-2011 05:38 PM
  14. BobZhome's Avatar
    Go sign...at least I see copied files being rejected:
    Code:
    Checking build tools versions...
    build/core/Makefile:25: warning: overriding commands for target `out/target/product/thunderc/system/lib/hw/gralloc.default.so'
    build/core/base_rules.mk:523: warning: ignoring old commands for target `out/target/product/thunderc/system/lib/hw/gralloc.default.so'
    build/core/Makefile:25: warning: overriding commands for target `out/target/product/thunderc/system/lib/libril.so'
    build/core/base_rules.mk:523: warning: ignoring old commands for target `out/target/product/thunderc/system/lib/libril.so'
    build/core/Makefile:25: warning: overriding commands for target `out/target/product/thunderc/system/bin/rild'
    build/core/base_rules.mk:523: warning: ignoring old commands for target `out/target/product/thunderc/system/bin/rild'
    bdfull3r likes this.
    11-28-2011 07:12 PM
  15. JerryScript's Avatar
    Go sign...at least I see copied files being rejected:
    Code:
    Checking build tools versions...
    build/core/Makefile:25: warning: overriding commands for target `out/target/product/thunderc/system/lib/hw/gralloc.default.so'
    build/core/base_rules.mk:523: warning: ignoring old commands for target `out/target/product/thunderc/system/lib/hw/gralloc.default.so'
    build/core/Makefile:25: warning: overriding commands for target `out/target/product/thunderc/system/lib/libril.so'
    build/core/base_rules.mk:523: warning: ignoring old commands for target `out/target/product/thunderc/system/lib/libril.so'
    build/core/Makefile:25: warning: overriding commands for target `out/target/product/thunderc/system/bin/rild'
    build/core/base_rules.mk:523: warning: ignoring old commands for target `out/target/product/thunderc/system/bin/rild'
    So copying those to the appropriate out folders should work for now, right?
    mustafu likes this.
    11-28-2011 08:18 PM
  16. sellers86's Avatar
    If you guys need any help I can attempt. This is the whole reason I wanted to learn to build from source in the first place is so I could build and ICS ROM. I can test or even attempt to build.
    11-28-2011 10:48 PM
  17. BobZhome's Avatar
    So copying those to the appropriate out folders should work for now, right?
    Yep, did that...but now that's it's copying my files, I'm getting stops. ICS does not like the overlays!

    If you guys need any help I can attempt. This is the whole reason I wanted to learn to build from source in the first place is so I could build and ICS ROM. I can test or even attempt to build.
    I don't hide anything, your welcomed to clone my git.
    mustafu likes this.
    11-29-2011 03:50 AM
  18. bigsupersquid's Avatar
    @Bob:
    I had to remove most of the overlays to get GB or ICS to compile with the thunderc folders at all.
    'course, I wasn't using any CM source in the repo at the time, so I was kind of hoping using your manifest would take care of that...
    I removed all but framesworks/base/core/res/res/xml/eri.xml and packages/apps/MMS/res/xml/mms_config.xml to get pure AOSP to build without griping about the overlays.
    you could also manually edit out the parts that error from each file in the overlay as it stops compiling, but I got really tired of that process and went for overkill, leaving in the 2 files I was pretty sure were needed. Probably don't need to wipe out the whole set of files... it will at least compile if you do though.

    On day 3 of trying to sync your manifest.... my connection sucks!
    and repo sucks too, since it downloads hundreds of MB from a single project, then stops downloading without showing any kind of error and just hangs there for hours, has to be restarted, and ignores all the data it already downloaded from that project and begins it again from point zero.

    edit: woo! finally finished getting the repo. Can't imagine how much longer it would've taken if I hadn't removed device/tuna and device/maguro from the manifest (tuna's over 500MB by itself, haven't tried to download that puppy yet.)
    BTW, I also removed the NFC app from the manifest, since the OV doesn't have the capability to use it.
    bdfull3r and mustafu like this.
    11-29-2011 07:47 AM
  19. BobZhome's Avatar
    I corrected one overlay last night and push it to git. This morning before leaving for the day, I corrected another... but did not push it because I was pressed for time. I'll work on correcting them all later, when I get home.

    Sent from my LG-VM670 using Tapatalk
    11-29-2011 09:16 AM
  20. tony5593's Avatar
    Hey, how can i try this? If its even possible? & What program do you guys use to mess with code? Id really like to learn.

    Sent from my LG-VM670 using Tapatalk
    11-29-2011 08:24 PM
  21. JerryScript's Avatar
    Read the building your own rom thread, details on building are in there. Then come back here and join us stumbling around in the dark
    mustafu likes this.
    11-29-2011 09:59 PM
  22. tony5593's Avatar
    Okay awesome! Thanks. & Sorry for kinda getting off topic.

    Sent from my LG-VM670 using Tapatalk
    11-29-2011 10:09 PM
  23. JerryScript's Avatar
    CM has an ICS daily driver ready for at least one phone:
    Unofficial Android Build CyanogenMod Gets An Ice Cream Sandwich
    mustafu likes this.
    11-30-2011 04:07 AM
  24. bdfull3r's Avatar
    CM has an ICS daily driver ready for at least one phone:
    Unofficial Android Build CyanogenMod Gets An Ice Cream Sandwich

    I like the article and it points to the relatively stable build on the Nexus S that i am almost positive will jump start a lot of hummingbird phones.

    My problem after reading this article is its constant reliance on calling unofficial Android insecure.
    And what baffles me is the example in there is a phone with 1.4(i think it was a type for 1.5) but can run 2.3.7.

    Donut to Eclair to Froyo to Gingerbread. ONe constant inprovement is secuity. Every new version of Android patches known security flaws and some of them very dangerous flaws. If i can stay current AND secure, damn right i am going to root. It was my primary reason for rooting my OV

    Sorry for getting away from topic but i felt like saying it
    11-30-2011 04:28 PM
  25. thewraith420's Avatar
    Just thought this needed a bump back to the top :-) loving the IHO builds and can't wait to see what you can come up with for ICS. Keep up the great work.

    Sent from my LG-VM670 using BACKside IHO 1122
    12-02-2011 11:58 AM
339 12345 ...
LINK TO POST COPIED TO CLIPBOARD