From: "Miles Lane" <miles.lane@gmail.com>
To: "Arjan van de Ven" <arjan@infradead.org>
Cc: "Andrew Morton" <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail'
Date: Sat, 1 Jul 2006 15:56:28 -0700 [thread overview]
Message-ID: <a44ae5cd0607011556t65b22b06m317baa9a47ff962@mail.gmail.com> (raw)
In-Reply-To: <a44ae5cd0607011537o1cf00545td19e568dcb9c06c1@mail.gmail.com>
On 7/1/06, Miles Lane <miles.lane@gmail.com> wrote:
> On 7/1/06, Arjan van de Ven <arjan@infradead.org> wrote:
> > On Sat, 2006-07-01 at 14:25 -0700, Miles Lane wrote:
> > > On 7/1/06, Arjan van de Ven <arjan@infradead.org> 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?
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?
Thanks,
Miles
next prev parent reply other threads:[~2006-07-01 22:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-01 21:09 Miles Lane
2006-07-01 21:17 ` Arjan van de Ven
2006-07-01 21:25 ` Miles Lane
2006-07-01 21:29 ` Arjan van de Ven
2006-07-01 22:37 ` Miles Lane
2006-07-01 22:56 ` Miles Lane [this message]
2006-07-01 23:06 ` Sam Ravnborg
2006-07-01 23:11 ` H. Peter Anvin
2006-07-01 23:26 ` H. Peter Anvin
2006-07-01 23:34 ` Miles Lane
2006-07-01 23:35 ` H. Peter Anvin
2006-07-02 3:01 ` Sam Ravnborg
2006-07-02 3:03 ` H. Peter Anvin
2006-07-02 4:05 ` Miles Lane
2006-07-02 4:52 ` H. Peter Anvin
2006-07-02 6:12 ` Miles Lane
2006-07-02 7:42 ` Arjan van de Ven
2006-07-02 17:07 ` Miles Lane
2006-07-02 17:32 ` Arjan van de Ven
2006-07-02 17:37 ` H. Peter Anvin
2006-07-02 17:50 ` Arjan van de Ven
2006-07-02 17:52 ` Arjan van de Ven
2006-07-02 18:04 ` H. Peter Anvin
2006-07-03 5:17 ` Ingo Molnar
2006-07-03 13:07 ` Miles Lane
2006-07-03 15:09 ` H. Peter Anvin
[not found] <fa.WuLfTz/aICPisBh2gZXGQmS9xvs@ifi.uio.no>
[not found] ` <fa.LW8cO+QP5MhBZ9HST2AOy+N/e6o@ifi.uio.no>
2006-07-02 4:26 ` Robert Hancock
[not found] <fa.iPhEst5K48JbrGWRr3l3/GEBesY@ifi.uio.no>
[not found] ` <fa.iffnN5wM1UwqtCYhmqLAkGCMC2o@ifi.uio.no>
2006-07-02 17:31 ` Robert Hancock
2006-07-02 17:44 ` H. Peter Anvin
2006-07-02 17:51 ` Arjan van de Ven
2006-07-02 18:01 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a44ae5cd0607011556t65b22b06m317baa9a47ff962@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®