From: "Miles Lane" <miles.lane@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Sam Ravnborg" <sam@ravnborg.org>,
"Arjan van de Ven" <arjan@infradead.org>,
"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 21:05:26 -0700 [thread overview]
Message-ID: <a44ae5cd0607012105g23a22e67ma3fd2bdd7c9352a4@mail.gmail.com> (raw)
In-Reply-To: <44A73790.5030006@zytor.com>
On 7/1/06, H. Peter Anvin <hpa@zytor.com> wrote:
> Sam Ravnborg wrote:
> >
> >> -KLIBCREQFLAGS :=
> >> +KLIBCREQFLAGS := $(call cc_option, -fno-stack-protector, )
> >
> > This needs to be $(call cc-option, ...)
> > '-' not '_'.
> >
>
> *plonk* OK... I feel dumb now :)
>
> Miles: could you try this out?
>
> >> +++ b/usr/klibc/arch/arm/MCONFIG
> >> @@ -12,7 +12,7 @@ CPU_TUNE := strongarm
> >>
> >> KLIBCOPTFLAGS = -Os -march=$(CPU_ARCH) -mtune=$(CPU_TUNE)
> >> KLIBCBITSIZE = 32
> >> -KLIBCREQFLAGS = -fno-exceptions
> >> +KLIBCREQFLAGS += -fno-exceptions
> >
> > This should be fixed for KLIBCOPTFLAGS also. Unrelated to this issue.
> >
>
> *Nod.*
I gave it my best shot, but my build is still unhappy.
I set:
KLIBCREQFLAGS := $(call cc-option, -fno-stack-protector, )
in scripts/Kbuild.klibc.
KLIBCOPTFLAGS = -march=i386 -Os -g -fomit-frame-pointer
$(gcc_align_option) $(call cc-option, -fno-stack-protector, )
in usr/klibc/arch/i386/MCONFIG
CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
$(call cc-option, -fno-stack-protector, ) -fno-common
in Makefile.
Trying to compile, I get:
include/asm/system.h: In function '__set_64bit_var':
include/asm/system.h:209: warning: dereferencing type-punned pointer
will break strict-aliasing rules
next prev parent reply other threads:[~2006-07-02 4:05 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
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 [this message]
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=a44ae5cd0607012105g23a22e67ma3fd2bdd7c9352a4@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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®