From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Poky & armv5te
Date: Wed, 02 Feb 2011 11:27:59 -0700 [thread overview]
Message-ID: <4D49A22F.6030003@mlbassoc.com> (raw)
In-Reply-To: <1296669636.1544.4238.camel@rex>
On 02/02/2011 11:00 AM, Richard Purdie wrote:
> On Wed, 2011-02-02 at 09:42 -0800, Darren Hart wrote:
>> On 02/02/2011 09:24 AM, Gary Thomas wrote:
>>> I'd like to use Poky with my OMAP-L138 which is armv5te
>>> Sadly today, this just isn't a go because of GCC issues.
>>> I've tried all the combinations which are in the trees
>>> (main& contrib) with no luck:
>>> * 4.3.3 - fails to build GCC
>>> * 4.5.1 - everything builds but kernel crashes
>>> * 4.5.2 - fails to build GCC
>>>
>>> Am I totally out of luck?
>>
>> What are you running into? I've recently backported some changes in
>> support of the Beagleboard (armv7-a) which were necessary to build with
>> 4.5.1 and our 2.21 binutils.
>
> Those wouldn't affect armv5. What puzzles me is that qemuarm is
> effectively an armv5 like system and those do build and boot in qemu.
>
> When you managed images above for 4.5.1 did you try using a known good
> kernel with our userspace? I'm wondering if we can narrow it to a kernel
> issue?
Not sure I got that far, but I'll check it out.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-02-02 18:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 17:24 Poky & armv5te Gary Thomas
2011-02-02 17:42 ` Darren Hart
2011-02-02 18:00 ` Gary Thomas
2011-02-02 18:00 ` Richard Purdie
2011-02-02 18:27 ` Gary Thomas [this message]
2011-02-02 22:17 ` Gary Thomas
2011-02-03 0:21 ` Richard Purdie
2011-02-03 14:32 ` Bruce Ashfield
2011-02-03 14:41 ` Gary Thomas
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=4D49A22F.6030003@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@lists.pokylinux.org \
--cc=richard.purdie@linuxfoundation.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.