From: Scott Wood <oss@buserror.net>
To: Sam Bobroff <sam.bobroff@au1.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: michaele@au1.ibm.com
Subject: Re: [PATCH 1/1] powerpc: Detect broken or mismatched toolchains
Date: Mon, 22 Feb 2016 20:05:01 -0600 [thread overview]
Message-ID: <1456193101.2463.133.camel@buserror.net> (raw)
In-Reply-To: <5c8ce41d4341aa5c0698abbc0284359a789d2334.1456117980.git.sam.bobroff@au1.ibm.com>
On Mon, 2016-02-22 at 16:13 +1100, Sam Bobroff wrote:
> It can currently be difficult to diagnose a build that fails due to
> the compiler, linker or other parts of the toolchain being unable to
> build binaries of the type required by the kernel config. For example
> using a little endian toolchain to build a big endian kernel may
> produce:
>
> as: unrecognized option '-maltivec'
>
> This patch adds a basic compile test and error message to
> arch/powerpc/Makefile so that the above error becomes:
>
> *** Sorry, your toolchain seems to be broken or incorrect. ***
> Make sure it supports your kernel configuration (ppc64).
>
> Signed-off-by: Sam Bobroff <sam.bobroff@au1.ibm.com>
> ---
How is this more useful than getting to actually see the way in which the
toolchain (or the CFLAGS) is broken?
-Scott
next prev parent reply other threads:[~2016-02-23 2:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 5:13 [PATCH 1/1] powerpc: Detect broken or mismatched toolchains Sam Bobroff
2016-02-23 2:05 ` Scott Wood [this message]
2016-02-23 4:59 ` Sam Bobroff
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=1456193101.2463.133.camel@buserror.net \
--to=oss@buserror.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michaele@au1.ibm.com \
--cc=sam.bobroff@au1.ibm.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;
as well as URLs for NNTP newsgroup(s).