Since libGMP is not actually required by Amakuni, it was interesting to see why it would produce an error when running the Amakuni binary without this library available. It appears that when MLton is built, it can be either built statically against libGMP or dynamically against libGMP. When built statically against libGMP, the necessary code for this library is included with the build of MLton. However when built against libGMP dynamically, this file is only referenced from its location on the machine currently building MLton. This means that when any binary is built with MLton, it tries to find libGMP even though it may not necessarily use any code from it.
A possible solution to this may be to rebuild MLton statically against libGMP and see if this problem persists.
It should be noted that while reported during testing of the Mac PKG, this problem also appeared on the Ubuntu system if libGMP was not available.
Since libGMP is not actually required by Amakuni, it was interesting to see why it would produce an error when running the Amakuni binary without this library available. It appears that when MLton is built, it can be either built statically against libGMP or dynamically against libGMP. When built statically against libGMP, the necessary code for this library is included with the build of MLton. However when built against libGMP dynamically, this file is only referenced from its location on the machine currently building MLton. This means that when any binary is built with MLton, it tries to find libGMP even though it may not necessarily use any code from it.
A possible solution to this may be to rebuild MLton statically against libGMP and see if this problem persists.
It should be noted that while reported during testing of the Mac PKG, this problem also appeared on the Ubuntu system if libGMP was not available.