Building your own ROM

Code:
make: *** [out/target/product/thunderc/obj/EXECUTABLES/dnsmasq_intermediates/log.o] Error 1
make: *** Waiting for unfinished jobs....


Not sure what to make of this, is this what you are getting Pbailey212?


Code:
make: *** [out/target/product/thunderc/obj/EXECUTABLES/dnsmasq_intermediates/log.o] Error 1
make: *** Waiting for unfinished jobs....

Not sure what to make of this, is this what you are getting Pbailey212?

Im pretty sure it is, I'm not home so i can't double check. Did you fallow all of Jerry's steps? Wasn't dnmmasq the line he said to comment out? I blame Jerry
 
...Did you fallow all of Jerry's steps? Wasn't dnmmasq the line he said to comment out?...
Yep, that's the one, will compile fine if you either comment that out or grab the commit that fixes it.
...I blame Jerry
jesussaysaskgoogle.jpg
 
Hmm, I commented it out, but I will try the other options.

Don't expect any of us to have all the answers. If one of us knew everything asked, I would have to wonder about them.
 
I had been waiting for the slightest excuse to use that image since I saw it the other day. ;)

Have you tried syncing with bob's repository?
 
Tip of the week:
You hate doing lunch, then try brunch:
Code:
. build/envsetup.sh && brunch thunderc_VM670
You may find that it builds a tiny bit faster ;)
Bob

Thanks, Bob. I just did a benchmark on my Linux system (Ubuntu 11.04 x64, Phenom II X4 @3.5GHz, 4GB RAM). Before each test, I started a new terminal, sourced build/envsetup.sh, and did a make clobber. The build commands and times are given below.

lunch 2 && make -j4 bacon

real 24m13.467s
user 71m29.880s
sys 3m48.490s
________________________

brunch thunderc_VM670

real 24m43.931s
user 72m0.540s
sys 3m42.920s
 
Last edited:
Lol, you saved some time in typing, selecting, and waiting ;)

Sent from my LG-VM670 using Tapatalk
 
I have seen that you have added smartass2 in the kernel. Will you release them soon or need more testing? I can help if you need testing, just tell me what files to grab from the repo. You have v2, v2.1, V3, V3a, and another without any version.
 
Last edited:
I have seen that you have added smartass2 in the kernel. Will you release them soon or need more testing? I can help if you need testing, just tell me what files to grab from the repo. You have v2, v2.1, V3, V3a, and another without any version.
The kernel with no version number is the newest, which is 3.1
You can grab it from my repo, if you want. I'm about to test it....if everything is ok, I'll post it to my LG Public folder in a little bit.
I wanted to test it first...I didn't like the fact that smartass wasn't working in v3a.
Bob
 
  • Like
Reactions: mrg666
The kernel with no version number is the newest, which is 3.1
You can grab it from my repo, if you want. I'm about to test it....if everything is ok, I'll post it to my LG Public folder in a little bit.
I wanted to test it first...I didn't like the fact that smartass wasn't working in v3a.
Bob

Thanks, Bob. I am on it. Smartass in V3a was not a big deal. Nobody complained; that includes me.

Edit: Your v3.1 kernel works fine. I have tested the two new governors (SmartassV2 and InteractiveX). They work as expected. I have uploaded the ROM to Wiki. Thanks again.
 
Last edited:
Tip of the week:
Bookmark this site: $ cheat git
The best...most complete list of git cheats.
Bob

that's really nice.
now if I can just find a way to make repo pick up where it left off in the middle of a huge project like platform/prebuilt when it times out and won't reconnect, or my connection drops... I hate redownloading 900MB of data just because repo has a selective memory after it crashes.

there's a small repo/git cheatsheet near the bottom of this link.
 
Last edited:
that's really nice.
now if I can just find a way to make repo pick up where it left off in the middle of a huge project like platform/prebuilt when it times out and won't reconnect, or my connection drops... I hate redownloading 900MB of data just because repo has a selective memory after it crashes.

there's a small repo/git cheatsheet near the bottom of this link.
900MB? Maybe the first set up, but repo sync is very fast...especially if you edit out all the phone you don't need.
Forking and mantaining 101:
Take my android folder located here: https://github.com/BobZhome/android/blob/gingerbread/default.xml and fork it.
It will show up on your github here: https://github.com/bigsupersquid
With terminal on your system type: git clone git@github.com:bigsupersquid/android.git
It will download a android folder.
Edit the default.xml to your liking.
With terminal in that android folder type: git add .
then: git commit -m "what ever you want to say goes here"
then: git push
Your edited default.xml will be on your github :D

Now setting up your system to use that default.xml file of yours:
With terminal in your ~/android/system folder type: init -u git://github.com/bigsupersquid/android.git -b gingerbread --repo-url=git://github.com/android/tools_repo.git
Then type: repo sync -f

Now your repo sync's should be a lot faster :cool:
You probably knew this anyway...it was for the newbies...:-*

Oh and by the way, this post assume you have some basic knowledge...example is changing directories ;)

Bob
 
  • Like
Reactions: bigsupersquid
Yeah, the initial sync is what I was talking about.
I've piddled with the aosp, caf, and now iho repos. I've tried several variants of grabbing iho, so the time and bandwidth have been adding up.
Seems like I keep syncing in the middle of commits or something, I keep getting build errors in different CM projects.
Appreciate the pointers. I'll definitely give your method a shot.
I did find one blog which said
If you have already downloaded old source code (for example, android-2.2_r1.1), you can reduce amount of newly download size to use old repository. so you download only the difference.
and then gives instructions to copy over the old stuff.
It definitely cuts the initial sync time, but I'm just not sure if it's carrying some kind of glitches into the new folder or not... so I'm trying full, clean sync again.
I also noticed that
Code:
repo sync -j32
running repo with some obscene number of threads seems to speed up the resume on a broken initial sync.
I hadn't tried the -f option, I'll definitely test this out.
 
Yes, Blarf pulled in all the commits from CM7.1 the other day, and merged a pull request I added to get the repo working again. You should have no problems now doing a clean repo sync with IHO. ;)
 
  • Like
Reactions: mrg666

Latest posts

Trending Posts

Forum statistics

Threads
956,596
Messages
6,969,041
Members
3,163,582
Latest member
shy_panther