Hello all, I was trying to cook up this AOKP based rom last night, and I let it build overnight as I usually do.
This morning, I woke up to:
Code:
make[6]: *** [drivers/net/wireless/bcmdhd/dhd_linux.o] Error 1
make[5]: *** [drivers/net/wireless/bcmdhd] Error 2
make[4]: *** [drivers/net/wireless] Error 2
make[3]: *** [drivers/net] Error 2
make[2]: *** [drivers] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/nathan/AICP/kernel/htc/m7'
make: *** [TARGET_KERNEL_BINARIES] Error 2
I was going to use a prebuilt, but when I go to my m7spr directory (straight from AOKP source) I didn't see a kernel folder.
I know that I need to edit TARGET_KERNEL_BINARIES in BoardConfig.mk for m7-common, but I edited it to "aokp_m7_defconfig" and nothing changed. Please help and thank you in advance!!
That really doesn't show what the error is, just that there is an error.
Sent from my HTCONE
thicklizard said:
That really doesn't show what the error is, just that there is an error.
Sent from my HTCONE
Click to expand...
Click to collapse
I was hoping that someone might recognize this or something but I run into almost every time.
Installed a package that someone said would fix the problem, and I'm anxious to see if it works, but it will have to be until tonight.
Also, I discovered that java 7 doesn't play well with kitkat. For some reason, you can use 7 to build jb, but if you use it with kitkat you will have issues. I installed 7 to use netflix on ubuntu, but I reverted to 6. The combination of those two things will hopefully fix it, if not I'll be back
Thank you for your help.
nathantaylor said:
I was hoping that someone might recognize this or something but I run into almost every time.
Installed a package that someone said would fix the problem, and I'm anxious to see if it works, but it will have to be until tonight.
Also, I discovered that java 7 doesn't play well with kitkat. For some reason, you can use 7 to build jb, but if you use it with kitkat you will have issues. I installed 7 to use netflix on ubuntu, but I reverted to 6. The combination of those two things will hopefully fix it, if not I'll be back
Thank you for your help.
Click to expand...
Click to collapse
I would have to see the exact error in that .c file
Sent from my HTCONE
thicklizard said:
I would have to see the exact error in that .c file
Sent from my HTCONE
Click to expand...
Click to collapse
Yeah, I'm long past that terminal window now but if it ever comes up again I'll try and DM you or something.... Thank you
Sent from my Nexus 7 using Tapatalk 4
You can and will have many unidentifiable errors based on Java 7. In my experience, even having 6 installed won't help forever because somehow 7 will inadvertently be tripped; no idea why. This is what I did:
http://forum.xda-developers.com/showpost.php?p=47782603&postcount=4978
Hope it helps....
Related
Hey there, I'm compiling the android source with a couple of mods merged in from cyanogenmod and leonnib4. I was getting a few random errors, but they went away with simple fixes...Now, I'm getting a new error, and I can't seem to wrap my head around it. It happens almost right out of the gate...every time I type make...
EDIT: New error 41. I seemed to have fixed the old error 1 by removing the previous build from out/target/product/passion, as the error pointed to the obj folder. Everything went smooth until the camera, and now I have a new error. I'm trying to merge in CyanogenMod camera source (for 720p), and I think that's the problem. Could it be something in the framework? I'm lost.
I have set up my build env on a MacBook Pro running OS X 10.5.8 with all the proper tools installed as per the AOSP site's instructions. I have run the envsetup script, and chosen the passion lunch option (yum )...
Anyway, here's the error:
Code:
81 errors
make: *** [out/target/common/obj/APPS/Camera_intermediates/classes-full-debug.jar] Error 41
The full scenario on pastebin: http://pastebin.com/8359mktC
Does anyone have any idea what's going on?
ik this is really old but what did u do to fix this? having the same error compiling cm9
i am trying to compile kernel src from dell with android ndk. i got this error
SYMLINK include/asm -> include/asm-arm
CC kernel/bounds.s
cc1: error: unrecognized command line option "-mlittle-endian"
cc1: error: unrecognized command line option "-mapcs"
cc1: error: unrecognized command line option "-mno-sched-prolog"
cc1: error: unrecognized command line option "-mabi=apcs-gnu"
kernel/bounds.c:1: error: bad value (armv5t) for -march= switch
kernel/bounds.c:1: error: bad value (armv5t) for -mtune= switch
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
where can i find nvidia src from how_to_build.txt ?
thanks
mashi said:
i am trying to compile kernel src from dell with android ndk. i got this error
SYMLINK include/asm -> include/asm-arm
CC kernel/bounds.s
cc1: error: unrecognized command line option "-mlittle-endian"
cc1: error: unrecognized command line option "-mapcs"
cc1: error: unrecognized command line option "-mno-sched-prolog"
cc1: error: unrecognized command line option "-mabi=apcs-gnu"
kernel/bounds.c:1: error: bad value (armv5t) for -march= switch
kernel/bounds.c:1: error: bad value (armv5t) for -mtune= switch
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
where can i find nvidia src from how_to_build.txt ?
thanks
Click to expand...
Click to collapse
I told you the other day how to fix that stuff... You're not specifying the cross compiler to use.
export PATH=$PATH:/media3/android/ds7/dev/arm-2010q1/bin
export CROSS_COMPILE=arm-none-linux-gnueabi-
export ARCH=arm
Using CodeSorcery. If you're using something else, substitute, and of course update the path.
As for the nvidia source.. I never did find 2.6.32.9 from nvidia, but I did find this..
http://developer.nvidia.com/tegra/forum/build-android-source-tegra-250
From which I was able to grab it. Then I ran into this:
http://developer.nvidia.com/tegra/forum/linux-kernel-compilation-error-when-building-confignfsfsm
In the end, either source of the kernel I used, one gave me that the symbol map didn't match (using Dell source 3.36) and the other I kept getting the outer_cache symbol missing (from the nvidia source).
I suspect that it's just a matter of setting up the kernel correctly. I'm using /proc/config.gz but I googled around a bit and some folks here on XDA building a kernel on a phone were saying they had to add some extra parameters given to them by Samsung before being able to successfully build a module that would work for their phone.
Hopefully one of us figures it out... You want CIFS, I want TUN.
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin:/home/alan/android-ndk-r5c/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin
echo $CROSS_COMPILER
/home/alan/android-ndk-r5c/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi-
echo $ARCH
arm
I have set all those path before compile the kernel
khaytsus said:
I told you the other day how to fix that stuff... You're not specifying the cross compiler to use.
export PATH=$PATH:/media3/android/ds7/dev/arm-2010q1/bin
export CROSS_COMPILE=arm-none-linux-gnueabi-
export ARCH=arm
Using CodeSorcery. If you're using something else, substitute, and of course update the path.
As for the nvidia source.. I never did find 2.6.32.9 from nvidia, but I did find this..
http://developer.nvidia.com/tegra/forum/build-android-source-tegra-250
From which I was able to grab it. Then I ran into this:
http://developer.nvidia.com/tegra/forum/linux-kernel-compilation-error-when-building-confignfsfsm
In the end, either source of the kernel I used, one gave me that the symbol map didn't match (using Dell source 3.36) and the other I kept getting the outer_cache symbol missing (from the nvidia source).
I suspect that it's just a matter of setting up the kernel correctly. I'm using /proc/config.gz but I googled around a bit and some folks here on XDA building a kernel on a phone were saying they had to add some extra parameters given to them by Samsung before being able to successfully build a module that would work for their phone.
Hopefully one of us figures it out... You want CIFS, I want TUN.
Click to expand...
Click to collapse
I'll be following this thread as I'm trying to figure this out, too (I'm very much a Linux n00b, though, so the progress is incredibly slow). I think the kernel compilation is the main thing holding us back from getting some custom ROMs on here; once the parameters of the build environment are found, we'll probably have an easier time of it (and, good as DJ_Steve is, it would be nice to have a few more devs working this device).
Does this link help at all?
http://opensource.dell.com/releases/streak7/3.36/HOW-TO-BUILD.txt
Z4nd4r said:
I'll be following this thread as I'm trying to figure this out, too (I'm very much a Linux n00b, though, so the progress is incredibly slow). I think the kernel compilation is the main thing holding us back from getting some custom ROMs on here; once the parameters of the build environment are found, we'll probably have an easier time of it (and, good as DJ_Steve is, it would be nice to have a few more devs working this device).
Does this link help at all?
http://opensource.dell.com/releases/streak7/3.36/HOW-TO-BUILD.txt
Click to expand...
Click to collapse
Not really, at least not me.. First off finding nvidia Froyo source was a PITA and I only got it from a clone of the old repo so no tellling there.. Plus the other steps seem to mostly be nonsense, as files don't match up, etc..
Otherwise, I can readily compile the Dell code but the output won't load.. Symbol map does not match; ie: config is different. Maybe even compiler differences.. Dunno.
Im sorry for my noobness, but what would this code actually do for us? Would we then have the ability to compile our own kernels and overclock and whatnot?
ssmr2t said:
Im sorry for my noobness, but what would this code actually do for us? Would we then have the ability to compile our own kernels and overclock and whatnot?
Click to expand...
Click to collapse
Maybe, but I just want tun.ko for now. Still no luck today, switched to Android NDK but still symbol issues.
Sent from my Dell Streak 7 using Tapatalk
If u can catch it compiler version is output through dmesg during bootup I don't have me streak handy or I would check. Compiler version may very well play a roll in modules loading though I have experienced it on x86 anyway
Brandas said:
If u can catch it compiler version is output through dmesg during bootup I don't have me streak handy or I would check. Compiler version may very well play a roll in modules loading though I have experienced it on x86 anyway
Click to expand...
Click to collapse
Good idea, but it doesn't seem to have much info..
<5>[ 0.000000] Linux version 2.6.32.9 ([email protected]) (gcc version 4.4.0 (GCC) ) #8 SMP PREEMPT Mon Mar 28 14:04:54 CST 2011
Thread Resurrection in progress.
I'm going to be adding FTDI VCP support. Figured I'd post here to see what progress others have made... was a little surprised to only find 2 dev pages for this tablet.
Yeah, I've been working on a 2.6.35 kernel myself slowly, but I totally screwed it up and need to start over.
Maybe who try developing kernel should search help in other tegra2 device forums
Sent from my LG-P500 using Tapatalk
nikoltu said:
Maybe who try developing kernel should search help in other tegra2 device forums
Click to expand...
Click to collapse
Any particular forum you have in mind? I did take a look at the somewhat updated Dell Opensource page:
http://opensource.dell.com/releases/streak7/5.06/
But it is definitely aimed at HC, and I don't think it would do much for an ICS build. On the other hand, at least it gives what "appears" to be the source and binaries for the devices (though I'm a little more inclined to use what I was able to pull off the device with ADB).
FWIW...
---------- Post added at 11:52 AM ---------- Previous post was at 11:33 AM ----------
One other link that appears to be of interest:
http://developer.nvidia.com/tegra-resources
Note the releases as of 12/19 of updated Tegra kits
The info from opensource.dell.com is missing a lot of information.
Hey there all
I'm trying to compile a kernel for the GT-I9070P from the default Sammy source (opensource.samsung.com) and I've encountered an error and I hope you guys can help me with this:
Code:
drivers/staging/nmf-cm/cm/engine/dsp/src/dsp.c: In function 'cm_DSP_AcknowledgeDspIrq':
drivers/staging/nmf-cm/cm/engine/dsp/src/dsp.c:315:5: error: variable 'dummy' set but not used [-Werror=unused-but-set-variable]
cc1: all warnings being treated as errors
make[3]: *** [drivers/staging/nmf-cm/cm/engine/dsp/src/dsp.o] Error 1
make[2]: *** [drivers/staging/nmf-cm] Error 2
make[1]: *** [drivers/staging] Error 2
make[1]: *** Waiting for unfinished jobs....
I wonder if any of you guys have encountered these errors.....
Hi.
Dont use GCC 4.5+ to build kernel.
If you still wanna use GCC 4.5+, here is a method:
In your /drivers/staging/nmf-cm/makefile, just delete "Werror".
And build it again.
Recommend using Linaro GCC 4.4.5 or GCC 4.4.3 .
EDIT:
Although you can have a booting kernel, but the phone will reboot immediately when you dial out.
I replacd dsp.c from other source code, and it built with no errors.
The phone still will reboot when dial out.
Hmm....so that means the phone will reboot upon attempting to call someone ?
I give up writing anymore signatures.
CallMeVentus said:
Hmm....so that means the phone will reboot upon attempting to call someone ?
I give up writing anymore signatures.
Click to expand...
Click to collapse
Yep, when some calls come it will reboot, too.
It has no reboot issue with gcc 4.4
BTW,sorry, just now i replied a wrong thread.
cocafe said:
Yep, when some calls come it will reboot, too.
It has no reboot issue with gcc 4.4
BTW,sorry, just now i replied a wrong thread.
Click to expand...
Click to collapse
Nah it's fine , I believe you just saved my ass
I give up writing anymore signatures.
Thread moved to General section.
Go Dirty, Never Clean and make your brain burn
Does anybody have tried or have any experience compiling this rom for our device?
I have spend few hours today figuring out how to do that, found some problems the fixinf them and the another problem and cant move forward.
Got his error:
Code:
make: *** No rule to make target '/home/pajdek/DU/out/target/product/w7/obj/STATIC_LIBRARIES/libqc-art-compiler_intermediates/export_includes', needed by '/home/pajdek/DU/out/target/product/w7/obj/SHARED_LIBRARIES/libart-compiler_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
Dont know what to do now any thoughts?
ppajdek said:
Go Dirty, Never Clean and make your brain burn
Does anybody have tried or have any experience compiling this rom for our device?
I have spend few hours today figuring out how to do that, found some problems the fixinf them and the another problem and cant move forward.
Got his error:
Code:
make: *** No rule to make target '/home/pajdek/DU/out/target/product/w7/obj/STATIC_LIBRARIES/libqc-art-compiler_intermediates/export_includes', needed by '/home/pajdek/DU/out/target/product/w7/obj/SHARED_LIBRARIES/libart-compiler_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
Dont know what to do now any thoughts?
Click to expand...
Click to collapse
Hi,
I compile several roms for the Galaxy S4, but I have seen this there before. A quick and dirty fix is to do this:
Code:
$ mkdir /home/pajdek/DU/out/target/product/w7/obj/STATIC_LIBRARIES/libqc-art-compiler_intermediates/
$ touch /home/pajdek/DU/out/target/product/w7/obj/STATIC_LIBRARIES/libqc-art-compiler_intermediates/export_includes
Then you have to build dirty, e.g., don't "make clean" before your build.
Another option is to build CM for your phone, then steal the file from the out folder of CM's build and put it in the out folder of your build.
Here is a write up I did on that, if you want to read up on it a bit:
https://thealaskalinuxuser.wordpress.com/2016/06/10/error-no-rule-to-make-target-export_includes/
Hope that helps! Good luck!
Thanks for your reply, i will try that.
Uncle google told me that there were a commit for CM that should fix this.
Two solutions to try
I am trying to build a rom (for the flame (4) device) but I am getting this error that I cannot resolve, it pops up even with allow missing dependencies
Code:
bootable/recovery/Android.mk: error: "librecovery_ui_ext (SHARED_LIBRARIES android-arm64) missing librecovery_ui_flame (STATIC_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
build/make/core/main.mk:1006: error: exiting from previous errors.
ahsank128 said:
I am trying to build a rom (for the flame (4) device) but I am getting this error that I cannot resolve, it pops up even with allow missing dependencies
Code:
bootable/recovery/Android.mk: error: "librecovery_ui_ext (SHARED_LIBRARIES android-arm64) missing librecovery_ui_flame (STATIC_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
build/make/core/main.mk:1006: error: exiting from previous errors.
Click to expand...
Click to collapse
Best place to ask: https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763/page986
Good luck! :good:
StrangerWeather said:
Best place to ask: https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763/page986
Good luck! :good:
Click to expand...
Click to collapse
Thank You!
ahsank128 said:
Thank You!
Click to expand...
Click to collapse
Did you ever manage to get this solved?