From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Tegra build failure in latest master
Date: Thu, 20 Feb 2014 10:33:38 -0700 [thread overview]
Message-ID: <53063C72.6020506@wwwdotorg.org> (raw)
In-Reply-To: <20140220182652.12778555@lilith>
On 02/20/2014 10:26 AM, Albert ARIBAUD wrote:
> Hi Stephen,
>
> On Thu, 20 Feb 2014 09:35:14 -0700, Stephen Warren
> <swarren@wwwdotorg.org> wrote:
>
>> I the latest u-boot/master (0a8e823ad0c5 "Prepare v2014.04-rc1"),
>> compilation of all Tegra boards fails as below. This is with the ARM
>> cross-compilers from Ubuntu 12.10.
>>
>> [swarren at swarren-lx1 u-boot]$ ./MAKEALL -s tegra
>> Configuring for dalmore board...
>> cc1: error: bad value (armv5) for -march= switch
>> cc1: error: bad value (armv5) for -march= switch
>> /home/swarren/shared/git_wa/tegra-uboot-flasher/u-boot/lib/asm-offsets.c:1:0:
>> error: bad value (armv5) for -march= switch
>> make: *** [lib/asm-offsets.s] Error 1
>> size: './u-boot': No such file
>> cc1: error: bad value (armv5) for -march= switch
>> cc1: error: bad value (armv5) for -march= switch
>> /home/swarren/shared/git_wa/tegra-uboot-flasher/u-boot/lib/asm-offsets.c:1:0:
>> error: bad value (armv5) for -march= switch
>> make: *** [lib/asm-offsets.s] Error 1
>> make: *** Waiting for unfinished jobs....
>
> I've build the whole of ARM with the latest u-boot/master and all
> except venice2 builds fine.
>
> Which version of ARM compilers are you using?
Well, I thought I had CROSS_COMPILE pointing to the ARM cross-compilers
from Ubuntu 12.10. However, I had it set incorrectly:-(
So, false alarm:-)
prev parent reply other threads:[~2014-02-20 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 16:35 [U-Boot] Tegra build failure in latest master Stephen Warren
2014-02-20 17:26 ` Albert ARIBAUD
2014-02-20 17:33 ` Stephen Warren [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=53063C72.6020506@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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