Unable to make on Arch Linux
rtl8723au (master) $ make
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/3.14.2-1-ARCH/build M=/home/tp/rtl8723au modules
make[1]: Entering directory '/usr/lib/modules/3.14.2-1-ARCH/build'
Makefile:615: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
CC [M] /home/tp/rtl8723au/core/rtw_cmd.o
gcc: erreur: unrecognized command line option ‘-fstack-protector-strong’
scripts/Makefile.build:308: recipe for target '/home/tp/rtl8723au/core/rtw_cmd.o' failed
make[2]: *** [/home/tp/rtl8723au/core/rtw_cmd.o] Error 1
Makefile:1274: recipe for target '_module_/home/tp/rtl8723au' failed
make[1]: *** [_module_/home/tp/rtl8723au] Error 2
make[1]: Leaving directory '/usr/lib/modules/3.14.2-1-ARCH/build'
Makefile:516: recipe for target 'modules' failed
make: *** [modules] Error 2
CC version:
rtl8723au (master) $ cc --version
cc (GCC) 4.8.2 20140206 (prerelease)
Copyright © 2013 Free Software Foundation, Inc.
Looks like the kernel you're using was compiled against GCC 4.9.0, as per the following: https://mailman.archlinux.org/pipermail/arch-general/2014-May/036065.html https://bugs.archlinux.org/task/40171
You're using GCC 4.8.2 which doesn't support the stack-protector-strong flag. Looks like Arch broke everybody else's modules.
To make it more clear (I hope), you will not be able to build this driver using Arch's kernel 3.14.2-1 until Arch updates your compiler to 4.9.0. Your other option is to get the kernel source, and build your own 3.14.2-1 using your current gcc.
Thanks for the info. Arch updated gcc to 4.9.0 already.
Le jeudi 1 mai 2014, lwfinger [email protected] a écrit :
To make it more clear (I hope), you will not be able to build this driver using Arch's kernel 3.14.2-1 until Arch updates your compiler to 4.9.0. Your other option is to get the kernel source, and build your own 3.14.2-1 using your current gcc.
— Reply to this email directly or view it on GitHubhttps://github.com/lwfinger/rtl8723au/issues/39#issuecomment-41979483 .
Timothée Poisot, Ph.D.
Québec Centre for Biodiversity Sciences Université du Québec à Rimouski International Network of Next-Generation Ecologists
http://timotheepoisot.fr/ http://doodle.com/tpoisot/ @tpoi
It builds now, but with errors
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/3.14.2-1-ARCH/build M=/home/tp/rtl8723au modules
make[1]: Entering directory '/usr/lib/modules/3.14.2-1-ARCH/build'
CC [M] /home/tp/rtl8723au/os_dep/usb_intf.o
/home/tp/rtl8723au/os_dep/usb_intf.c: In function ‘rtw_drv_entry’:
/home/tp/rtl8723au/os_dep/usb_intf.c:1466:53: erreur: macro "__DATE__" might prevent reproducible builds [-Werror=date-time]
DBG_8723A("build time: %s %s\n", __DATE__, __TIME__);
^
/home/tp/rtl8723au/os_dep/usb_intf.c:1466:1: erreur: macro "__TIME__" might prevent reproducible builds [-Werror=date-time]
DBG_8723A("build time: %s %s\n", __DATE__, __TIME__);
^
cc1: some warnings being treated as errors
scripts/Makefile.build:308: recipe for target '/home/tp/rtl8723au/os_dep/usb_intf.o' failed
make[2]: *** [/home/tp/rtl8723au/os_dep/usb_intf.o] Error 1
Makefile:1274: recipe for target '_module_/home/tp/rtl8723au' failed
make[1]: *** [_module_/home/tp/rtl8723au] Error 2
make[1]: Leaving directory '/usr/lib/modules/3.14.2-1-ARCH/build'
Makefile:516: recipe for target 'modules' failed
make: *** [modules] Error 2
Doesn't seem too bad, because I can install and load the module, though.
I have no idea how that works as your console output clearly indicates that the build failed.
I removed the code that referenced DATE and TIME and pushed the changes. Do another git pull and rebuild.
I also had the error in https://github.com/lwfinger/rtl8723au/issues/39#issuecomment-42062637 and commenting it out resolved the DATE/TIME issue for me.
Or you could have done a 'git pull' to get an updated source. Now, you will likely have to undo your changes to get a clean pull.
I know. My device does not have an Ethernet port, so I would have had to reboot into an older kernel version to get Internet access and do a git pull. It was easier to just comment out the offending line. :)
I just wanted to comment as tpoisot never followed up, and I think that this issue is now resolved.