[MLton-devel] mlton/doc CHANGES,1.62,1.63

[Henry Cejtin]

I agree that 1 is probably the way to go.  An advantage would be that the
resulting executables would not depend on the shared gmp library being on
the machine you are going to run the executable on.  One disadvantage is that
it means if that machine has a version optimized for the CPU it uses, you
will not take advantage of it.  (I would say that it is still a net win.)
As to how to do this, I remember that the linker walks down the search path
(set in /etc/ld.so.conf) and first looks for a .so file and then for a .a
(unless you specify -static).  A bit of a pain.  What would be nice would be
if you could do
	-static -lgmp -dynamic
to just have it link with the static gmp, but this does not work.

_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel