The default falls back to shared as you note. It also links the implicit libraries like glibc dynamically.
--static forces everything to be static, including turning off libSegFault if necessary, and failing if anything else isn't available statically. The build process falls back to shared libraries when compilation tests with static libraries fail. These can be seen with --debug-configuration and looking at the commands that try to link libraries statically. On 04/05/2016 08:34 AM, Mathias Müller wrote: > @all In what circumstances does the build process fall back to "shared" > with the default settings? Why is it not "--static" that is the default? _______________________________________________ Moses-support mailing list Moses-support@mit.edu http://mailman.mit.edu/mailman/listinfo/moses-support
