Linux deployment requirements for GHC-produced binaries

[Yitzchak Gale]

Hi Brandon,

Thanks for your response and explanation.

I wrote:
>> [For] GHC-compiled binaries...
>> what are the exact requirements we need to communicate
>> to our customers?

You wrote:
> Ideally you would use `ldd` on
> binaries to determine other dynamic dependencies
> that must be communicated

ldd just says "not a dynamic executable".

When run against ghc itself, ldd gives a list of 11 dynamic
libraries, and for each of them the specific binary version
of the library that it linked against on my own particular
machine.

Does the machine on which we run the GHC-compiled
binary need every single one of these libraries in order
to run?

Here is the list of libraries - identical for both
GHC 7.4.2 and GHC 7.6.3:

linux-vdso.so.1
libncursesw.so.5
librt.so.1
libutil.so.1
libdl.so.2
libgmp.so.3
libm.so.6
libpthread.so.0
libc.so.6
libtinfo.so.5
/lib64/ld-linux-x86-64.so.2

Thanks,
Yitz