Even if you were to use IA32EL, you would still need ia32 binaries. IA32EL is just a different way to execute x86 binaries, but you still need them.
Pedro
-----Original Message-----
From: linux-ia64-owner@xxxxxxxxxxxxxxx [mailto:linux-ia64-owner@xxxxxxxxxxxxxxx] On Behalf Of Émeric MASCHINO
Sent: Thursday, May 22, 2014 16:03
To: linux-ia64@xxxxxxxxxxxxxxx
Subject: How to deal with ia32 binary support nowadays?
Hi,
Tony removed support of ia32 binaries back in 2010. ia32 support was supposedly broken since Al Viro killed altroot in 2008 [2]. I've no clue what altroot is and what's its relationship with ia32 support, but even without altroot, x86_64 still can execute ia32 binaries, a
(large?) part of the ia32 support coming from ia64 [3]. How is that
x86_64 can run ia32 binaries and no more ia64? There was also talk about merging ia64 implementation with x86_64 one some times ago [4], but I don't know how all this ended (by copying part of ia64 implementation into x86_64 as alluded to earlier? In this case, it's code duplication, not merge).
An alternative is using Intel's proprietary IA-32 EL software, that cannot be found anymore on Earth...
How do you deal with (rare) ia32 binaries on ia64 nowadays?
Émeric
[1] http://marc.info/?l=linux-ia64&m=126565735012367&w=2
[2] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7f2da1e7d0330395e5e9e350b879b98a1ea495df
[3] http://marc.info/?l=linux-ia64&m=126665829806428&w=2
[4] http://marc.info/?l=linux-ia64&m=114851556409633&w=2
--
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
��.n��������+%������w��{.n�����{��&�����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
|