From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: gcc-cross-initial Failure
Date: Fri, 05 Apr 2013 17:36:06 +0100 [thread overview]
Message-ID: <515EFD76.2090009@communistcode.co.uk> (raw)
In-Reply-To: <D19A794A-8644-4443-9628-2B137F2BC89F@gmail.com>
On 05/04/2013 17:15, Khem Raj wrote:
> On Apr 5, 2013, at 7:03 AM, Jack Mitchell <ml@communistcode.co.uk> wrote:
>
>> Doing my usual git master pull and rebuild today, resulted in gcc-cross-initial failing to build.
>>
>> Please find the log attached, does anyone know what could have caused it? I recently changed the TUNES, so could something not be being re-built when it should be?
>
> it could be gcc is crashing on you. What TUNEs did you change
I build for the beaglebone and I changed them in line with your default
beaglebone build patch you posted a week or so ago. I think it moved it
form soft to hard float possibly...
>
>> Cheers,
>> Jack.
>>
>> --
>>
>> Jack Mitchell (jack@embed.me.uk)
>> Embedded Systems Engineer
>> http://www.embed.me.uk
>>
>> --
>>
>> <log.do_compile.840>_______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2013-04-05 16:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 14:03 gcc-cross-initial Failure Jack Mitchell
2013-04-05 16:15 ` Khem Raj
2013-04-05 16:36 ` Jack Mitchell [this message]
2013-04-05 17:03 ` Khem Raj
2013-04-08 8:52 ` Jack Mitchell
2013-04-08 9:06 ` Jack Mitchell
2013-05-08 2:23 ` gcc-cross-initial Failure (is a meta-aarch64 screw up) Khem Raj
2013-05-08 5:13 ` [Angstrom-devel] " Koen Kooi
2013-05-08 6:43 ` Marcin Juszkiewicz
2013-05-08 8:22 ` Marcin Juszkiewicz
2013-05-14 21:43 ` Khem Raj
2013-05-15 2:39 ` Marcin Juszkiewicz
2013-05-08 9:55 ` Jack Mitchell
2013-04-09 14:23 ` gcc-cross-initial Failure Khem Raj
2013-04-05 19:07 ` Elvis Dowson
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=515EFD76.2090009@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.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 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.