From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: improve SSP logic
Date: Tue, 8 Mar 2016 17:13:57 +0100 [thread overview]
Message-ID: <20160308171357.309278e1@free-electrons.com> (raw)
In-Reply-To: <1457453323-11947-1-git-send-email-Vincent.Riera@imgtec.com>
Hello Vicente,
On Tue, 8 Mar 2016 16:08:43 +0000, Vicente Olivert Riera wrote:
> Don't enable SSP support on toolchains just because they use glibc or
> musl. Instead of that, make the toolchains to declare if they support
> SSP or not. And also add a check to detect SSP support when using custom
> external toolchains.
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> toolchain/Config.in | 2 --
> toolchain/helpers.mk | 17 ++++++++++++++++
> toolchain/toolchain-external/Config.in | 23 ++++++++++++++++++++--
> toolchain/toolchain-external/toolchain-external.mk | 1 +
> 4 files changed, 39 insertions(+), 4 deletions(-)
>
> diff --git a/toolchain/Config.in b/toolchain/Config.in
> index fc30c6e..e0044c1 100644
> --- a/toolchain/Config.in
> +++ b/toolchain/Config.in
> @@ -15,7 +15,6 @@ config BR2_TOOLCHAIN_USES_GLIBC
> select BR2_TOOLCHAIN_HAS_THREADS_DEBUG
> select BR2_TOOLCHAIN_HAS_THREADS_NPTL
> select BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDS
> - select BR2_TOOLCHAIN_HAS_SSP
>
> config BR2_TOOLCHAIN_USES_UCLIBC
> bool
> @@ -27,7 +26,6 @@ config BR2_TOOLCHAIN_USES_MUSL
> select BR2_TOOLCHAIN_HAS_THREADS
> select BR2_TOOLCHAIN_HAS_THREADS_DEBUG
> select BR2_TOOLCHAIN_HAS_THREADS_NPTL
> - select BR2_TOOLCHAIN_HAS_SSP
>
> choice
> prompt "Toolchain type"
I think this patch is incomplete because you are now saying that all
glibc and musl toolchains no longer have SSP support, and only
re-enable SSP support for external toolchains on a per-toolchain basis.
Sounds good for external toolchains.
But what about internal glibc and musl toolchains ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-08 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 16:08 [Buildroot] [PATCH] toolchain: improve SSP logic Vicente Olivert Riera
2016-03-08 16:13 ` Thomas Petazzoni [this message]
2016-03-08 16:18 ` Vicente Olivert Riera
-- strict thread matches above, loose matches on Subject: below --
2016-03-15 16:39 Vicente Olivert Riera
2016-03-15 16:39 ` 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=20160308171357.309278e1@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