All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <lists@nerdbynature.de>
To: Benjamin Herrenschmidt <benh@au1.ibm.com>
Cc: Christophe LEROY <christophe.leroy@c-s.fr>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: bootx_init.c:88: undefined reference to `__stack_chk_fail_local'
Date: Tue, 10 Jan 2017 10:46:23 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.20.999.1701101041480.5450@trent.utfs.org> (raw)
In-Reply-To: <1484022722.21117.8.camel@au1.ibm.com>

On Mon, 9 Jan 2017, Benjamin Herrenschmidt wrote:
> On Mon, 2017-01-09 at 18:11 -0800, Christian Kujau wrote:
> > So, with -fno-stack-protector my GCC 4.9.2 compiles with 
> > CC_STACKPROTECTOR_STRONG=y but panics during boot:
> 
> How can it make any sense to have -fno-stack-protector and
> CC_STACKPROTECTOR_STRONG=y at the same time ?

I've set -fno-stack-protector only for bootx_init.c, as laid out in the 
diff I posted. This way the kernel at least compiled.

Thanks,
Christian.
-- 
BOFH excuse #423:

It's not RFC-822 compliant.

  parent reply	other threads:[~2017-01-10 18:46 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 [this message]
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
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=alpine.DEB.2.20.999.1701101041480.5450@trent.utfs.org \
    --to=lists@nerdbynature.de \
    --cc=benh@au1.ibm.com \
    --cc=christophe.leroy@c-s.fr \
    --cc=linuxppc-dev@lists.ozlabs.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 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.