All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin Ertsås" <martiert@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Openembedded and ld-linux-armhf.so.3
Date: Wed, 02 May 2012 11:35:17 +0200	[thread overview]
Message-ID: <4FA0FFD5.6080201@gmail.com> (raw)
In-Reply-To: <CAMKF1spxTuL1b6yMN=N68tq=MLfJGT9jmgd6VzHmY+TwZvNLsA@mail.gmail.com>

On 05/01/12 14:32, Khem Raj wrote:
> On Mon, Apr 30, 2012 at 11:44 PM, Martin Ertsås <martiert@gmail.com> wrote:
>> On 05/01/12 00:05, Khem Raj wrote:
>>> On Fri, Apr 27, 2012 at 5:38 AM, Martin Ertsås<martiert@gmail.com>  wrote:
>>>> I'm working on a pandaboard with OMAP4460. Were trying to use the newest
>>>> PVR drivers, which conforms to the result that arose from
>>>> https://wiki.linaro.org/OfficeofCTO/HardFloat/LinkerPathCallApr2012
>>>>
>>>> We have applied the patch at the bottom of that page gcc, and also a
>>>> patch for making eglibc make ld-linux-armhf, and load ld-linux-armhf
>>>> instead of ld-linux. Problem is, this gives us a kernel panic when it
>>>> tries to run init.
>>> interesting bits are why kernel panics ?
>>> what error do you get from kernel ?
>>> is it some illegal instruction or something like that ?
>>> Do you have VFP enabled
>>>
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>> Found out the problem why kernel panics. The patches I posted were the
>> correct ones, but before this I used
>>
>> SYSLIB_PATH or something before "/lib/ld-linux-armhf.so.3", so the output
>> actually was /lib/lib/ld-linux-armhf.so.3
>>
> ok good. I would be interested if you test the patchset i posted
> it will help a lot
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
The patches posted seems to be working fine. I at least didn't have any
problems with them.



  parent reply	other threads:[~2012-05-02  9:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 12:38 Openembedded and ld-linux-armhf.so.3 Martin Ertsås
2012-04-27 15:04 ` Mark Hatle
2012-04-27 15:08   ` Martin Ertsås
2012-04-29  2:40 ` Khem Raj
2012-04-30  6:00   ` Martin Ertsås
2012-04-30 23:00     ` Khem Raj
2012-04-30 22:05 ` Khem Raj
2012-05-01  6:44   ` Martin Ertsås
2012-05-01 12:32     ` Khem Raj
2012-05-01 12:43       ` Martin Ertsås
2012-05-02  9:35       ` Martin Ertsås [this message]
2012-05-02 21:06         ` Khem Raj
2012-05-03  6:48           ` Martin Ertsås
2012-05-03  7:48             ` Koen Kooi
2012-05-03  7:51               ` Martin Ertsås
2012-05-03 13:52                 ` Khem Raj
2012-05-01  5:06 ` Khem Raj

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=4FA0FFD5.6080201@gmail.com \
    --to=martiert@gmail.com \
    --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.