1 2> ATTENTION! Please read and follow: 3> - if this is a _question_ about how to build / test / query / deploy using Bazel, ask it on StackOverflow instead: https://stackoverflow.com/questions/tagged/bazel 4> - if this is a _discussion starter_, send it to bazel-discuss@googlegroups.com or cc-bazel-discuss@googlegroups.com 5> - if this is a _bug_ or _feature request_, fill the form below as best as you can. 6 7### Description of the problem / feature request: 8 9> Replace this line with your answer. 10 11### Feature requests: what underlying problem are you trying to solve with this feature? 12 13> Replace this line with your answer. 14 15### Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible. 16 17> Replace this line with your answer. 18 19### What operating system are you running Bazel on? 20 21> Replace this line with your answer. 22 23### What's the output of `bazel info release`? 24 25> Replace this line with your answer. 26 27### If `bazel info release` returns "development version" or "(@non-git)", tell us how you built Bazel. 28 29> Replace this line with your answer. 30 31### What version of rules_cc do you use? Can you paste the workspace rule used to fetch rules_cc? What other relevant dependencies does your project have? 32 33> Replace this line with your answer. 34 35### What Bazel options do you use to trigger the issue? What C++ toolchain do you use? 36 37> Replace this line with your answer. 38 39### Have you found anything relevant by searching the web? 40 41> Replace these lines with your answer. 42> 43> Places to look: 44> * StackOverflow: http://stackoverflow.com/questions/tagged/bazel 45> * GitHub issues: 46> * https://github.com/bazelbuild/rules_cc/issues 47> * https://github.com/bazelbuild/bazel/issues 48> * email threads: 49> * https://groups.google.com/forum/#!forum/bazel-discuss 50> * https://groups.google.com/forum/#!forum/cc-bazel-discuss 51 52### Any other information, logs, or outputs that you want to share? 53 54> Replace these lines with your answer. 55> 56> If the files are large, upload as attachment or provide link. 57