public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: linux-kernel@vger.kernel.org
Cc: Michal Marek <mmarek@suse.cz>,
	linux-kbuild@vger.kernel.org,
	Markos Chandras <Markos.Chandras@imgtec.com>
Subject: Re: [PATCH] Makefile: Unset stack-protector gcc flag if it is not supported
Date: Thu, 20 Feb 2014 12:46:32 +0000	[thread overview]
Message-ID: <5305F928.5070600@imgtec.com> (raw)
In-Reply-To: <1391793327-9578-1-git-send-email-markos.chandras@imgtec.com>

On 02/07/2014 05:15 PM, Markos Chandras wrote:
> In case the compiler does not support the stack-protector option,
> unset the flag to avoid build failures. Printing a warning is enough
> to let the user know that this flag will not be used.
> Fixes the following build problem when using a toolchain which does
> not support the -fstack-protector-strong flag:
>
> Makefile:614: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG:
> -fstack-protector-strong not supported by compiler
> mips-linux-gnu-gcc: error: unrecognized command line option
> '-fstack-protector-strong'
> scripts/Makefile.build:308: recipe for target 'scripts/mod/empty.o' failed
> make[2]: *** [scripts/mod/empty.o] Error 1
> make[2]: *** Waiting for unfinished jobs....
> scripts/Makefile.build:455: recipe for target 'scripts/mod' failed
>
> Cc: Michal Marek <mmarek@suse.cz>
> Cc: linux-kbuild@vger.kernel.org
> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
> ---
>   Makefile | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/Makefile b/Makefile
> index 606ef7c..63a5333 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -607,12 +607,14 @@ ifdef CONFIG_CC_STACKPROTECTOR_REGULAR
>     ifeq ($(call cc-option, $(stackp-flag)),)
>       $(warning Cannot use CONFIG_CC_STACKPROTECTOR: \
>   	      -fstack-protector not supported by compiler))
> +    stackp-flag :=
>     endif
>   else ifdef CONFIG_CC_STACKPROTECTOR_STRONG
>     stackp-flag := -fstack-protector-strong
>     ifeq ($(call cc-option, $(stackp-flag)),)
>       $(warning Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: \
>   	      -fstack-protector-strong not supported by compiler)
> +    stackp-flag :=
>     endif
>   else
>     # Force off for distro compilers that enable stack protector by default.
>

Ping again?

-- 
markos


  parent reply	other threads:[~2014-02-20 12:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07 17:15 [PATCH] Makefile: Unset stack-protector gcc flag if it is not supported Markos Chandras
2014-02-13 11:04 ` Markos Chandras
2014-02-20 12:46 ` Markos Chandras [this message]
2014-02-20 12:53   ` Richard Weinberger
2014-02-20 13:53     ` Markos Chandras
2014-02-20 13:57       ` Richard Weinberger

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=5305F928.5070600@imgtec.com \
    --to=markos.chandras@imgtec.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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