**** BEGIN LOGGING AT Wed Mar 16 02:59:58 2016
Mar 16 07:12:29 <blogic> Kaloz: ping
Mar 16 07:41:12 <builder> build #235 of imx6 is complete: Failure [failed shell_18 compile_9]  Build details are at http://buildbot.openwrt.org:8010/builders/imx6/builds/235
Mar 16 07:50:54 <builder> build #168 of mpc52xx is complete: Failure [failed shell_13]  Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/168
Mar 16 07:58:05 <builder> build #240 of brcm63xx is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/240
Mar 16 08:01:18 <builder> build #232 of cns21xx is complete: Failure [failed shell_13]  Build details are at http://buildbot.openwrt.org:8010/builders/cns21xx/builds/232
Mar 16 09:21:52 <builder> build #197 of brcm63xx.smp is complete: Failure [failed shell_18]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx.smp/builds/197
Mar 16 09:22:17 <builder> build #242 of ipq806x is complete: Failure [failed shell_18]  Build details are at http://buildbot.openwrt.org:8010/builders/ipq806x/builds/242
Mar 16 09:29:08 <builder> build #240 of lantiq is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/240
Mar 16 10:07:13 <Kaloz> blogic: pong
Mar 16 12:08:30 <blogic> Kaloz: approve the mail to the users list please
Mar 16 12:08:40 <blogic> Kaloz: Your message has been rejected, probably because you are not
Mar 16 12:08:45 <blogic> ... subscribed to the mailing lis
Mar 16 12:09:01 <blogic> or someone else needs to resend it
Mar 16 12:21:39 <Kaloz> blogic: resent it
Mar 16 12:27:29 <rmilecki> i posted on forum (and so added news to the main site)
Mar 16 12:27:31 <rmilecki> https://openwrt.org/
Mar 16 12:27:37 <rmilecki> https://forum.openwrt.org/viewtopic.php?id=63415
Mar 16 12:41:59 <blogic> rmilecki: thatnks for solving issues
Mar 16 13:24:35 <netprince> Thanks everyone for the CC bugfix release
Mar 16 14:50:14 <mamarley> blogic: Regarding GLIBC 2.23, should I make it the default in my patch or just add it and leave 2.22 as default?
Mar 16 17:49:17 <builder> build #243 of ramips is complete: Failure [failed compile_2]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/243
Mar 16 17:49:17 <builder> build #198 of brcm63xx.smp is complete: Failure [failed compile_2]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx.smp/builds/198
Mar 16 18:26:07 <mamarley> Hmm, I attempted to create a patch for adding GLIBC 2.23 to trunk, but when compiling for x86_64, I get a bunch of "undefined reference to `__stack_chk_guard'" while compiling the toolchain.
Mar 16 18:32:50 <plntyk> mamarley: check SSP / stack protector settings during compilation or so
Mar 16 18:33:57 <plntyk> its all aroung the build system (grep -R "SSP_SUPPORT")
Mar 16 18:52:00 <mamarley> plntyk: I did some googling and figured out that's what it was, but I am using the default settings (make defconfig and change only the target and the libc).  I don't have SSP turned on.  In fact, you can't turn it on for x86_64.
Mar 16 18:57:29 <builder> build #179 of uml is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/179
Mar 16 18:58:27 <plntyk> mamarley:  well you could post a log of the toolchain build (always enable logging^^)
Mar 16 18:59:13 <plntyk> mamarley: there is  toolchain/glibc/common.mk:export libc_cv_ssp=no
Mar 16 18:59:52 <plntyk> checking configure logs for ssp / libssp / stack protection stuff
Mar 16 19:02:25 <mamarley> It prints out thousands of lines of output when compiling.  I don't know how to isolate those particular ones.
Mar 16 19:03:05 <plntyk> there is an option to enable logging in menuconfig - CONFIG_BUILD_LOG=y  - and then you have txt files in folder logs/
Mar 16 19:03:25 <plntyk> its in advanced dev options
Mar 16 19:03:27 <mamarley> Ah, OK.
Mar 16 19:05:01 <mamarley> OK, rebuilding with that on...
Mar 16 20:58:53 <builder> build #179 of ath25 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/ath25/builds/179
Mar 16 22:17:04 <mamarley> plntyk: It looks like I am getting "-fstack-protector-strong" in logs/toolchain/glibc/compile.txt despite having stack protection turned off in "Global Build Settings".
Mar 16 22:17:04 <mamarley> Hmm, looks like there is another SSP option under Toolchain Configuration.  Let me turn that off...  It does default to on though, and GLIBC 2.22 was fine with that.
Mar 16 22:17:04 <mamarley> Even with that turned off I still get the same result (-fstack-protector-strong and the build failure.)
Mar 16 22:20:42 <plntyk> yeah - so you just have to track down where that flag comes from - the build_dir/toolchain... dir afaik where the error happens should contain a config.log where compile variables might be set
Mar 16 22:25:17 <mamarley> There is no config.log there.
Mar 16 22:26:39 <mamarley> There is some Configure-related output in the "compile.txt" under logs/toolchain/glibc though.
Mar 16 22:27:29 <mamarley> It says "checking for -fstack-protector-strong... yes", but gives no clue as to why.
Mar 16 22:34:55 <mamarley> I'm clueless.
Mar 17 00:07:09 <mamarley> I was able to solve the issue by adding "export libc_cv_ssp_strong=no" to the common.mk file.
Mar 17 01:23:00 <builder> build #170 of adm5120 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/170
**** ENDING LOGGING AT Thu Mar 17 02:59:58 2016