From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Problem with new image-prelink
Date: Wed, 14 Sep 2011 09:30:26 -0500 [thread overview]
Message-ID: <4E70BA82.60606@windriver.com> (raw)
In-Reply-To: <840A81C1B782724A8EB52725BD519EFF18EAAF@MBX20.4emm.local>
On 9/13/11 8:33 PM, James Limbouris wrote:
>> -----Original Message-----
>> From: openembedded-core-bounces@lists.openembedded.org
>> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
>> Mark Hatle
>> Sent: Wednesday, 14 September 2011 8:52 AM
>> To: openembedded-core@lists.openembedded.org
>> Subject: Re: [OE-core] Problem with new image-prelink
>>
>> Please try the new version of the prelinker. I just sent a pull request for it,
>> but there was a missing typecast on a printf. This was causing problems on
>> various systems, and likely could be causing the issue that you observed on
>> ARM
>> as well.
>>
>> I did build the latest version for the ARM target, and successfully ran it there
>> under QEMU.
>>
>> --Mark
>
> Thanks Mark - all working, on host and target.
Does this also resolve the initial issue you found, QT failing to work after
prelinking?
If not, I'd like to open a new defect on it and see if we can figure out the
cause still...
--Mark
> James
>
> _______________________________________________
> 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:[~2011-09-14 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 3:34 Problem with new image-prelink James Limbouris
2011-09-09 15:57 ` Mark Hatle
2011-09-12 1:39 ` James Limbouris
2011-09-12 14:50 ` Mark Hatle
2011-09-13 2:58 ` James Limbouris
2011-09-13 9:16 ` Phil Blundell
2011-09-14 0:52 ` Mark Hatle
2011-09-14 1:33 ` James Limbouris
2011-09-14 14:30 ` Mark Hatle [this message]
2011-09-15 1:01 ` James Limbouris
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=4E70BA82.60606@windriver.com \
--to=mark.hatle@windriver.com \
--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.