ARMv4 vs ARMv6

[Andy Green]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:

| Your application will depend on some library.  The dependency is
expressed as a
| library package name.  Two packages (one armv4, one armv6) provide this
| library.  Either of the two will fulfill that dependency.  On an armv6
device,
| opkg will prefer the armv6 over the armv4 from the feed.  An armv4
device will
| not even look at the armv6 feed and thus only see the armv4 package
and install
| it.  so by default you should get whatever is best for your device.
|
| The difference to i386/x86_64 is exactly this:
| * x86_64 application cannot link i386 lib
| * i386 application cannot link x86_64 libt
| * armv6 application can link armv4 lib
| * armv4 application can link armv6 lib

Alright, it's very clear now, thanks for taking the time to explain
Alastair too.

The heuristic that opkg will prefer v6 over v4 when it can have both is
the last part that wasn't spelt out, that even takes care if you have
both v4 and v6 dependencies on the same lib that updates give you a
consistent result.

So I guess we just have to figure out how to offer a single unified
toolchain.

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkj4Sr0ACgkQOjLpvpq7dMoVPACffnap1csXBQRQA6azdtcaR6Ux
54MAnRUu/znha6tp66UgFedsVFOswR8y
=QAwC
-----END PGP SIGNATURE-----