From: Sebastian Herbszt <herbszt@gmx.de>
To: Benjamin Marzinski <bmarzins@redhat.com>
Cc: dm-devel@redhat.com, Sebastian Herbszt <herbszt@gmx.de>
Subject: multipath-tools: -fstack-protector to fstack-protector-strong change
Date: Mon, 21 Jul 2014 17:17:32 +0200 [thread overview]
Message-ID: <20140721171732.00002396@localhost> (raw)
Hello Benjamin,
your patch "enable gcc format-security check" (9b7741c) not only added
-Wformat-security, but also changed fstack-protector to fstack-protector-strong.
Was this change intentional? It is not mentioned in the commit log and seems
to require a recent gcc:
cc: error: unrecognized command line option ‘-fstack-protector-strong’
with
gcc version 4.8.2 20140324 [gcc-4_8-branch revision 208789] (SUSE Linux)
Sebastian
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next reply other threads:[~2014-07-21 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 15:17 Sebastian Herbszt [this message]
2014-07-21 22:45 ` multipath-tools: -fstack-protector to fstack-protector-strong change Benjamin Marzinski
2014-07-22 4:59 ` Bart Van Assche
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=20140721171732.00002396@localhost \
--to=herbszt@gmx.de \
--cc=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
/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