From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: use -fstack-protector-strong for both compiling and linking
Date: Sat, 18 Jun 2022 23:07:33 +0200 [thread overview]
Message-ID: <20220618210733.ZJOZrhBCwjQkBtLbNQoTrCjgOdZjqx_FqcGcYG2sAIU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-229@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 315 bytes --]
There's a closed pull request on the mblaze repository
use -fstack-protector-strong for both compiling and linking
https://github.com/leahneukirchen/mblaze/pull/229
Description:
gcc needs -fstack-protector-strong when linking else `__stack_chk_fail` and `__stack_chk_guard` are not defined (at least on Solaris).
prev parent reply other threads:[~2022-06-18 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 3:17 [PR PATCH] " gco
2022-06-18 21:07 ` leahneukirchen [this message]
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=20220618210733.ZJOZrhBCwjQkBtLbNQoTrCjgOdZjqx_FqcGcYG2sAIU@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
--subject='Re: [PR PATCH] [Closed]: use -fstack-protector-strong for both compiling and linking' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).