Attribution when distributing binaries linked with wild?

[garpin7]

The MIT license and Apache 2.0 license require attribution. If I link a C executable with wild, do I have to include the wild license files when distributing the binaries? (if the C standard libraries are not included)

The LLVM linker uses the Apache 2.0 license with the LLVM exceptions, which says that attribution isn't needed:

As an exception, if, as a result of your compiling your source code, portions
of this Software are embedded into an Object form of such source code, you
may redistribute such embedded portions in such Object form without complying
with the conditions of Sections 4(a), 4(b) and 4(d) of the License.

The wild licenses don't have such exceptions.

[mati865]

Wild doesn't include its own objects when linking, it doesn't even have anything embeddable.
I think this exception is for things like libunwind, compiler-rt and libc++ in LLVM repo, which depending on how you build your core might be embedded into the binary. For example, when you compiler with Clang and enable any sanitizer, a part of compiler-rt subproject would be embedded into your binary.