Skip to content

Conversation

@ckolli5
Copy link

@ckolli5 ckolli5 commented May 10, 2022

The warning is unlikely to indicate a real issue, and Bazel already silences parallel warnings with -no_warning_for_no_symbols.

For more context, see #4057

Fixes #4057

Closes #15325.

PiperOrigin-RevId: 446659148

The warning is unlikely to indicate a real issue, and Bazel already silences parallel warnings with `-no_warning_for_no_symbols`.

For more context, see #4057

Fixes #4057

Closes #15325.

PiperOrigin-RevId: 446659148
@ckolli5 ckolli5 merged commit 7c52cb6 into bazelbuild:release-5.2.0 May 10, 2022
meteorcloudy pushed a commit that referenced this pull request May 10, 2022
The warning is unlikely to indicate a real issue, and Bazel already silences parallel warnings with `-no_warning_for_no_symbols`.

For more context, see #4057

Fixes #4057

Closes #15325.

PiperOrigin-RevId: 446659148

Co-authored-by: Christopher Sauer <[email protected]>
@ShreeM01 ShreeM01 added the team-Rules-CPP Issues for C++ rules label Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

team-Rules-CPP Issues for C++ rules

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants