All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] toolchain: fix detection of SSP support
Date: Sun, 25 Mar 2018 23:21:56 +0200	[thread overview]
Message-ID: <20180325232156.1716cb0b@windsurf> (raw)
In-Reply-To: <20180325035953.25906-2-casantos@datacom.ind.br>

Hello,

On Sun, 25 Mar 2018 00:59:52 -0300, Carlos Santos wrote:
> GCC issues a warning message if -fstack-protector is passed but SSP is
> not available, so in order to force the compilation to fail we must also
> pass -Werror.
> 
> All external toolchains were verified. The only one whose configuration
> incorrectly selected BR2_TOOLCHAIN_HAS_SSP was CodeSourcery NIOSII.
> 
> Fixes:
>   http://autobuild.buildroot.net/results/ce8fe8ac9cf0db01ae15d476ea714ff176965cfb
>   http://autobuild.buildroot.net/results/09ce8f05e28c0219f499ce55130e896cae0c8b45
> 
> Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
> ---
>  toolchain/helpers.mk                                                    | 2 +-
>  .../toolchain-external/toolchain-external-codesourcery-niosII/Config.in | 1 -
>  2 files changed, 1 insertion(+), 2 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-03-25 21:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-25  3:59 [Buildroot] [PATCH 0/2] tpm2-* fix build errors Carlos Santos
2018-03-25  3:59 ` [Buildroot] [PATCH 1/2] toolchain: fix detection of SSP support Carlos Santos
2018-03-25 21:21   ` Thomas Petazzoni [this message]
2018-03-25  3:59 ` [Buildroot] [PATCH 2/2] tpm2-tools: fix compilation error due to uninitialized variable Carlos Santos
2018-03-25 13:44   ` Peter Korsgaard

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=20180325232156.1716cb0b@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.