From: Guenter Roeck <private@roeck-us.net>
To: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Cc: Vineet Gupta <vgupta@synopsys.com>
Subject: arc build failures in -next due to ARCv2 patch
Date: Fri, 26 Jun 2015 16:58:49 -0700 [thread overview]
Message-ID: <558DE739.4020804@roeck-us.net> (raw)
Hi,
my arc test builds in -next now fail with
cc1: error: unrecognized command line option "-mno-ll64"
make[2]: *** [scripts/mod/empty.o] Error 1
make[1]: *** [scripts/mod] Error 2
make[1]: *** Waiting for unfinished jobs....
cc1: error: unrecognized command line option "-mno-ll64"
make[1]: *** [kernel/bounds.s] Error 1
due to commit 'ARCv2: Support for ARCv2 ISA and HS38x cores'.
This is with gcc 4.8.3 built from buildroot.
Do I now need a new compiler / toolchain to build the kernel ?
Any chance to make this change compatible to work with older
compilers ?
Thanks,
Guenter
next reply other threads:[~2015-06-26 23:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 23:58 Guenter Roeck [this message]
2015-06-27 11:42 ` arc build failures in -next due to ARCv2 patch Vineet Gupta
2015-06-27 14:16 ` Guenter Roeck
2015-06-28 15:16 ` Vineet Gupta
2015-08-31 10:35 ` ARCv2 testing exposure (Re: arc build failures in -next due to ARCv2 patch) Vineet Gupta
2015-08-31 13:58 ` Guenter Roeck
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=558DE739.4020804@roeck-us.net \
--to=private@roeck-us.net \
--cc=linux-next@vger.kernel.org \
--cc=vgupta@synopsys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.