From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Christophe LEROY <christophe.leroy@c-s.fr>,
Segher Boessenkool <segher@kernel.crashing.org>
Cc: Christian Kujau <lists@nerdbynature.de>, linuxppc-dev@lists.ozlabs.org
Subject: Re: bootx_init.c:88: undefined reference to `__stack_chk_fail_local'
Date: Thu, 12 Jan 2017 09:20:47 -0600 [thread overview]
Message-ID: <1484234447.2492.34.camel@kernel.crashing.org> (raw)
In-Reply-To: <7604032b-c9ae-e3ce-fcd5-d9e555559f52@c-s.fr>
On Thu, 2017-01-12 at 15:42 +0100, Christophe LEROY wrote:
> The 4.6.3 uses __stack_chk_guard, while the 4.4.4 and 4.8.3 use
> -28680(r2)
>
> Is it dependent on the way GCC is built ? Then do we have a way to
> know,
> when we compile, which method GCC will use ?
>
> See details below for each of the 3 GCC versions.
I think it depends if you built it along with glibc (so it can produce
userspace binaries) or not.
Cheers,
Ben.
next prev parent reply other threads:[~2017-01-12 15:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 15:25 bootx_init.c:88: undefined reference to `__stack_chk_fail_local' Christian Kujau
2017-01-03 19:20 ` Christian Kujau
2017-01-03 22:50 ` Benjamin Herrenschmidt
2017-01-03 22:57 ` Christian Kujau
2017-01-04 8:23 ` Christophe LEROY
2017-01-04 8:40 ` Segher Boessenkool
2017-01-04 7:32 ` Christophe LEROY
2017-01-04 15:22 ` Christian Kujau
2017-01-04 18:33 ` Christian Kujau
2017-01-10 2:11 ` Christian Kujau
2017-01-10 4:32 ` Benjamin Herrenschmidt
2017-01-10 6:12 ` Christophe LEROY
2017-01-10 18:46 ` Christian Kujau
2017-01-10 6:26 ` Christophe LEROY
2017-01-11 22:54 ` Segher Boessenkool
2017-01-12 7:52 ` Christophe LEROY
2017-01-12 14:42 ` Christophe LEROY
2017-01-12 15:20 ` Benjamin Herrenschmidt [this message]
2017-01-12 18:07 ` Segher Boessenkool
2017-01-13 12:15 ` Christophe LEROY
2017-01-13 12:23 ` David Laight
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=1484234447.2492.34.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lists@nerdbynature.de \
--cc=segher@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).