From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next] tpm2-abrmd: fix build without stack smashing protection (SSP)
Date: Wed, 21 Nov 2018 15:43:37 -0200 [thread overview]
Message-ID: <20181121174337.341-1-casantos@datacom.com.br> (raw)
The configuration environment setup that disables SSP if the toolchain
does not support it must be updated after the bump to version 2.0.3.
Fixes:
http://autobuild.buildroot.net/results/bd9005eeb24678aa530179a80bbc99b2176f8559
http://autobuild.buildroot.net/results/feff61dcb481a94f5f030117830984c5e09727ea
Signed-off-by: Carlos Santos <casantos@datacom.com.br>
---
package/tpm2-abrmd/tpm2-abrmd.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/tpm2-abrmd/tpm2-abrmd.mk b/package/tpm2-abrmd/tpm2-abrmd.mk
index a4d9cfb384..74cc66ba20 100644
--- a/package/tpm2-abrmd/tpm2-abrmd.mk
+++ b/package/tpm2-abrmd/tpm2-abrmd.mk
@@ -13,7 +13,7 @@ TPM2_ABRMD_DEPENDENCIES = dbus libglib2 tpm2-tss host-pkgconf
# configure.ac doesn't contain a link test, so it doesn't detect when
# libssp is missing.
-TPM2_ABRMD_CONF_ENV = ax_cv_check_cflags___fstack_protector_all=$(if $(BR2_TOOLCHAIN_HAS_SSP),yes,no)
+TPM2_ABRMD_CONF_ENV = ax_cv_check_cflags___________Werror_______fstack_protector_all=$(if $(BR2_TOOLCHAIN_HAS_SSP),yes,no)
TPM2_ABRMD_CONF_OPTS += \
--with-systemdsystemunitdir=$(if $(BR2_INIT_SYSTEMD),/usr/lib/systemd/system,no) \
--
2.19.1
next reply other threads:[~2018-11-21 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 17:43 Carlos Santos [this message]
2018-11-21 20:06 ` [Buildroot] [PATCH next] tpm2-abrmd: fix build without stack smashing protection (SSP) Thomas Petazzoni
2018-11-22 1:46 ` Carlos Santos
2018-11-23 14:01 ` Carlos Santos
2018-11-28 10:43 ` Carlos Santos
2018-12-03 12:28 ` 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=20181121174337.341-1-casantos@datacom.com.br \
--to=casantos@datacom.com.br \
--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