Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] eglibc: defaults to SSP
Date: Sun, 25 Aug 2013 08:59:41 -0300	[thread overview]
Message-ID: <5219F1AD.10004@zacarias.com.ar> (raw)
In-Reply-To: <20130825111144.052f703c@skate>

On 08/25/2013 06:11 AM, Thomas Petazzoni wrote:

> Ok, so if we try to summarize this:
> 
>  * The option to enable SSP should be in "Build options" and not in the
>    "Toolchain" menu, because what it mainly does is adjust the
>    CFLAGS/CXXFLAGS for all packages.
> 
>  * In the case of the internal toolchain backend, it would make sure
>    that the SSP support in the C library in enabled. I.e, nothing for
>    eglibc/glibc, and enable SSP for uClibc.
> 
>  * In the case of the external toolchain backend, we would need to have
>    an option like "Toolchain supports SSP?" that the user must fill in.
>    But this would mean the "Use SSP" option in "Build options" would
>    have to depend on the "Toolchain supports SSP?" option.
> 
> Something like that?

Yes, i'd add for the last point "if custom external toolchain" because
we can determine if the predefined toolchain has ssp when it's
bumped/added with an internal knob.
It's possible libssp might need to be handled (copied) for some external
toolchains depending on age too and how they were configured.
Regards.

  reply	other threads:[~2013-08-25 11:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-27 14:32 [Buildroot] [PATCH] eglibc: defaults to SSP Gustavo Zacarias
2013-08-23 19:09 ` Thomas Petazzoni
2013-08-23 19:53   ` Gustavo Zacarias
2013-08-25  9:11     ` Thomas Petazzoni
2013-08-25 11:59       ` Gustavo Zacarias [this message]
2013-08-26 22:03         ` Thomas Petazzoni

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=5219F1AD.10004@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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