From: "H. Peter Anvin" <hpa@zytor.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Miles Lane <miles.lane@gmail.com>, 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: Sun, 02 Jul 2006 11:04:37 -0700 [thread overview]
Message-ID: <44A80AB5.9060101@zytor.com> (raw)
In-Reply-To: <1151862632.3111.25.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
>>>
>> Obviously, but at that time we should enable -fno-stack-protector vs
>
> -fno-stack-protector doesn't even exist afaics; simply because gcc has
> this as a positive commandline option only..
You actively have to fight gcc's internals to make a boolean option
positive only, and that's a good thing. The only reason it's possible
at all are as a way to deal with multistate options.
-hpa
next prev parent reply other threads:[~2006-07-02 18:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-01 21:09 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail' 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
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 [this message]
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=44A80AB5.9060101@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.