>> > > > > >> > > > KLIBCLD usr/klibc/libc.so > >> > > > usr/klibc/execl.o: In function `execl': ... > > >https://wiki.ubuntu.com/GccSsp > > > >It appears that Ubuntu's Edgy Eft (the development tree) now contains > >"Stack Smashing Protection" enabled by default. I found a web page > >that states that -fno-stack-protector can be used to disable this > >functionality. Interestingly, another web page stated that SSP has > >been enabled in Redhat compilers for a long time and is now also > >enabled in Debian SID. Perhaps -fno-stack-protector should be added > >to the kernel build be default? > > Darn it. I don't seem to know how to get -fno-stack-protector to > work. I ran: > export CFLAGS=-fno-stack-protector > make mrproper > cp ../.config . > make oldconfig > CFLAGS=-fno-stack-protector make all install modules modules_install > > But I am still getting the errors. Anyone know what I am doing wrong? For klibc you need to patch scripts/Kbuild.klibc Appending it to KLIBCWARNFLAGS seems the right place. Do you know from what gcc version we can start using -fno-stack-protector? Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'
- From: "H. Peter Anvin" <[email protected]>
- Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'
- From: "Miles Lane" <[email protected]>
- Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'
- From: "H. Peter Anvin" <[email protected]>
- Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'
- References:
- 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'
- From: "Miles Lane" <[email protected]>
- Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'
- From: Arjan van de Ven <[email protected]>
- Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'
- From: "Miles Lane" <[email protected]>
- Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'
- From: Arjan van de Ven <[email protected]>
- Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'
- From: "Miles Lane" <[email protected]>
- Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'
- From: "Miles Lane" <[email protected]>
- 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'
- Prev by Date: Re: 2.6.17-mm5 dislikes raid-1, just like mm4
- Next by Date: Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'
- Previous by thread: Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'
- Next by thread: Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'
- Index(es):
 |