Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-91356

Print final compiler or linker command that failed when Bazel compilation fails

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Build

      Currently the Bazel compiler wrapper hides arguments by default, ex:

      external/local_config_cc/cc_wrapper.sh -U_FORTIFY_SOURCE -fstack-protector -Wall -Wthread-safety -Wself-assign -Wunused-but-set-parameter -Wno-free-nonheap-object -fcolor-diagnostics ... (remaining 76 arguments skipped)

      To help debug what went wrong, we should setup Bazel to automatically print out the full command line string. This involves either switching away from Bazel's cc_wrapper somehow (maybe by depending on less of the default toolchain?) or by calling aquery after a Bazel execution fails via a `tools/bazel` hook to analyze the failure and print out the effective compiler/linker command that was used.

            Assignee:
            Unassigned Unassigned
            Reporter:
            zack.winter@mongodb.com Zack Winter
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: