From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] package/Makefile.in: Do not use CPPFLAGS for hardening options
Date: Fri, 10 Aug 2018 22:32:17 +0200 [thread overview]
Message-ID: <20180810223217.21bcb66f@windsurf> (raw)
In-Reply-To: <1531998123-28360-2-git-send-email-stefan.sorensen@spectralink.com>
Hello,
On Thu, 19 Jul 2018 13:02:01 +0200, Stefan S?rensen wrote:
> The hardening options are compiler flags, not pure pre-processor flags, so
> put them in CFLAGS, not CPPFLAGS.
>
> This fixes build errors where -D_FORTIFY_SOURCE=2 whas put in CPPFLAGS and
> then applied to configure tests which could fail since the required -O2 is
> only in CFLAGS.
>
> Signed-off-by: Stefan S?rensen <stefan.sorensen@spectralink.com>
I have applied this patch, from the series resent by Matt Weber.
See:
https://git.buildroot.org/buildroot/commit/?h=next&id=d4f5801027f3329fb6c2cd096f3396d3cd067390
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-10 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 11:02 [Buildroot] [PATCH v2 0/3] Hardening build flags fixes Stefan Sørensen
2018-07-19 11:02 ` [Buildroot] [PATCH v2 1/3] package/Makefile.in: Do not use CPPFLAGS for hardening options Stefan Sørensen
2018-08-10 20:32 ` Thomas Petazzoni [this message]
2018-07-19 11:02 ` [Buildroot] [PATCH v2 2/3] package/Makefile.in: Add missing options to LDFLAGS for full RELRO build Stefan Sørensen
2018-08-10 20:34 ` Thomas Petazzoni
2018-07-19 11:02 ` [Buildroot] [PATCH v2 3/3] package/Makefile.in: Use gcc spec files for PIE build flags Stefan Sørensen
2018-07-19 12:27 ` [Buildroot] [PATCH v2 0/3] Hardening build flags fixes Thomas Petazzoni
2018-07-19 12:51 ` Sørensen, Stefan
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=20180810223217.21bcb66f@windsurf \
--to=thomas.petazzoni@bootlin.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