From: Gary Thomas <gary@mlbassoc.com>
To: Phil Blundell <pb@pbcl.net>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Recovering GCC 4.8
Date: Fri, 19 Feb 2016 09:34:10 +0100 [thread overview]
Message-ID: <56C6D382.9090900@mlbassoc.com> (raw)
In-Reply-To: <1455868969.2039.44.camel@pbcl.net>
On 2016-02-19 09:02, Phil Blundell wrote:
> On Fri, 2016-02-19 at 07:37 +0100, Gary Thomas wrote:
>> | checking for suffix of object files... configure: error: in
>> `/local/p0381_2016-02-19/tmp/work/cortexa7hf-neon-amltd-linux-gnueabi/libgcc-initial/4.8.4-r0/gcc-4.8.4/build.arm-amltd-linux-gnueabi.arm-amltd-linux-gnueabi/libgcc':
>> | configure: error: cannot compute suffix of object files: cannot compile
>> | See `config.log' for more details.
>
> I suspect you probably have some or other option set in CC or CFLAGS
> that gcc-4.8 doesn't support. What does it say in config.log?
It's complaining about an illegal -march=armv7ve, which seems to have
been added since I last built for this machine with GCC 4.8:
commit c6a19917ec5350cdfc4053d14462609782613bbc
Author: Martin Jansa <Martin.Jansa@gmail.com>
Date: Tue Oct 6 17:08:59 2015 +0200
arch-armv7ve: add tune include for armv7ve and use it from cortexa7 and cortexa15
I'll see what I can do with this. Duh, I should have looked at
the config.log before raising flags!
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2016-02-19 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 6:37 Recovering GCC 4.8 Gary Thomas
2016-02-19 8:02 ` Phil Blundell
2016-02-19 8:34 ` Gary Thomas [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=56C6D382.9090900@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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.