Last edited by saturdaywasokay (2014-05-18 01:56:43)
Why Icecat? Iceweasel has the same sauce of philosophical debate, security updates (Icecat was last updated 7 months ago) and FWIW, Debian-specific patches.
But if you must use it - normally I'd say LD_LIBRARY_PATH (see signature) but with intertwined software like browsers that's hard. What's left is recompiling from source, trying the 32bit variant, or dist-upgrade to testing/sid.
Last edited by Alad (2014-05-17 12:40:04)
IMHO using the 32bit version via multiarch would do nothing to solve the problem
Apart from Alad's suggestion to use LD_LIBRARY_PATH, which is by no means a sane way to run a program of that size, compiling Icecat might be impossible for you – it's essentially a flavour of Firefox, and Firefox needs >= 4GB of RAM to compile (think 6-12GB) (otherwise it might not compile correctly!) and a reasonably fast processor (think at least i5/i7 class) if you don't want to wait too long. It definitely takes ~30 minutes to an hour on a powerful system (definitely longer than building the kernel).
Upgrading to testing/unstable is the easiest way. Alternatively, you could create a VM using qemu-kvm or virtualbox in which you run Debian Unstable + Icecat.