From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: H1940 Boot Issues -> Executable Build Problems?
Date: Wed, 05 Jan 2011 09:33:06 +0100 [thread overview]
Message-ID: <ig1ac2$ej0$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTimbxOoZQRPQ+MsSNT++aXYnJsta8VmOA_Nbmc-k@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
That looks suspiciously like
http://www.flickr.com/photos/quimgil/478715643/ :)
On 05-01-11 08:42, Khem Raj wrote:
> here is updated patch
>
>
>
> On Tue, Jan 4, 2011 at 10:46 PM, Khem Raj <raj.khem@gmail.com> wrote:
>> On Tue, Jan 4, 2011 at 7:32 PM, Russell Morris <openembedded@rkmorris.us> wrote:
>>> Hi,
>>>
>>>
>>>
>>> A bit more info to try and help out here - as I'm fighting with this as best I can, but it's still kicking my butt ... :-).
>>>
>>>
>>>
>>> It really does look like the executable that is being created is not build for the arm920t (armv4t). I have tried to run the executable on the target, and also with a modified version of qemu - and neither one works. If I tell qemu that the target is an arm920t the executable will not run, but if I let it be the default qemu-arm it runs just fine.
>>>
>>>
>>>
>>> Has anyone else been able to get an OE build to run on an arm920t (armv4t) processor?
>>>
>>>
>>
>> OK you seem to be one patient guy :) Here is totally untested patch
>> for gcc. Please apply it on top of your openembedded. Then use
>> DISTRO=minimal
>> or any other distro that uses gcc 4.5 and build OE from scratch again
>> and see if that helps and report back.
>>
>> Thanks
>> -Khem
>>
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNJCzCMkyGM64RGpERAvW/AKCTiQztYmWbEMLOvxHWtP0TrfGSwgCgnIdQ
Df+XY7rjrMPTZKaMxfAXwRg=
=JXQ8
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-01-05 8:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 3:32 H1940 Boot Issues -> Executable Build Problems? Russell Morris
[not found] ` <AANLkTim22AbOed09n1Ez6A2gtJhnjUDm3Ksv+tRDnn=8@mail.gmail.com>
2011-01-05 7:42 ` Khem Raj
2011-01-05 8:33 ` Koen Kooi [this message]
2011-01-05 8:49 ` Khem Raj
2011-01-05 14:47 ` Russell Morris
2011-01-05 8:47 ` Koen Kooi
[not found] ` <1294238916100625500@rkmorris.us>
2011-01-05 15:11 ` Phil Blundell
2011-01-05 17:45 ` Khem Raj
2011-01-05 17:20 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2011-01-08 14:52 Russell Morris
2011-01-05 18:49 Russell Morris
2011-01-05 20:23 ` Khem Raj
2011-01-05 23:07 ` Russell Morris
[not found] ` <1294288661406628500@rkmorris.us>
2011-01-06 6:15 ` Khem Raj
2011-01-06 14:30 ` Russell Morris
2011-01-06 7:54 ` Koen Kooi
[not found] ` <AANLkTimaX4kPer1-+UFRq-80PBFrcT8oxorC=SHwHWFU@mail.gmail.com>
2011-01-06 14:28 ` Russell Morris
[not found] ` <201101061721.30643.anarsoul@gmail.com>
[not found] ` <1294330448552193500@rkmorris.us>
2011-01-06 16:32 ` Vasily Khoruzhick
2011-01-06 16:50 ` Russell Morris
[not found] ` <201101062040.16993.anarsoul@gmail.com>
2011-01-06 23:41 ` Khem Raj
2011-01-01 18:34 openembedded
2011-01-02 6:44 ` Khem Raj
2011-01-02 12:34 ` openembedded
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='ig1ac2$ej0$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@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.