Ok . . . *make ARCH=arm > CROSS_COMPILE=/home/m/qbb/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf- > -C /lib/modules/3.2.0-4-amd64/build M=/home/m/qbb/rtl8812AU_8821AU_linux > modules* >
First of all, modules / drivers have to be compiled against a specific kernel, for the specified hardware. Here, this gcc toolchain *might* possibly be able to handle the task, however you're linking against the wrong modules( wrong architecture *and* wrong kernel headers ). *make[1]: Entering directory `/usr/src/linux-headers-3.2.0-4-amd64' > /usr/src/linux-headers-3.2.0-4-common/arch/x86/Makefile:81: stack protector > enabled but no compiler support* > Unsure about this specific complaint, but you can google the error as easily as I. *make[3]: > /home/m/qbb/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf-gcc-4.6: > Command not found* > *CC [M] /home/m/qbb/rtl8812AU_8821AU_linux/core/rtw_cmd.o /bin/sh: 1: > /home/m/qbb/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf-gcc-4.6: > not found* > Command not found. It is very likely since the path you've given is for the gnueabi-4.9* gcc toolchain. So . . . gcc 4.6* is not likely to exist in this path. Meaning: you're grasping at straws, hoping the toolchain you want / need exists in this location, but it does not. *make[4]: *** [/home/m/qbb/rtl8812AU_8821AU_linux/core/rtw_cmd.o] Error 127* > *make[3]: *** [_module_/home/m/qbb/rtl8812AU_8821AU_linux] Error 2* > *make[2]: *** [sub-make] Error 2* > *make[1]: *** [all] Error 2* > *make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-4-amd64'* > *make: *** [modules] Error 2* Superfluous errors, likely to clear up once the previous error conditions are taken care of. So with all the above said, this probably does not help you solve your problem. What would help you fix / understand the problem is understanding how to use the / a gcc toolchain. There are many books on the internet that explain this process. Some of which can be downloaded for free, and are very good.Passed that, you're going to need a firm grasp of how to compile kernel modules for your hardware. My suggestion, and actually what I would do in your place would be to compile the kernel modules natively on the beaglebone black. You can make an alternate sdcard, or some form of bootable media / root file system to act as a build / support system for your beaglebone black. This "support" image needs to be the exact same kernel as your "production" image. Going about things this way alleviates the potential cross compiler issues you're very likely ( and have already met ) to run into. Now, gain, with all that said, there is already a very good chance that the realtech drivers you're trying to compile already exist in the kernel, but you may need to enable them in the kernel config( no hands on and simply a guess ). Either way no one without the specific hardware, could tell you 100% for sure how to go about what you need done. And quite honestly there is no incentive for me, or anyone else to go out and buy hardware specifically to tell you how it is done. Let alone take our own time to do so . . . Sorry if that seems harsh, but that is the plain simple truth of the matter. On Thu, Feb 5, 2015 at 11:33 PM, m <[email protected]> wrote: > Yea you are right, i was trying to follow RCN"S compiler settings. > > Can you recommend a guide/tutorial for setting up a cross compiling > environment for the new Beaglebone Blacks running Debian? > > I have a spare laptop, so I can install whatever flavor of Linux or > Windows the tutorial recommends. I just keep hitting dead ends when I try > it on my own desktop that runs Debian 7.4. > > On Thursday, February 5, 2015 at 7:45:28 PM UTC-8, William Hermans wrote: >> >> Linaro is just a prebuilt gcc, with (I havent paid much attention to >> which ) prepackaged libc. As the previous poster said, make is complaining >> that it doesnt know where to find the needed gcc toolchain path. That, and >> I am guessing you're following parts of RCN's cross compiler setup guide >> for compiling uboot, and the Linux kernel. >> >> On Thu, Feb 5, 2015 at 2:26 PM, Graham <[email protected]> wrote: >> >>> >>> m: >>> >>> I am sorry that I am not familiar with the linaro cross-compiler, I >>> exclusively use the gcc, >>> and I let the Eclipse IDE automatically generate the make files. >>> >>> I can only suggest that you review the installation instructions for the >>> linaro, and make sure >>> that everything is installed properly in the intended locations. Check >>> that everything are >>> compatible versions of Linux and the tool chain >>> >>> The errors are saying that "arm-linux-gnueabihf-gcc-4.6" can't be >>> located. That is version 4.6 of >>> the gcc cross compiler. Perhaps linaro actually distributes the gcc. I >>> would go look in those >>> locations and see what is there. If you see what you are expecting, but >>> Linux says it can not >>> see it, then it is usually incompatible versions of the support >>> libraries like glibc, preventing >>> run time dynamic linking. >>> >>> If it is not there at all, then there is some kind of installation error. >>> >>> --- Graham >>> >>> == >>> >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
