I am having the exact same problem with the same build environment. If I rename /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 to something different then the binary runs no problems. So libcrypto is being statically linked. But why would a statically linked binary care about the system copy of libcrypto?
-- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
