From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751201AbWGAWhy (ORCPT ); Sat, 1 Jul 2006 18:37:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751202AbWGAWhy (ORCPT ); Sat, 1 Jul 2006 18:37:54 -0400 Received: from py-out-1112.google.com ([64.233.166.176]:40361 "EHLO py-out-1112.google.com") by vger.kernel.org with ESMTP id S1751201AbWGAWhx (ORCPT ); Sat, 1 Jul 2006 18:37:53 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ItRjtM/qimphCeyih+lw0/GHPM+uj70OkuYSIUonx8+E0L22H/6KCahyXQz9QdBh/iSybMNQl6YdQgCGm2RXllAc05VsuDaOD8Cg29Yl6AGH57UiWRnCvinZjPfUkIzJBQjDjmxANGtu/Za9fskIGst8D3wNxQruFB4grrUemZQ= Message-ID: Date: Sat, 1 Jul 2006 15:37:53 -0700 From: "Miles Lane" To: "Arjan van de Ven" Subject: Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail' Cc: "Andrew Morton" , LKML In-Reply-To: <1151789342.3195.60.camel@laptopd505.fenrus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1151788673.3195.58.camel@laptopd505.fenrus.org> <1151789342.3195.60.camel@laptopd505.fenrus.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 7/1/06, Arjan van de Ven wrote: > On Sat, 2006-07-01 at 14:25 -0700, Miles Lane wrote: > > On 7/1/06, Arjan van de Ven wrote: > > > On Sat, 2006-07-01 at 14:09 -0700, Miles Lane wrote: > > > > I am getting this: > > > > > > > > KLIBCLD usr/klibc/libc.so > > > > usr/klibc/execl.o: In function `execl': > > > > usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail' > > > > usr/klibc/execle.o: In function `execle': > > > > usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail' > > > > usr/klibc/execvpe.o: In function `execvpe': > > > > usr/klibc/execvpe.c:75: undefined reference to `__stack_chk_fail' > > > > usr/klibc/execlp.o: In function `execlp': > > > > usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail' > > > > usr/klibc/execlpe.o: In function `execlpe': > > > > usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail' > > > > usr/klibc/vfprintf.o:usr/klibc/vfprintf.c:26: more undefined > > > > references to `__stack_chk_fail' follow > > > > make[2]: *** [usr/klibc/libc.so] Error 1 > > > > > > > > But I've searched all the .h and .c files in the tree and found no > > > > reference to __stack_chk_fail. I am running Ubuntu's Edgy Eft (the > > > > latest development tree). > > > > > > somehow you're getting -fstack-protector added to your CFLAGs.. which > > > won't do you any good unless you link to glibc or another library that > > > implements the user side of the feature... > > > > The only reference to -fstack-protector in my linux kernel tree is here: > > > try looking at your CFLAGS environment variable.. that may get > inherited ;) 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? Thanks, Miles