This is an apparent ABI issue encountered with the ldc2 compiler snap package when running on Ubuntu 14.04. This is probably a rather esoteric issue, but I thought I'd record it in case there is something that can be done snapcraft-side: I imagine it might carry some relevance to any snap package exposing a library to be linked against. ldc2 is a compiler for the D programming language, and the D standard library includes a copy of zlib, which is built from C source before being statically linked into the `libphobos2-ldc.a` static library included in the final snap package. In theory this allows the user to write D programs using zlib's capabilities. However, when trying to compile a simple zlib-using program on Ubuntu 14.04, linking fails with the following message: /usr/bin/gcc zlibtest.o -o zlibtest -L/snap/ldc2/x1/bin/../lib -lphobos2-ldc -ldruntime-ldc -Wl,--gc-sections -lrt -ldl -lpthread -lm -m64 /usr/bin/ld: /snap/ldc2/x1/bin/../lib/libphobos2-ldc.a(zutil.c.o): unrecognized relocation (0x2a) in section `.text' /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status Error: /usr/bin/gcc failed with status: 1 This matches the error message described in the following bug: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1545653 ... where problems were encountered trying to link against a library compiled with a later binutils than was available on the host system. This would suggest that there may be a problematic mismatch between the binutils used to build snap packages in a `snapcraft cleanbuild`, versus that available on 14.04. An example program to generate the issue can be found here: https://github.com/ldc-developers/ldc2.snap/issues/17