From: Michal Marek <mmarek@suse.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Behan Webster <behanw@converseincode.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Makefile: Fix unrecognized cross-compiler command line options
Date: Mon, 09 Jun 2014 23:36:16 +0200 [thread overview]
Message-ID: <539628D0.2090702@suse.cz> (raw)
In-Reply-To: <1401177252-11919-1-git-send-email-geert@linux-m68k.org>
Dne 27.5.2014 09:54, Geert Uytterhoeven napsal(a):
> On architectures that setup CROSS_COMPILE in their arch/*/Makefile
> (arc, blackfin, m68k, mips, parisc, score, sh, tile, unicore32, xtensa),
> cc-option and cc-disable-warning may check against the wrong compiler,
> causing errors like
>
> cc1: error: unrecognized command line option "-Wno-maybe-uninitialized"
>
> if the host gcc supports a compiler option, while the cross compiler
> doesn't support that option.
>
> Move all logic using cc-option or cc-disable-warning below the inclusion
> of the arch's Makefile to fix this.
>
> Introduced by
> - commit e74fc973b6e531fef1fce8b101ffff05ecfb774c ("Turn off
> -Wmaybe-uninitialized when building with -Os"),
> - commit 61163efae02040f66a95c8ed17f4407951ba58fa ("kbuild: LLVMLinux:
> Add Kbuild support for building kernel with Clang").
>
> As -Wno-maybe-uninitialized requires a quite recent gcc (gcc 4.6.3 on
> Ubuntu 12.04 LTS doesn't support it), this only showed up recently (gcc
> 4.8.2 on Ubuntu 14.04 LTS does support it).
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Applied to kbuild.git#kbuild, thanks.
Michal
prev parent reply other threads:[~2014-06-09 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 7:54 [PATCH] Makefile: Fix unrecognized cross-compiler command line options Geert Uytterhoeven
2014-06-09 21:36 ` Michal Marek [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=539628D0.2090702@suse.cz \
--to=mmarek@suse.cz \
--cc=arnd@arndb.de \
--cc=behanw@converseincode.com \
--cc=geert@linux-m68k.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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