From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RFC v1 1/1] gcc: fix problem with detecting SSP under uclibc-ng
Date: Thu, 17 Sep 2015 19:42:10 +0200 [thread overview]
Message-ID: <20150917174210.GH8475@waldemar-brodkorb.de> (raw)
In-Reply-To: <CA+BsyQ7RqCVPi6h9VUJpdQ49pVZwLnCGzRtL+wN1JUhs+T7_WA@mail.gmail.com>
Hi,
Brendan Heading wrote,
> Aside from that .. GCC actually already has a block which checks
> UCLIBC_HAS_SSP. The problem is that it reaches it only if the glibc
> version check returns that the version is 2.3 or lower. The fix might
> simply be to reorder the check.
>
> I'm curious why GCC have done this rather than doing a check for the
> __stack_chk symbols. Would be interested in hearing from Alexey and
> Waldemar.
I vote for the GCC patch, if there is already a __UCLIBC_HAS_SSP__
check.
best regards
Waldemar
next prev parent reply other threads:[~2015-09-17 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 14:37 [Buildroot] [PATCH RFC v1 1/1] gcc: fix problem with detecting SSP under uclibc-ng Brendan Heading
2015-09-17 17:14 ` Thomas Petazzoni
2015-09-17 17:29 ` Brendan Heading
2015-09-17 17:42 ` Waldemar Brodkorb [this message]
2015-09-17 20:20 ` Thomas Petazzoni
2015-09-17 21:22 ` Brendan Heading
2015-09-18 7:11 ` Thomas Petazzoni
2015-09-17 22:10 ` Alexey Brodkin
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=20150917174210.GH8475@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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