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.