From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] sox: disable SSP when using MIPS Codescape toolchains
Date: Mon, 29 Feb 2016 21:08:27 +0100 [thread overview]
Message-ID: <20160229210827.18465518@free-electrons.com> (raw)
In-Reply-To: <56D47948.9020505@imgtec.com>
Hello,
On Mon, 29 Feb 2016 17:00:56 +0000, Vicente Olivert Riera wrote:
> Uhm..., how would you do that? BR2_TOOLCHAIN_HAS_SSP is selected by
> BR2_TOOLCHAIN_USES_GLIBC. We would need to do changes in the toolchain
> infra in order to not define it in that place, and define it
> individually for every toolchain. Is that what you mean?
Yes, this is what I mean. It is indeed more work, but looks cleaner IMO.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-29 20:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 16:39 [Buildroot] [PATCH] sox: disable SSP when using MIPS Codescape toolchains Vicente Olivert Riera
2016-02-29 16:51 ` Thomas Petazzoni
2016-02-29 17:00 ` Vicente Olivert Riera
2016-02-29 20:08 ` Thomas Petazzoni [this message]
2016-03-01 10:40 ` Peter Korsgaard
2016-03-01 10:32 ` Peter Korsgaard
2016-03-01 10:36 ` Vicente Olivert Riera
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=20160229210827.18465518@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox