-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compilation error on rtw_mlme_ext.c #49
Comments
try with this toolchain Also see this there is something in rtw_mlme_ext.c at line number 1835 |
Ok, I tried with this toolchain
#endif #ifdef CONFIG_AP_MODE |
what version of gcc you are using look at this
change line 1835 attribute ((fallthrough)); to /* attribute ((fallthrough)); */ that is comment these lines to disable but still I think your gcc version is less than 7.x because attribute ((fallthrough)); was introduced at gcc 7.x or greater. try and leave comment |
Thanks, I'll try. Can I first assemble the kernel with one compiler and then build the module with another? Because the kernel source is not going with the new versions of the compiler and giving a huge amount of errors |
yes definitely you can do that but remember my notes not to change any name or anything |
I just tried to build the official driver rtl8188eus |
yes definitely you have to build the kernel first from source code then only you can do this |
There is a slightly easier method to make it build into kernel. @Re4son may you provide patch link? |
yes please share it if you have any |
I don't have any patches for the 8812eus, sorry. It turned out that the driver we've been using never actually worked on Android and I removed it because it caused conflicts with the rtl8812au, which by itself works perfectly. |
Yes, it would be cool to add this driver to the kernel |
what are you telling guys I am using both 8188eu.ko and 88XXau.ko at the same time not conflicting at all |
You are talking about rtl8812eu or rtl8188eus, the rtl8188eus driver cannot conflict with rtl8812au if I am not mistaken. I really don’t understand, these are different chips |
Look I want to be clear on this I successfully built two drivers both from aircrack-ng project name rtl8812au and rtl8188eus. All the guides I provided were only for these two drivers. I never built 8812eus or anything like that if you are trying my guides for building 8812eu or 8812eus then I m sorry mate cant help you in this regard because I dont have any device to test for them. You also should try 8812eus project page if any not here. This place is only for 8188eus. Regards. |
Did you build them as kernel modules? |
yes I build them as kernel modules |
This link #31 |
Nice. |
yup absolutely why dont you also ship 8188eus along with 8812au ? |
Because we don't want modules on Android and 8812eus does not compile alongside 8812au. |
ok now i get that |
I used this
toolchain:
wget https://releases.linaro.org/components/toolchain/binaries/4.9-2016.02/arm-linux-gnueabihf/gcc-linaro-4.9-2016.02-x86_64_arm-linux-gnueabihf.tar.xz
kernel source:
git clone https://github.com/Re4son/android_kernel_lge_hammerhead -b nethunter-7.1
p.s I uploaded work progress to image hosting
So first I build kernel from source:
1 a) https://ibb.co/PrcMhgN
b) https://ibb.co/bXdmFvC
c) https://ibb.co/nssySDS (Here you can see that the compilation was successful)
2 make
a) https://ibb.co/NLRQq9X mrproper
b) https://ibb.co/r0XT6HZ defconfig nethunter_defconfig and modules_prepare
c) https://ibb.co/HLyNZ8b modules_install and git clone rtl8188eus
3 Next, I configured Makefile
https://ibb.co/HqxQC77 this
4 And finally "make"
https://ibb.co/r6t01Pk this
Hooray, compilation started, but breaks off on 'rtw_mlme_ext.c'
I can’t understand what the problem is, please tell me what I'm doing wrong
My defconfig file if that
http://s000.tinyupload.com/index.php?file_id=12376423205617620599
Thanks
The text was updated successfully, but these errors were encountered: