Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'

[Miles Lane]

On 7/1/06, Sam Ravnborg <sam@xxxxxxxxxxxx> wrote:
>  >> > > >
> > >> > > >   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?

This fixed is for me.  Andrew, would this be appropriate to merge into
your tree?

--- scripts/Kbuild.klibc.old    2006-07-01 16:32:55.000000000 -0700
+++ scripts/Kbuild.klibc        2006-07-01 16:28:59.000000000 -0700
@@ -51,7 +51,7 @@
KLIBCREQFLAGS     :=
KLIBCARCHREQFLAGS :=
KLIBCOPTFLAGS     :=
-KLIBCWARNFLAGS    := -W -Wall -Wno-sign-compare -Wno-unused-parameter
+KLIBCWARNFLAGS    := -W -Wall -Wno-sign-compare -Wno-unused-parameter
-fno-stack-protector
KLIBCSHAREDFLAGS  :=
KLIBCBITSIZE      :=
KLIBCLDFLAGS      :=
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/