The former is the GNU compiler, targeting the GNU C library, glibc, and only supports (AFAIK) dynamic linking – I'm unsure if this a fundamental limition of how glibc is compiled/designed, or if it's a licencing issue (or similar). We have a choice between x86_64-unknown-linux-gnu and x86_64-unknown-linux-musl.

Note that it's not the same feature that I use in my other post, for reasons that should become apparant. This was initially done with the dependency line actix-web =, which will be important later on. So what do I do? Well, there has been a bit written about cross-compiling Rust here and here, for example, so let's give that a go! Notes If possible, I want to be able to do everything on macOS directly - I don't want to have to boot a Linux VM just to 'cross-compile', for example.

I'm doing development on macOS, so I need to cross-compile.

This means that I need to build a statically-linked binary.PAS builds and supports the container itself - I can't install any deb files on it, for example.PAS runs all applications on a Linux container (by default - there is Windows support, but I'm not interested in that).PWS is a hosted version of Pivotal Application Service (PAS).I was deploying to PWS, because I work for Pivotal and have a small amount of free credit to use on the platform.However, when it came time to deploy it, I ran into some major issues: Writing the app itself wasn't too hard, and I managed to get it working with only minor issues (the biggest issue was noticing that I only had my IP address from my previous ISP whitelisted with Mailgun!) If you're looking for a simple set of instructions, check the conclusion - but be aware that you might need to read the rest of the post to understand why these things are needed. As I mentioned in another story, I wrote a simple Rust app to handle the posting of a simple contact form from this blog.

Musl cross compiler