From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Openembedded and ld-linux-armhf.so.3
Date: Thu, 03 May 2012 06:52:03 -0700 [thread overview]
Message-ID: <4FA28D83.90604@gmail.com> (raw)
In-Reply-To: <4FA23915.6040604@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/03/2012 12:51 AM, Martin Ertsås wrote:
> Fair point, I was just told that some packages might look at the
> name of the toolchain, and perhaps not give the optimal path for
> hard floats with the name of linux-gnueabi. Clearly some packages
> do actually look at the name of the toolchain, but for most cases
> at least, the only difference will be the hardfloat flag given to
> the compiler. Also seen quite a few toolchains using hardfloats
> which has the hf prefix, to show that this is actually a hardfloat
> toolchain.
some distros may rely on triplet and if it makes into gcc and gcc
starts relying on it we will have to reconsider but at present I dont
see a need to change triplet
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+ijYMACgkQuwUzVZGdMxQoGACfSjsIVwB+uPW/cDbtUbQR87oC
r/gAniC35ygSHDUIe0O1urrsO/w+gcEl
=ZLo8
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-05-03 14:01 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
2012-05-03 7:51 ` Martin Ertsås
2012-05-03 13:52 ` Khem Raj [this message]
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=4FA28D83.90604@gmail.com \
--to=raj.khem@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox