Hi, I'm VisualTech48 and i own a Galaxy S Plus (I9001).
Our great Developers [Arco98, Ivendor, Doomsday98, Oisis, etc.] are developing ICS Roms and trying to make Jelly Bean too but we are missing a key element of this game.
It's the 3.0.x Kernel. We really need a good coder.
If anyone knows, or can help us code this kernel we are Ready to donate, and help by giving logs if even needed.
If we donate to someone, he/she must:
Help our devs with codeing
Give us a booting kernel
We have done allready a part of the project but we need help with codeing, that is why I even started this thread.
What has oisis done:
Added board-ariesve.c here:
arch/arm/mach-msm/board-ariesve.c
Included Ariesve board to Kconfig and Makefile.
Added missing files:
include/linux/fsa9480.h
arch/arm/mach-msm/include/mach/msm_reqs.h
Click to expand...
Click to collapse
Compilation error:
Code:
arch/arm/mach-msm/board-ariesve.c: In function 'pm8058_gpios_init':
arch/arm/mach-msm/board-ariesve.c:329: error: variable 'sdcc_det' has initializer but incomplete type
arch/arm/mach-msm/board-ariesve.c:330: error: unknown field 'direction' specified in initializer
arch/arm/mach-msm/board-ariesve.c:330: warning: excess elements in struct initializer
error, forbidden warning: board-ariesve.c:330
make[1]: *** [arch/arm/mach-msm/board-ariesve.o] Error 1
What needs to be done:
include and port file from 2.6.35.X - arch/arm/mach-msm/board-ariesve.c
include/find missing drivers for i9001
Click to expand...
Click to collapse
We whould really apriciate if someone can help us because this kernel can open a whole new page for our phone.
Why did i remade a new thread? Because i think we have more chances of reply then in the I9000 Forum.
Thank you for reading this, VisualTech48
Original Thread: http://forum.xda-developers.com/showthread.php?t=1742976
Hello, i am trying to build a kernel using the linaro toolchain from here http://is.gd/Au5yrh . Kernel builds fine with gcc-4.4.3 from cyanogenmod but with linaro all the warnings are treated as errors like the one below.
Code:
arch/arm/mm/alignment.c: In function 'do_alignment':
arch/arm/mm/alignment.c:298:15: warning: 'offset.un' may be used uninitialized in this function [-Wuninitialized]
error, forbidden warning: alignment.c:298
make[1]: *** [arch/arm/mm/alignment.o] Error 1
I know one way to solve this is to actually edit the code and fix this warning but since this works and i might end up braking something i am looking maybe for an easier solution.
I have tried editing the Makefile CFLAGS removing -Werror but yet no luck.
The kernel tree is this if it helps https://github.com/ezeteze/kernel_huawei
Thanks in advance!
ezet said:
Hello, i am trying to build a kernel using the linaro toolchain from here http://is.gd/Au5yrh . Kernel builds fine with gcc-4.4.3 from cyanogenmod but with linaro all the warnings are treated as errors like the one below.
Code:
arch/arm/mm/alignment.c: In function 'do_alignment':
arch/arm/mm/alignment.c:298:15: warning: 'offset.un' may be used uninitialized in this function [-Wuninitialized]
error, forbidden warning: alignment.c:298
make[1]: *** [arch/arm/mm/alignment.o] Error 1
I know one way to solve this is to actually edit the code and fix this warning but since this works and i might end up braking something i am looking maybe for an easier solution.
I have tried editing the Makefile CFLAGS removing -Werror but yet no luck.
The kernel tree is this if it helps https://github.com/ezeteze/kernel_huawei
Thanks in advance!
Click to expand...
Click to collapse
edit and find "offset.un" and add = NULL; at the end
so code looks like this.. offset.un = NULL;
go ahead and try it..
OR
offset.un = 0;
Update: I have since found a solution to this error... I was using "make -j9 otapackage" and doing "make" instead seems to prevent the error.
===
Old post:
I am new to AOSP building... I first synced the master branch and built it, no issues, then I synced 4.2.1_r1.2 and built that (both for toro), no issues. Then I decided to sync many recent branches going back to 4.0.4... I decided to try and build 4.1.1_r5 since that seems to be what the factory image uses. I recieved the following error:
Import includes file: out/target/product/toro/obj/EXECUTABLES/check_prereq_intermediates/import_includes
Export includes file: build/tools/check_prereq/Android.mk -- out/target/product/toro/obj/EXECUTABLES/check_prereq_intermediates/export_includes
Export includes file: device/samsung/tuna/recovery/Android.mk -- out/target/product/toro/obj/STATIC_LIBRARIES/librecovery_updater_tuna_intermediates/export_includes
Export includes file: device/samsung/toro/recovery/Android.mk -- out/target/product/toro/obj/STATIC_LIBRARIES/librecovery_updater_toro_intermediates/export_includes
make: *** No rule to make target `out/target/product/toro/obj/PACKAGING/updater_extensions_intermediates/register.inc.list', needed by `out/target/product/toro/obj/PACKAGING/updater_extensions_intermediates/register.inc'. Stop.
make: *** Waiting for unfinished jobs....
Export includes file: bootable/recovery/edify/Android.mk -- out/target/product/toro/obj/STATIC_LIBRARIES/libedify_intermediates/export_includes
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
I'm not exactly sure why this happened, any hints anyone can offer will be greatly appreciated. First I had an error regarding some vender proprietary file from the master branch, so I deleted it and re-extracted the 4.1.1 proprietary binaries. Of course I am compiling jro03o while the binaries are jro03h. Maybe I should try it with jro 03r binaries?
I was thinking maybe if I could "unsync" all other aosp branches other than the one I want to build on (4.1.1_r5) that might fix the error due to some mix-matching of files between syncs... Is it possible to "unsync" from aosp branches?
I re-extracted the most recent binaries for 4.2.1 and synced back to the master branch and am rebuilding that one. So far no errors, but won't know until it finishes in an hour or so.
bump...
Since this, I have successfully built and flashed 4.2.1_r1.2, however, now I am trying to syn 4.1.1_r6.1 and getting this same error again. Any ideas?
I decided to try just a simple "make" with no multi-threading to see if that might help, and it definitely created the "out/target/product/toro/obj/PACKAGING/updater_extensions_intermediates/register.inc.list" file.
Any idea why this might happen when using "make -j9 otapackage" as opposed "make"? Is it possible that doing a single-threaded build at first is necessary, then multi-threaded builds after that work. When I first compiled the master branch, I did a single-thread build, and may have done single threaded at first with 4.2.1_r1.2, I can't exactly recall how many single-thread builds I did before I learned about "-j#" option... which VASTLY speeds up my builds to an hour give or take!
Thought I'd start up a general thread where we can come to ask and answer general android building questions. I've been guilty myself of high jacking threads for questions and answering questions regarding porting, compiling, building, etc. Figured I'd try to start up a general thread for just that topic.
I'll start. Having some issues with external/jpeg.
Code:
external/jpeg/jddctmgr.c:350: error: undefined reference to 'jpeg_idct_islow'
external/jpeg/jddctmgr.c:340: error: undefined reference to 'jpeg_idct_ifast'
Have never seen that error before, I'm comparing it to other ROMs that I've built and the file is exactly the same. Not sure what else is linked to it.
@danjull Did you ever find the solution to this? How do you go about troubleshooting build errors (in general)? Do you usually look at what other files that file calls for or so you just kind of stumble through the while source looking for clues?
Sent from my Droid DNA using Tapatalk Pro
jamiethemorris said:
@danjull Did you ever find the solution to this? How do you go about troubleshooting build errors (in general)? Do you usually look at what other files that file calls for or so you just kind of stumble through the while source looking for clues?
Sent from my Droid DNA using Tapatalk Pro
Click to expand...
Click to collapse
I haven't yet.
It's a mix. Sometimes it's luck, sometimes it's clear enough so you can just follow the paths. I usually compare the problem source file to CM or another source I know works. Look at commits that happen after a known good build.
danjull said:
I haven't yet.
It's a mix. Sometimes it's luck, sometimes it's clear enough so you can just follow the paths. I usually compare the problem source file to CM or another source I know works. Look at commits that happen after a known good build.
Click to expand...
Click to collapse
Okay, cool. That's pretty much what I've been doing. I've also been doing diff -r between the cm11 source and the rom I'm building for folders that I think may be problematic and printing it to a file. So if you have the cm11 source locally you could try using that for external/jpeg or just external. I tried meld for this sort of thing too, but it didn't seem to be to helpful when it comes to entire directories.
Sent from my Droid DNA using Tapatalk Pro
isnt that gcc related as in the variable isnt defined as used?
figured i should post somewhere where i can find other devs(rather than the omni thread lol)
i got these errors today while building slimkat and after searching every line of code in the whole source, it was only reference once and that was the line that through the error
it makes it more difficult because this is the out/ folder so i really cant compare to CM11:
Code:
/home/zach/android.SlimKat/system/out/target/product/dlx/obj/GYP/shared_intermediates/blink/bindings/V8SVGAElement.cpp:71: error: undefined reference to 'WebCore::SVGAElement::svgTarget()'
/home/zach/android.SlimKat/system/out/target/product/dlx/obj/GYP/shared_intermediates/blink/bindings/V8SVGAElement.cpp:99: error: undefined reference to 'WebCore::SVGAElement::href()'
/home/zach/android.SlimKat/system/out/target/product/dlx/obj/GYP/shared_intermediates/blink/bindings/V8SVGAElement.cpp:85: error: undefined reference to 'WebCore::SVGAElement::externalResourcesRequired()'
/home/zach/android.SlimKat/system/out/target/product/dlx/obj/STATIC_LIBRARIES/third_party_WebKit_Source_core_webcore_derived_gyp_intermediates/SVGElementFactory.cpp:134: error: undefined reference to 'WebCore::SVGAElement::create(WebCore::QualifiedName const&, WebCore::Document*)'
i havent had any success with this
EDIT: nuketown 2025 population slimkat (da fuq did i just say?)
anyways resyncing the repos tonight, maybe it will be better to just start over
EDIT: nuking solves all problems
I'm trying to build tripndroid, I ran into a few other errors that I fixed already, but I'm hitting this now
Code:
In file included from frameworks/av/services/audioflinger/Tracks.cpp:32:0:
frameworks/av/services/audioflinger/AudioFlinger.h:518:5: error: expected class-name before '{' token
In file included from frameworks/av/services/audioflinger/Effects.cpp:30:0:
frameworks/av/services/audioflinger/AudioFlinger.h:518:5: error: expected class-name before '{' token
frameworks/av/services/audioflinger/Effects.cpp: In member function 'android::sp<android::AudioFlinger::EffectModule> android::AudioFlinger::EffectChain::getEffectFromIndex_l(int)':
frameworks/av/services/audioflinger/Effects.cpp:1343:40: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
make: *** [/run/media/jamiethemorris/LinuxExternal/android/tripndroid_kk/out/target/product/dlx/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/Tracks.o] Error 1
make: *** Waiting for unfinished jobs....
make: *** [/run/media/jamiethemorris/LinuxExternal/android/tripndroid_kk/out/target/product/dlx/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/Effects.o] Error 1
In file included from frameworks/av/media/mediaserver/main_mediaserver.cpp:32:0:
frameworks/av/services/audioflinger/AudioFlinger.h:518:5: error: expected class-name before '{' token
make: *** [/run/media/jamiethemorris/LinuxExternal/android/tripndroid_kk/out/target/product/dlx/obj/EXECUTABLES/mediaserver_intermediates/main_mediaserver.o] Error 1
In file included from frameworks/av/services/audioflinger/AudioFlinger.cpp:46:0:
frameworks/av/services/audioflinger/AudioFlinger.h:518:5: error: expected class-name before '{' token
In file included from frameworks/av/services/audioflinger/AudioFlinger.cpp:46:0:
frameworks/av/services/audioflinger/AudioFlinger.h: In constructor 'android::AudioFlinger::AudioFlinger()':
frameworks/av/services/audioflinger/AudioFlinger.h:833:13: warning: 'android::AudioFlinger::mGlobalEffectEnableTime' will be initialized after [-Wreorder]
In file included from frameworks/av/services/audioflinger/AudioFlinger.cpp:46:0:
frameworks/av/services/audioflinger/AudioFlinger.h:779:31: warning: 'volatile bool android::AudioFlinger::mAllChainsLocked' [-Wreorder]
frameworks/av/services/audioflinger/AudioFlinger.cpp:146:1: warning: when initialized here [-Wreorder]
frameworks/av/services/audioflinger/AudioFlinger.cpp: In member function 'virtual android::sp<android::IDirectTrack> android::AudioFlinger::createDirectTrack(pid_t, uint32_t, audio_channel_mask_t, audio_io_handle_t, int*, android::IDirectTrackClient*, audio_stream_type_t, android::status_t*)':
frameworks/av/services/audioflinger/AudioFlinger.cpp:651:9: error: 'AudioEventObserver' was not declared in this scope
frameworks/av/services/audioflinger/AudioFlinger.cpp:651:29: error: 'obv' was not declared in this scope
frameworks/av/services/audioflinger/AudioFlinger.cpp:651:48: error: expected type-specifier before 'AudioEventObserver'
frameworks/av/services/audioflinger/AudioFlinger.cpp:651:48: error: expected '>' before 'AudioEventObserver'
frameworks/av/services/audioflinger/AudioFlinger.cpp:651:48: error: expected '(' before 'AudioEventObserver'
frameworks/av/services/audioflinger/AudioFlinger.cpp:651:68: error: expected primary-expression before '>' token
frameworks/av/services/audioflinger/AudioFlinger.cpp:651:82: error: expected ')' before ';' token
frameworks/av/services/audioflinger/AudioFlinger.cpp:653:23: error: 'audio_stream_out_t' has no member named 'set_observer'
make: *** [/run/media/jamiethemorris/LinuxExternal/android/tripndroid_kk/out/target/product/dlx/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/AudioFlinger.o] Error 1
In file included from frameworks/av/services/audioflinger/Threads.cpp:52:0:
frameworks/av/services/audioflinger/AudioFlinger.h:518:5: error: expected class-name before '{' token
In file included from frameworks/av/services/audioflinger/AudioFlinger.h:440:0,
from frameworks/av/services/audioflinger/Threads.cpp:52:
frameworks/av/services/audioflinger/Threads.h: In constructor 'android::AudioFlinger::PlaybackThread::PlaybackThread(const android::sp<android::AudioFlinger>&, android::AudioFlinger::AudioStreamOut*, audio_io_handle_t, audio_devices_t, android::AudioFlinger::ThreadBase::type_t)':
frameworks/av/services/audioflinger/Threads.h:628:14: warning: 'android::AudioFlinger::PlaybackThread::mScreenState' will be initialized after [-Wreorder]
frameworks/av/services/audioflinger/Threads.h:564:26: warning: 'audio_output_flags_t android::AudioFlinger::PlaybackThread::mOutputFlags' [-Wreorder]
frameworks/av/services/audioflinger/Threads.cpp:1050:1: warning: when initialized here [-Wreorder]
In file included from frameworks/av/services/audioflinger/Threads.cpp:52:0:
frameworks/av/services/audioflinger/AudioFlinger.h: In constructor 'android::AudioFlinger::DirectAudioTrack::DirectAudioTrack(const android::sp<android::AudioFlinger>&, int, android::AudioFlinger::AudioSessionDescriptor*, android::IDirectTrackClient*, audio_output_flags_t)':
frameworks/av/services/audioflinger/AudioFlinger.h:594:26: warning: 'android::AudioFlinger::DirectAudioTrack::mAudioFlinger' will be initialized after [-Wreorder]
frameworks/av/services/audioflinger/AudioFlinger.h:541:13: warning: 'int android::AudioFlinger::DirectAudioTrack::mOutput' [-Wreorder]
frameworks/av/services/audioflinger/Threads.cpp:5494:1: warning: when initialized here [-Wreorder]
In file included from frameworks/av/services/audioflinger/Threads.cpp:52:0:
frameworks/av/services/audioflinger/AudioFlinger.h:541:13: warning: 'android::AudioFlinger::DirectAudioTrack::mOutput' will be initialized after [-Wreorder]
frameworks/av/services/audioflinger/AudioFlinger.h:540:33: warning: 'android::AudioFlinger::AudioSessionDescriptor* android::AudioFlinger::DirectAudioTrack::mOutputDesc' [-Wreorder]
frameworks/av/services/audioflinger/Threads.cpp:5494:1: warning: when initialized here [-Wreorder]
In file included from frameworks/av/services/audioflinger/Threads.cpp:52:0:
frameworks/av/services/audioflinger/AudioFlinger.h:540:33: warning: 'android::AudioFlinger::DirectAudioTrack::mOutputDesc' will be initialized after [-Wreorder]
frameworks/av/services/audioflinger/AudioFlinger.h:539:29: warning: 'android::IDirectTrackClient* android::AudioFlinger::DirectAudioTrack::mClient' [-Wreorder]
frameworks/av/services/audioflinger/Threads.cpp:5494:1: warning: when initialized here [-Wreorder]
In file included from frameworks/av/services/audioflinger/Threads.cpp:52:0:
frameworks/av/services/audioflinger/AudioFlinger.h:574:14: warning: 'android::AudioFlinger::DirectAudioTrack::mEffectConfigChanged' will be initialized after [-Wreorder]
frameworks/av/services/audioflinger/AudioFlinger.h:572:14: warning: 'bool android::AudioFlinger::DirectAudioTrack::mKillEffectsThread' [-Wreorder]
frameworks/av/services/audioflinger/Threads.cpp:5494:1: warning: when initialized here [-Wreorder]
In file included from frameworks/av/services/audioflinger/Threads.cpp:52:0:
frameworks/av/services/audioflinger/AudioFlinger.h:572:14: warning: 'android::AudioFlinger::DirectAudioTrack::mKillEffectsThread' will be initialized after [-Wreorder]
frameworks/av/services/audioflinger/AudioFlinger.h:543:30: warning: 'audio_output_flags_t android::AudioFlinger::DirectAudioTrack::mFlag' [-Wreorder]
frameworks/av/services/audioflinger/Threads.cpp:5494:1: warning: when initialized here [-Wreorder]
frameworks/av/services/audioflinger/Threads.cpp: In member function 'virtual android::status_t android::AudioFlinger::DirectAudioTrack::start()':
frameworks/av/services/audioflinger/Threads.cpp:5565:30: error: 'audio_stream_out_t' has no member named 'start'
frameworks/av/services/audioflinger/Threads.cpp: In member function 'virtual void android::AudioFlinger::DirectAudioTrack::stop()':
frameworks/av/services/audioflinger/Threads.cpp:5577:26: error: 'audio_stream_out_t' has no member named 'stop'
frameworks/av/services/audioflinger/Threads.cpp: In member function 'virtual ssize_t android::AudioFlinger::DirectAudioTrack::write(const void*, size_t)':
frameworks/av/services/audioflinger/Threads.cpp:5593:26: error: 'audio_stream_out_t' has no member named 'is_buffer_available'
frameworks/av/services/audioflinger/Threads.cpp: In member function 'void android::AudioFlinger::DirectAudioTrack::allocateBufPool()':
frameworks/av/services/audioflinger/Threads.cpp:5667:26: error: 'audio_stream_out_t' has no member named 'get_buffer_info'
frameworks/av/services/audioflinger/Threads.cpp:5673:20: error: invalid use of incomplete type 'struct android::AudioFlinger::DirectAudioTrack::allocateBufPool()::buf_info'
frameworks/av/services/audioflinger/Threads.cpp:5666:12: error: forward declaration of 'struct android::AudioFlinger::DirectAudioTrack::allocateBufPool()::buf_info'
frameworks/av/services/audioflinger/Threads.cpp:5674:26: error: invalid use of incomplete type 'struct android::AudioFlinger::DirectAudioTrack::allocateBufPool()::buf_info'
frameworks/av/services/audioflinger/Threads.cpp:5666:12: error: forward declaration of 'struct android::AudioFlinger::DirectAudioTrack::allocateBufPool()::buf_info'
frameworks/av/services/audioflinger/Threads.cpp:5678:30: error: invalid use of incomplete type 'struct android::AudioFlinger::DirectAudioTrack::allocateBufPool()::buf_info'
frameworks/av/services/audioflinger/Threads.cpp:5666:12: error: forward declaration of 'struct android::AudioFlinger::DirectAudioTrack::allocateBufPool()::buf_info'
I don't even know where to start with that... This is the part it's complaining about in Audioflinger.h:
Code:
#ifdef QCOM_HARDWARE
// server side of the client's IAudioTrack
class DirectAudioTrack : public android::BnDirectTrack,
public AudioEventObserver
{
I think maybe it's missing an #include or something? I just don't understand why I'm getting all of these errors. I would assume anyone building the ROM would get the same ones?
jamiethemorris said:
I'm trying to build tripndroid, I ran into a few other errors that I fixed already, but I'm hitting this now
Code:
In file included from frameworks/av/services/audioflinger/Tracks.cpp:32:0:
frameworks/av/services/audioflinger/AudioFlinger.h:518:5: error: expected class-name before '{' token
I think maybe it's missing an #include or something? I just don't understand why I'm getting all of these errors. I would assume anyone building the ROM would get the same ones?
Click to expand...
Click to collapse
What have java version are you using?
Sent from my HTC6435LVW using xda app-developers app
danjull said:
What have java version are you using?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I'll have to check when I get home. I'm pretty sure I'm using open jdk6 though.
Sent from my Droid DNA using Tapatalk Pro
---------- Post added at 07:23 PM ---------- Previous post was at 06:57 PM ----------
java version "1.6.0_51"
Java(TM) SE Runtime Environment (build 1.6.0_51-b09)
Java HotSpot(TM) 64-Bit Server VM (build 20.51-b01, mixed mode)
I'm giving up on tripndroid for now... I'm trying to build liquidsmooth now and I'm running into a kernel error. I couldn't see what it was because it happened too far back when it stopped. So I tried to build the kernel individually using linaro 4.8 and it stopped in the same place so I'm pretty sure it's the same error:
Code:
drivers/video/msm/mdp.c: In function 'mdp_hist_lut_write_off':
drivers/video/msm/mdp.c:400:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
error, forbidden warning: mdp.c:400
I think it has to do with linaro because I didn't have any problems building ProBam today with the same kernel... I also tried building the ProBam kernel by itself and it gave me the same error.
EDIT: Well, I used crpalmer's kernel instead and it built perfectly fine... Not the perfect solution though.
Liquid won't flash. No idea why. It just reboots instantly as soon as it starts flashing.
Sent from my iPad using Tapatalk
jamiethemorris said:
I'm giving up on tripndroid for now... I'm trying to build liquidsmooth now and I'm running into a kernel error. I couldn't see what it was because it happened too far back when it stopped. So I tried to build the kernel individually using linaro 4.8 and it stopped in the same place so I'm pretty sure it's the same error:
Code:
drivers/video/msm/mdp.c: In function 'mdp_hist_lut_write_off':
drivers/video/msm/mdp.c:400:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
error, forbidden warning: mdp.c:400
I think it has to do with linaro because I didn't have any problems building ProBam today with the same kernel... I also tried building the ProBam kernel by itself and it gave me the same error.
EDIT: Well, I used crpalmer's kernel instead and it built perfectly fine... Not the perfect solution though.
Click to expand...
Click to collapse
Search for 1024 in the kernel defconfig that is used. There is an config named something with FRAME that sets the size to warn on. You can change it to 2048 to fix the build.
---------- Post added at 06:13 AM ---------- Previous post was at 06:10 AM ----------
jamiethemorris said:
I'm giving up on tripndroid for now... I'm trying to build liquidsmooth now and I'm running into a kernel error. I couldn't see what it was because it happened too far back when it stopped. So I tried to build the kernel individually using linaro 4.8 and it stopped in the same place so I'm pretty sure it's the same error:
Code:
drivers/video/msm/mdp.c: In function 'mdp_hist_lut_write_off':
drivers/video/msm/mdp.c:400:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
error, forbidden warning: mdp.c:400
I think it has to do with linaro because I didn't have any problems building ProBam today with the same kernel... I also tried building the ProBam kernel by itself and it gave me the same error.
EDIT: Well, I used crpalmer's kernel instead and it built perfectly fine... Not the perfect solution though.
Click to expand...
Click to collapse
Also, run
brunch dlx 2>&1 | tee /tmp/build.txt
After the build, that tmp file should hold all the text from the build.
crpalmer said:
Search for 1024 in the kernel defconfig that is used. There is an config named something with FRAME that sets the size to warn on. You can change it to 2048 to fix the build.
---------- Post added at 06:13 AM ---------- Previous post was at 06:10 AM ----------
Also, run
brunch dlx 2>&1 | tee /tmp/build.txt
After the build, that tmp file should hold all the text from the build.
Click to expand...
Click to collapse
Thank you. Do you think that has anything to do with why it won't flash?
Sent from my Droid DNA using Tapatalk
jamiethemorris said:
Thank you. Do you think that has anything to do with why it won't flash?
Sent from my Droid DNA using Tapatalk
Click to expand...
Click to collapse
No, the frame size warning is just there to ensure people don't accidentally so something stupid and breaks the build to let them know. 1K is arbitrary so 2K is also fine.
Can someone give me a little explanation on how the manifest works? Like how it knows which branches to pull of each git project? I'm trying to build carbon and it's running into an issue about BluetoothLwPwrProximityMonitor being undefined. For whatever reason the BluetoothLwPwrProximityMonitor.java file was deleted in the cm11 BluetoothExt repo. This was several months ago though. Both CM11 and ProBam build fine, and they don't have any of the pxpmonitorservice stuff. So it looks like they're using the cm-10.2 or stable/cm-11.0 branch. But it the manifests I don't see anything that differentiates which branch they pull from. Basically, I think I need to have Carbon use stable/cm-11.0 instead of cm-11.0 and then I think it will build, but I just want to make sure I'm doing it right.
EDIT: I tried that, but it doesn't matter now because it gives me this all of a sudden:
Code:
make: *** No rule to make target `/run/media/jamiethemorris/LinuxExternal/android/carbon_kk/out/host/linux-x86/bin/mkbootimg', needed by `/run/media/jamiethemorris/LinuxExternal/android/carbon_kk/out/target/product/dlx/boot.img'. Stop.
Really weird. I'm guessing it's misleading. I tried putting BluetoothExt back to how it was but I get the same error. It got way further than this before.
Code:
find -name mkbootimg*
./system/core/mkbootimg
./system/core/mkbootimg/mkbootimg.c
./external/genext2fs/mkbootimg_ext2.sh
Also, liquid is now hitting this kernel error:
Code:
liquidsmooth_kk/kernel/htc/m7/drivers/video/msm/mipi_novatek.c:569:37: warning: argument to ‘sizeof’ in ‘snprintf’ call is the same expression as the destination; did you mean to provide an explicit length? [-Wsizeof-pointer-memaccess]
error, forbidden warning: mipi_novatek.c:569
I don't know why it's having so much trouble. I'm guessing I will find this in the defconfig as well?
Maybe building ROMs is just not for me...
Don't get discouraged. I'm fixing to start learning, and I need you to figure it all out so I can ask you all my noob questions.
Sent from my HTC6435LVW using Tapatalk
armydog13 said:
Don't get discouraged. I'm fixing to start learning, and I need you to figure it all out so I can ask you all my noob questions.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Thanks. For starters, read this http://xda-university.com/as-a-developer/getting-started-building-android-from-source and this http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code also this link is helpful because you will need to sync CM's repos at the same time for the device tree and kernel, and sometimes other repos http://xda-university.com/as-a-developer/repo-tips-tricks
jamiethemorris said:
I'm giving up on tripndroid for now... I'm trying to build liquidsmooth now and I'm running into a kernel error. I couldn't see what it was because it happened too far back when it stopped. So I tried to build the kernel individually using linaro 4.8 and it stopped in the same place so I'm pretty sure it's the same error:
Code:
drivers/video/msm/mdp.c: In function 'mdp_hist_lut_write_off':
drivers/video/msm/mdp.c:400:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
error, forbidden warning: mdp.c:400
I think it has to do with linaro because I didn't have any problems building ProBam today with the same kernel... I also tried building the ProBam kernel by itself and it gave me the same error.
EDIT: Well, I used crpalmer's kernel instead and it built perfectly fine... Not the perfect solution though.
Click to expand...
Click to collapse
I came here to ask some questions about building liquid myself but since you got it booting guess i might as well give on up huh? I guess I should bring up what im doing anyways so I dont accidentally start on a port one of the pros is starting on lol
DREWHAMM974 said:
I came here to ask some questions about building liquid myself but since you got it booting guess i might as well give on up huh? I guess I should bring up what im doing anyways so I dont accidentally start on a port one of the pros is starting on lol
Click to expand...
Click to collapse
No, don't give up, nothing wrong with teamwork and some learning experience. I don't have it booting, it fails when I flash it and I can't get it to build with the stock kernel
Sent from my Droid DNA using Tapatalk
I am currently trying to build an Ubuntu Touch-compatible kernel for use with the Xperia Z5 Compact. I have been following the How to build and flash a Linux kernel for AOSP supported devices guide and am at the point at which I have created an Ubuntu-compatible .config file but am having issues finally building the kernel (Step 7) using the .config file as I receive the following error:
make ARCH=arm64 CROSS_COMPILE=$CROSS_COMPILE -j 14
Makefile:791: *** multiple target patterns. Stop.
I know that this error is related to the call of link-vmlinux.sh which is referenced as follows on line 791 of the Makefile:
vmlinux: scripts/link-vmlinux.sh $(vmlinux-deps) FORCE
Any suggestions for debugging this problem would be greatly appreciated.
blackstar1744 said:
I am currently trying to build an Ubuntu Touch-compatible kernel for use with the Xperia Z5 Compact. I have been following the How to build and flash a Linux kernel for AOSP supported devices guide and am at the point at which I have created an Ubuntu-compatible .config file but am having issues finally building the kernel (Step 7) using the .config file as I receive the following error:
make ARCH=arm64 CROSS_COMPILE=$CROSS_COMPILE -j 14
Makefile:791: *** multiple target patterns. Stop.
I know that this error is related to the call of link-vmlinux.sh which is referenced as follows on line 791 of the Makefile:
vmlinux: scripts/link-vmlinux.sh $(vmlinux-deps) FORCE
Any suggestions for debugging this problem would be greatly appreciated.
Click to expand...
Click to collapse
Yah, I'm facing the same problem. Only with 64-bit targets (G4 and G4 Stylus), this doesn't happen with any 32bit targets. It doesn't matter if I swap out the toolchain, it doesn't matter which tree I'm working -- Omni, Bliss, CM13 -- all can't get past that error.
So it doesn't seem like it's in the build tree, but maybe my system. I'm using Arch, so I'm used to Android building snafus, but still I cannot figure this out. I've gone through every chain leading to the error and I can't seem to pin it down. It's really harshing my build.
Lil' help, y'all?
UPDATE: Nevermind, just had to set USE_HOST_LEX. Goddammit, I though I already tried that.
Any explanation for why you need to set USE_HOST_LEX? Is this an OS- or compiler-related modification? I'm compiling with UBERTC 4.9 on Ubuntu 14.04 LTS. I currently don't have USE_HOST_LEX in my .config file.
culot said:
Yah, I'm facing the same problem. Only with 64-bit targets (G4 and G4 Stylus), this doesn't happen with any 32bit targets. It doesn't matter if I swap out the toolchain, it doesn't matter which tree I'm working -- Omni, Bliss, CM13 -- all can't get past that error.
So it doesn't seem like it's in the build tree, but maybe my system. I'm using Arch, so I'm used to Android building snafus, but still I cannot figure this out. I've gone through every chain leading to the error and I can't seem to pin it down. It's really harshing my build.
Lil' help, y'all?
UPDATE: Nevermind, just had to set USE_HOST_LEX. Goddammit, I though I already tried that.
Click to expand...
Click to collapse
blackstar1744 said:
Any explanation for why you need to set USE_HOST_LEX? Is this an OS- or compiler-related modification? I'm compiling with UBERTC 4.9 on Ubuntu 14.04 LTS. I currently don't have USE_HOST_LEX in my .config file.
Click to expand...
Click to collapse
USE_HOST_LEX set the build to use host's Flex instead of the one in-tree. See build/core/config.mk:
Code:
ifeq ($(USE_HOST_LEX),yes)
LEX := flex
else
LEX := prebuilts/misc/$(BUILD_OS)-$(HOST_PREBUILT_ARCH)/flex/flex-2.5.39
endif
I don't know about elsewhere, but this has been a problem on Arch for a while. Lately this has not longer been a problem for me, so I assumed it was not an issue. Apparently still a problem for 64bit build, but not 32bit. Hmm.
Another workaround was to preface your make with LC_ALL=C, but I tried that without setting 'USE_HOST_LEX=yes' and it didn't help.
EDIT: I don't think it's compiler-related, as I did try different toolchains and different toolchain versions -- none made a difference. I tried 3 different Make versions, no help. USE_HOST_LEX? That fixed it. Compiling as we speak.
I added export USE_HOST_LEX=yes to my .bashrc and went back to the GCC compiler...new problem to debug. Any suggestions on debugging control groups would be greatly appreciated
Code:
make ARCH=arm64 CROSS_COMPILE=$CROSS_COMPILE -j 1
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CALL scripts/checksyscalls.sh
<stdin>:1226:2: warning: #warning syscall sched_setattr not implemented [-Wcpp]
<stdin>:1229:2: warning: #warning syscall sched_getattr not implemented [-Wcpp]
CC scripts/mod/devicetable-offsets.s
GEN scripts/mod/devicetable-offsets.h
HOSTCC scripts/mod/file2alias.o
HOSTLD scripts/mod/modpost
CHK include/generated/compile.h
SKIPPED include/generated/compile.h
CC kernel/cgroup.o
kernel/cgroup.c: In function 'subsys_cgroup_allow_attach':
kernel/cgroup.c:2138:59: error: invalid operands to binary != (have 'kuid_t' and 'kuid_t')
if (current != task && cred->euid != tcred->uid &&
^
kernel/cgroup.c:2139:18: error: invalid operands to binary != (have 'kuid_t' and 'kuid_t')
cred->euid != tcred->suid)
^
make[1]: *** [kernel/cgroup.o] Error 1
make: *** [kernel] Error 2
Random side rant: The way Google shows search results is going wayyy downhill.