4c12a75e69
libtool can currently produce 2 warnings: 1. No symbols were in the object file 2. An object file with the same basename was specified multiple times The first warning here is often harmless and may just mean you have some translation units with no symbols for the target you're building for. The second warning can lead to real issues like those mentioned in https://reviews.llvm.org/D113130 where ODR violations can slip in. This introduces a new -warnings_as_errors flag that can be used by build systems that want to verify they never hit these warnings. For example with bazel the libtool caller first uniques names to make sure the duplicate base name case is not possible, but if that doesn't work as expected, having it fail would be preferred. It's also worth noting that llvm-libtool-darwin works around an issue that cctools libtool experiences related to debug info and duplicate basenames, the workaround is described here: |
||
|---|---|---|
| .. | ||
| Inputs | ||
| L-and-l.test | ||
| archive-flattening.test | ||
| arm64-asm.test | ||
| cpu-subtype-matching.test | ||
| create-static-lib.test | ||
| deterministic-library.test | ||
| filelist.test | ||
| help-message.test | ||
| invalid-input-output-args.test | ||
| missing-library-type.test | ||
| no-symbols-warning.test | ||
| universal-bitcode-flattening.test | ||
| universal-bitcode-output.test | ||
| universal-object-flattening.test | ||
| universal-object-output.test | ||
| version.test | ||
| x86_64-asm.test | ||