ERROR LDFLAGS parameter in automatically generated build_script.sh

[Boring545]

I am compiling Envoy using Bazel, and I encountered an issue during the process: there is a problem compiling gperftools. After investigation, I found that the issue is caused by incorrect LDFLAGS—specifically, --gdb-index is not supported by my ld.

I discovered that rules_foreign_cc automatically generates a configuration file named gperftools_build_foreign_cc/build_script.sh, which specifies the erroneous LDFLAGS. I tried to manually modify this file, but each time I compile, a new file is generated, overwriting my changes. I also attempted to set LDFLAGS in the system environment, but it had no effect.

I searched for gdb-index in the Envoy, gperftools, and rules_foreign_cc project files, but strangely, none of them specify this ld parameter. I suspect that rules_foreign_cc retrieves this ld parameter via ldflags = flags_info.cxx_linker_executable, and I pinpointed the code to:

cxx_linker_executable = cc_common.get_memory_inefficient_command_line(
    feature_configuration = feature_configuration,
    action_name = ACTION_NAMES.cpp_link_executable,
    variables = cc_common.create_link_variables(
        cc_toolchain = cc_toolchain_,
        feature_configuration = feature_configuration,
        is_using_linker = True,
        is_linking_dynamic_library = False,
        must_keep_debug = False,
    ),
),

It seems that this ld parameter is retrieved from the cc_toolchain. Could you provide some advice on how to specify LDFLAGS?

---