tdm
Well-known member
- Apr 11, 2011
- 1,409
- 3,596
- 0
Ok, fixed that error by placing parcel.o fromt he old build folders
Never do this. You will likely end up with a broken ROM that crashes and/or misbehaves.
Ok, fixed that error by placing parcel.o fromt he old build folders
Never do this. You will likely end up with a broken ROM that crashes and/or misbehaves.
Ok. I'll start afresh. How do I fix that error? and thanks much for pointing that out.![]()
See if the issue persists with a clean build.
And BTW, for a clean build, you just do "rm -rf out".
frameworks/base/libs/binder/Parcel.cpp:488: error: prototype for 'bool android::Parcel::enforceInterface(const android::String16&) const' does not match any in class 'android::Parcel'
frameworks/base/include/binder/Parcel.h:77: error: candidate is: bool android::Parcel::enforceInterface(const android::String16&, android::IPCThreadState*) const
make: *** [out/target/product/thunderc/obj/SHARED_LIBRARIES/libbinder_intermediates/Parcel.o] Error 1
rm -rf out deletes the out directory right? Doesn't make clobber do the same?
Did 'rm -rf out' and then make bacon. Stopped at the exact same place like before.
Code:frameworks/base/libs/binder/Parcel.cpp:488: error: prototype for 'bool android::Parcel::enforceInterface(const android::String16&) const' does not match any in class 'android::Parcel' frameworks/base/include/binder/Parcel.h:77: error: candidate is: bool android::Parcel::enforceInterface(const android::String16&, android::IPCThreadState*) const make: *** [out/target/product/thunderc/obj/SHARED_LIBRARIES/libbinder_intermediates/Parcel.o] Error 1
Remove _INTERNAL_BINDER_PARCEL_ from your global cflags in BoardConfig.mk.
Looked at this closer today. It looks to be a clever hack for backward compatibility. But it relies on _INTERNAL_BINDER_PARCEL_ only being set internally, not globally. For some reason the BoardConfig.mk that I snagged from lupohirp has this set as a global cflag and that's what is causing the issue. So here's the real fix, in my device/lge/thunderc/BoardConfig.mk:
Code:-COMMON_GLOBAL_CFLAGS += -D_INTERNAL_BINDER_PARCEL_ -DUSE_LGE_ALS_DUMMY +COMMON_GLOBAL_CFLAGS += -DUSE_LGE_ALS_DUMMY
Sorry to be a total noob but are you guys doing this from your guys phone? If so wat app is it? Is it just terminal emulator?Now I'm getting this: Click to view quoted image
Its making me feel like a noob.....
(Sorry if my posting screenshots of errors gets annoying. I'm not smart enough to fix them easily)
Sorry to be a total noob but are you guys doing this from your guys phone? If so wat app is it? Is it just terminal emulator?
Sent from my VM670 using Tapatalk 2 Beta-4
Sorry to be a total noob but are you guys doing this from your guys phone? If so wat app is it? Is it just terminal emulator?
Sent from my VM670 using Tapatalk 2 Beta-4
gannon5197@icsbox:~/android/CNA$ make -j4 CNA_RELEASE=true
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.0.3
TARGET_PRODUCT=cna_thunderc
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv6-vfp
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=IML74K
============================================
build/core/base_rules.mk:78: *** Module name: busybox
build/core/base_rules.mk:79: *** Makefile location: external/busybox
build/core/base_rules.mk:80: *
build/core/base_rules.mk:81: * Each module must use a LOCAL_MODULE_TAGS in its
build/core/base_rules.mk:82: * Android.mk. Possible tags declared by a module:
build/core/base_rules.mk:83: *
build/core/base_rules.mk:84: * optional, debug, eng, tests, samples
build/core/base_rules.mk:85: *
build/core/base_rules.mk:86: * If the module is expected to be in all builds
build/core/base_rules.mk:87: * of a product, then it should use the
build/core/base_rules.mk:88: * "optional" tag:
build/core/base_rules.mk:89: *
build/core/base_rules.mk:90: * Add "LOCAL_MODULE_TAGS := optional" in the
build/core/base_rules.mk:91: * Android.mk for the affected module, and add
build/core/base_rules.mk:92: * the LOCAL_MODULE value for that component
build/core/base_rules.mk:93: * into the PRODUCT_PACKAGES section of product
build/core/base_rules.mk:94: * makefile(s) where it's necessary, if
build/core/base_rules.mk:95: * appropriate.
build/core/base_rules.mk:96: *
build/core/base_rules.mk:97: * If the component should be in EVERY build of ALL
build/core/base_rules.mk:98: * products, then add its LOCAL_MODULE value to the
build/core/base_rules.mk:99: * PRODUCT_PACKAGES section of
build/core/base_rules.mk:100: * build/target/product/core.mk
build/core/base_rules.mk:101: *
build/core/base_rules.mk:102: *** user tag detected on new module - user tags are only supported on legacy modules. Stop.
gannon5197@icsbox:~/android/CNA$
Oh no, it would take weeks to compile on a phone and it's not supported anyway. But I think at least one person is connecting to the build server with Android. I'd guess connectbot on a tablet but who knows.
Oh no, it would take weeks to compile on a phone and it's not supported anyway. But I think at least one person is connecting to the build server with Android. I'd guess connectbot on a tablet but who knows.
Sorry to be a total noob but are you guys doing this from your guys phone? If so wat app is it? Is it just terminal emulator?
Sent from my VM670 using Tapatalk 2 Beta-4
There are two computers in this house hooked up to the one TV. The littler kids like to kick me off and watch smosh on YouTube for hours. So I use connectbot on my phone for SSH. I wish I had a login on the build server....
I think Better Terminal Emulator does SSH also, but it's a paid app.
Sent from my LG-VM670 using Tapatalk