From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: Openembedded and ld-linux-armhf.so.3
Date: Fri, 27 Apr 2012 10:04:16 -0500 [thread overview]
Message-ID: <4F9AB570.4090906@windriver.com> (raw)
In-Reply-To: <4F9A932F.1020400@gmail.com>
On 4/27/12 7:38 AM, Martin Ertsås wrote:
> Hi.
>
> 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. Linking ld-linux.so.3 to ld-linux-armhf.so.3 does not
> work, and we're kind of in the dark as to what is missing.
>
> We tried fixing this by renaming the toolchain to be
> arm-none-linux-gnueabihf instead of arm-none-linux-gnueabi, as we heard
> this might be a problem with hardfloats, but this needed a lot of extra
> patches, and some patchwork on other packages like openssl and shadow.
>
> My question is, are there any ongoing plans to fix this, and make sure
> that if we have set hard float we make ld-linux-armhf in openembedded?
>
> For the record we are using eglibc2.15 and gcc4.6 from openembedded-core.
The ARM EABI + HF isn't well tested (to my knowledge) of oe-core. I was under
the impressions a few people did use it, and it was working successfully for
them. (Generally speaking people seem to agree that there is a place for ARM
EABI + HF, but the performance increase to the couple of items where it helps is
generally not worth the pain of incompatibility with the core ARM EABI. Thus
it's not used very much in OE.)
Could you verify that the stock configuration (without any of the changes you
described above) is working and will boot w/o a kernel panic at init?
If so then it'll be easier to help you track down the particulars of the ld.so
name change and related items.
--Mark
> Best regards
> Martin Ertsaas
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2012-04-27 15:13 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 [this message]
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
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=4F9AB570.4090906@windriver.com \
--to=mark.hatle@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox