Configs parsing errors on x86_64-unknown-linux-musl

[ghost]

The build for x86_64-unknown-linux-musl cannot parse configs.

Example:

vector.toml:

[sources.stdin]
  type = "stdin"

[sinks.console]
  type = "console"
  inputs = ["stdin"]

$ curl -sSf https://packages.timber.io/vector/nightly/vector-nightly-x86_64-unknown-linux-musl.tar.gz | tar xzf -
$ ./vector-0.3.0-201-gd723a95/bin/vector --config vector.toml 
Aug 23 18:27:21.282  INFO vector: Log level "info" is enabled.
Aug 23 18:27:21.282  INFO vector: Loading config. path="vector.toml"
Aug 23 18:27:21.283 ERROR log: Configuration error: unknown variant `stdin`, there are no variants for key `sources.stdin.type`  log.target="vector" log.module_path="vector" log.file="src/main.rs" log.line=299
Aug 23 18:27:21.283 ERROR vector: Configuration error: unknown variant `stdin`, there are no variants for key `sources.stdin.type`

I'm not sure what exactly causes this, but it should not be MUSL itself, as the build for Alpine from #669 works.

[lukesteensen]

That is very weird. I wonder if there's something that causes typetag to fail to register the different trait implementations?

[ghost]

typetag uses crate impl which is proc macro, so it seems to have something to do with support of proc macro for fully static builds.

It looks like proc macro requires working dynamic linker, even for static builds, but -static flag is always added to Rust linker’s flags. I will try to remove always added -static flag for Rust linker and see would it help or not.