From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [Suggestion] ARM: allmodconfig: about cross compiling failure under i386 ubuntu.
Date: Thu, 22 Aug 2013 11:22:10 +0100 [thread overview]
Message-ID: <20130822102210.GF25647@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130822074524.GS7656@atomide.com>
On Thu, Aug 22, 2013 at 12:45:24AM -0700, Tony Lindgren wrote:
> * Chen Gang <gang.chen@asianux.com> [130821 01:53]:
> > Hello Maintainers:
> >
> > When build arm with allmodconfig under ubuntu i386 with arm-linux-
> > gnueabi-gcc 4.7, as 2.22, it report the errors.
> >
> > Please help check, thanks (the related config file in attachment).
>
> It seems that some make flags may need to be specified separately
> in some makefiles. See the following for some examples:
>
> $ find arch/arm -name Makefile | xargs grep -i flags
>
> I'm getting different errors though, I'm getting:
>
> arch/arm/mach-zynq/hotplug.c:1: error: bad value (cortex-a9) for -mcpu= switch
>
> As probably my compiler does not support the cortex-a9 switch,
> I have gcc version 4.3.5 (Debian 4.3.5-4), tried with v3.11-rc5.
The use of -mcpu with -march is not a good idea anyway - you either use
-mcpu= or you use -march and -mtune.
-mcpu= sets the CPU type, which specifies the instruction architecture
(iow, which instructions can be used) and instruction scheduling behaviour.
-march= sets the architecture only. -mtune= sets the instruction
scheduling behaviour only.
So, that -mcpu= should probably be -mtune=, but if that fails due to
unrecognised instructions, the -march= parameter is wrong.
Even so, if gcc 4.3.5 doesn't support cortex-a9 as a CPU type, and we
want to support that gcc version, the setting of -mtune needs to be
conditionalised. As it is only a scheduling hint, it's probably fine
for it to end up being omitted.
next prev parent reply other threads:[~2013-08-22 10:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 8:26 [PATCH] ARM: OMAP2: add type cast from 'unsigned' to 'signed' Chen Gang
2013-08-21 8:31 ` [PATCH] ARM: OMAP2: remove useless variable 'ret' Chen Gang
2013-08-22 7:17 ` Tony Lindgren
2013-08-22 7:24 ` Chen Gang
[not found] ` <52147E12.4060401@asianux.com>
2013-08-22 7:45 ` [Suggestion] ARM: allmodconfig: about cross compiling failure under i386 ubuntu Tony Lindgren
2013-08-22 9:19 ` Chen Gang
2013-08-22 10:15 ` Chen Gang
2013-08-22 10:22 ` Russell King - ARM Linux [this message]
2013-08-23 1:47 ` Chen Gang
2013-08-23 2:06 ` Chen Gang
2013-08-23 3:04 ` [PATCH] ARM: VExpress: Kconfig: avoid arm6 compatible for ARCH_VEXPRESS Chen Gang
2013-08-23 3:12 ` Chen Gang
2013-08-23 5:51 ` Tony Lindgren
2013-08-23 7:02 ` Chen Gang
2013-08-23 7:15 ` Chen Gang
2013-08-23 8:02 ` [PATCH v2] ARM: VExpress: Makefile: add armv7 flags for inline assmembly code compiling Chen Gang
2013-08-23 8:12 ` Chen Gang
2013-09-23 1:50 ` [PATCH v3] " Chen Gang
2013-08-22 7:14 ` [PATCH] ARM: OMAP2: add type cast from 'unsigned' to 'signed' Tony Lindgren
2013-08-22 7:43 ` Chen Gang
2013-08-22 7:47 ` [PATCH v2] ARM: OMAP2: use 'int' instead of 'unsigned' for variable 'gpmc_irq_start' Chen Gang
2013-08-22 7:57 ` Tony Lindgren
2013-08-22 8:01 ` Chen Gang
2013-08-22 8:32 ` Tony Lindgren
2013-08-22 8:59 ` Chen Gang F T
2013-08-23 5:48 ` Tony Lindgren
2013-08-23 6:14 ` Chen Gang
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=20130822102210.GF25647@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).