From: Gary Thomas <gary@mlbassoc.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Poky & armv5te
Date: Wed, 02 Feb 2011 11:00:07 -0700 [thread overview]
Message-ID: <4D499BA7.8060604@mlbassoc.com> (raw)
In-Reply-To: <4D49976E.5030800@linux.intel.com>
On 02/02/2011 10:42 AM, 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.
As far as 4.5.1 goes, the kernel crashes immediately on bootup.
I didn't diagnose this much as it seemed to be similar to the
problem reported 2011-01-31 18:52GMT
'Kernel Panics on armv4t with gcc.4.5.1'
To that end, I tried to use the 4.5.2 patches from Nitin
which failed to build at all (reported this morning)
Do you have a tree with your changes? I could try my armv5te
overlay to see what happens.
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-02-02 18:00 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 [this message]
2011-02-02 18:00 ` Richard Purdie
2011-02-02 18:27 ` Gary Thomas
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=4D499BA7.8060604@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=dvhart@linux.intel.com \
--cc=poky@lists.pokylinux.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