droidmyme
Well-known member
Is it just me, or is the Wiki link in the OP broken?
Yes, the link in OP is broken, can we get this fixed?
Is it just me, or is the Wiki link in the OP broken?
I can post them for download on Monday if you want.
Yes, the link in OP is broken, can we get this fixed?
The OP was made by Blarf, and he doesn't participate in the forums any longer. so no we cannot change his link.
So I've finally had time to start up on the ROM building again, and I keep running into the stupidest problem. I forked the "android" and "android_vendor_cyanogen" repos and kept the rest pointing to IHO in the default.xml.
I changed PRODUCT_RELEASE_NAME in products/cyanogen_thunderc.mk from "IHO" to "something15525" and went to go make a build....it built fine, but the finished product zip is called:
update-CM-7.2.0-RC1-thunderc_LS670-KANG-signed.zip
shouldn't it be:
update-CM-7.2.0-RC1-something15525-KANG-signed.zip?
One more thing:
When I flashed it, I went to check the mod version, and it said:
CyanogenMod-7.2.0-RC1-thunderc_LS670-KANG
Shouldn't the "thunderc_LS670" be "something15525"?
This is getting me really frustrated that I can't get past this simple problem and I was hoping someone could tell me what I'm doing wrong.
Here's the change: https://github.com/something15525/a...mmit/e186ec8da6349b88df1f5dc4f3329530a688c7ce
The OP was made by Blarf, and he doesn't participate in the forums any longer. so no we cannot change his link.
Did this ever get answered?
line 13
CMVERSION := CyanogenMod-$(PRODUCT_VERSION_MAJOR).$(PRODUCT_VERSION_MINOR).$(PRODUCT_VERSION_MAINTENANCE)$(PRODUCT_VERSION_DEVICE_SPECIFIC)-$(CM_BUILD)-KANG
I think where you need to change on yours is
https://github.com/something15525/a.../blob/gingerbread/products/common_versions.mk
Code:line 13 CMVERSION := CyanogenMod-$(PRODUCT_VERSION_MAJOR).$(PRODUCT_VERSION_MINOR).$(PRODUCT_VERSION_MAINTENANCE)$(PRODUCT_VERSION_DEVICE_SPECIFIC)-$(CM_BUILD)-KANG
You should be able to manually change KANG to your name or add to the line $(PRODUCT_RELEASE_NAME)
I'm not using the latest IHO rearrangement yet, so I'm not too sure. Mine in in the cyanogen_thunderc.mk file.
libdl (out/target/product/thunderc_VM670/obj/SHARED_LIBRARIES/libdl_intermediates/LINKED/libdl.so)
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.6.1/libstdc++.so when searching for -lstdc++
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.6.1/libstdc++.a when searching for -lstdc++
/usr/bin/ld: cannot find -lstdc++
collect2: ld returned 1 exit status
make: *** [out/host/linux-x86/obj/EXECUTABLES/mkbootfs_intermediates/mkbootfs] Error 1
make: *** Waiting for unfinished jobs....
Hey Jerry or anybody else, can you help me? It seems as if I always screw myself when doing this, and I don't want to anymore. Lol.
When I go git push, it always gives me this error:
gannon5197@icsbox:~/android/cna/device/lge/thunderc$ git push origin
Enter passphrase for key '/home/gannon5197/.ssh/id_rsa':
To git@github.com:gannon5197/android_device_lge_thunderc.git
! [rejected] ics -> ics (non-fast-forward)
error: failed to push some refs to 'git@github.com:gannon5197/android_device_lge_thunderc.git'
To prevent you from losing history, non-fast-forward updates were rejected
Merge the remote changes before pushing again. See the 'Note about
fast-forwards' section of 'git push --help' for details.
gannon5197@icsbox:~/android/cna/device/lge/thunderc$
Can there be any negative effect to forcing it? I don't want to mess anything up.If you don't mind forcing the push. It will overwrite your remote commits. git push -f origin
Alright I'll get right on that. Thanks!Your local and remote are out of sync. I don't know your workflow so I can't say how to avoid this in the future. However, to fix it, do this:
1. Backup the whole directory (eg. using tar) so you don't lose anything.
2. Delete your .git directory.
3. Backup the remainder (your working files) somewhere.
4. Nuke the directory.
5. Pull a fresh copy from github.
6. Checkout the ics branch.
7. Delete everything except the .git directory.
8. Restore your working directory.
Now you should be able to checkin and push.
One more thing. Since I've made changes to the files inside in order for it to build correctly, should I be careful when I git pull? Like should I pull in commit by commit or just run a "git pull cna mod-4.0.4" by example?