Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mosh: fix build with the Codescape IMG toolchain
Date: Tue, 5 Apr 2016 23:25:24 +0300	[thread overview]
Message-ID: <20160405202524.GX3088@tarshish> (raw)
In-Reply-To: <95907701a43145654f7962319823a0f7fe73551b.1459879412.git.baruch@tkos.co.il>

Hi Buildroot list,

On Tue, Apr 05, 2016 at 09:03:32PM +0300, Baruch Siach wrote:
> The Codescape IMG toolchain does not provide the ssp library even though it's
> a glibc toolchain, and thus selects BR2_TOOLCHAIN_HAS_SSP. Add a patch that
> changes the compile test for -fstack-protector-all to a build test that
> correctly fails when ssp is missing.
> 
> This makes the seeding of ssp related configure variables unnecessary.

If forgot to add autobuild references.

Fixes:
http://autobuild.buildroot.net/results/f57/f571cf13462833984504b6dabad98a6b0fb3facb/
http://autobuild.buildroot.net/results/a20/a206849cae4ecb8b2b9afb077852576ccad3536e/
http://autobuild.buildroot.net/results/86b/86b99fe4df64b47c9b76e75896a7470d84d504d7/

> Signed-off-by: Baruch Siach <baruch@tkos.co.il>

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2016-04-05 20:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 18:03 [Buildroot] [PATCH] mosh: fix build with the Codescape IMG toolchain Baruch Siach
2016-04-05 20:25 ` Baruch Siach [this message]
2016-04-05 21:47 ` Arnout Vandecappelle
2016-04-05 23:08   ` Arnout Vandecappelle
2016-04-05 23:23     ` Arnout Vandecappelle
2016-04-06  3:27   ` Baruch Siach

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=20160405202524.GX3088@tarshish \
    --to=baruch@tkos.co.il \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox