From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Openembedded and ld-linux-armhf.so.3
Date: Thu, 03 May 2012 09:48:57 +0200 [thread overview]
Message-ID: <jntd9a$pip$1@dough.gmane.org> (raw)
In-Reply-To: <4FA22A58.3040100@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 03-05-12 08:48, Martin Ertsås schreef:
> On 05/02/12 23:06, Khem Raj wrote:
>> On 05/02/2012 02:35 AM, Martin Ertsås wrote:
>>> The patches posted seems to be working fine. I at least didn't have
>>> any problems with them.
>>
>>
>> thanks for trying them out. GCC patch is final but eglibc patch I still
>> got to improve that its not final version yet.
>
> No problem. Is there also plans for renaming the toolchains created to
> arm-none-linux-gnueabihf when using hardfloats?
What's the point in that? Renaming the toolchain won't grant it magical
powers and setting a targetvendor is perfectly valid.
I've seen too many presentations this year at ELC and Collab where someone
says "renaming the toolchain fixed it" when they actually mean "using a
bare-metal toolchain for userspace doesn't really work".
Just look at the building the kernel with LLVM talk, a third of Marks
presentation was about challenges with calling the right toolchain with the
right arguments.
</rant>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQIcBAEBAgAGBQJPojhnAAoJEHZqAkdh1vT63s0P/2yoPsNlXRcLHGfeH7SCtEHP
2fxZMUmxRzZjPF/rwqWCBwyHEseGtL15AfetHK2Ylvi+Pzw0Z+d5GpNlzwj4pBNo
JguZ6+4xo6Kd0mKxk9PN99ebcPYsQo23Hqs6Bpk6roYJNoBtmqUusZ/M0VoS+k/E
7KwUwYUjL1mONDpKWjPkuC2apkjjI/XQ/a9r0RlQ8qzKaMJDg8rJkRFV8Yzzrlxu
0DRjs+EyTjM/VUGXTxdnjsQwV4lbZC0bw9rZhISsXwG5JFEJVjkZ9pMMexqkAX7C
pE6YBWxAZ8g3ZAWd9AVwne4xR99xCPtYyqVr3smeEi+mxu+SLkZFaZvyFLhHsaBj
uRM9sKinrnnUdpWxCZ4qoNJ4j0h2tT7/wqBXsNyK5+0XmfJba58ZfyY2t8xSi4qn
d89gQ/iYTHCDpW+7Rogp5WNzhS2Y8a+ecvbP1zQHZitEfaA4TXUxB1x9hsqWVuT8
2RbVAIMgytCrj9sshdlAaWkFReF7CKSp7zMwn3FLCKFPLSsS7P260MQRWqpGJXjS
yPTaFgFeWBRbSOMtg8l2LP5gDVuyg1BrdmiRVycX/gOgj4ZTfMPOooyAWttVMj95
4cZO1yiCU4de8Fd2+8QW4KrUJhnKcI+pHZn0pP4qHMuKUoh+o0dbCz/O7OCK9now
VqIPweynKVrQ5SF8ZhYa
=F3G4
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-05-03 7:58 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
2012-05-02 21:06 ` Khem Raj
2012-05-03 6:48 ` Martin Ertsås
2012-05-03 7:48 ` Koen Kooi [this message]
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='jntd9a$pip$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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