From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3tzv5Q0TDPzDqYp for ; Fri, 13 Jan 2017 05:13:29 +1100 (AEDT) Date: Thu, 12 Jan 2017 12:07:14 -0600 From: Segher Boessenkool To: Benjamin Herrenschmidt Cc: Christophe LEROY , Christian Kujau , linuxppc-dev@lists.ozlabs.org Subject: Re: bootx_init.c:88: undefined reference to `__stack_chk_fail_local' Message-ID: <20170112180713.GU28613@gate.crashing.org> References: <81ef821b-8af2-0ee5-ab35-58639548dab7@c-s.fr> <20170111225440.GQ28613@gate.crashing.org> <1c81ce1a-33ca-7ba4-56f5-976935deb609@c-s.fr> <7604032b-c9ae-e3ce-fcd5-d9e555559f52@c-s.fr> <1484234447.2492.34.camel@kernel.crashing.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 In-Reply-To: <1484234447.2492.34.camel@kernel.crashing.org> List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Jan 12, 2017 at 09:20:47AM -0600, Benjamin Herrenschmidt wrote: > 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. Right. Tony's compilers are built using a (modified version of) buildall, and buildall goes out of its way to build without libc whatsoever, even if the configuration (powerpc64-linux, for example) expects one. Which leads to TARGET_LIBC_PROVIDES_SSP being undefined (it would normally be true for glibc >= 2.4), and that is all. Mystery solved. Thanks! Segher