Skip to content

Conversation

@keith
Copy link
Member

@keith keith commented Nov 10, 2020

The option used here was gcc specific. This adds the relevant clang
option.

Fixes #12461

@keith
Copy link
Member Author

keith commented Nov 10, 2020

@philwo

@keith
Copy link
Member Author

keith commented Nov 10, 2020

Ideally this would be conditional on clang instead I guess?

@philwo
Copy link
Member

philwo commented Nov 10, 2020

Thank you! Happy to merge this when presubmits pass.

Unfortunately I don't know how to use compiler specific cflags. :/ @oquenchil Any idea?

@keith
Copy link
Member Author

keith commented Nov 10, 2020

Envoy uses:

config_setting(
    name = "clang_build",
    flag_values = {
        "@bazel_tools//tools/cpp:compiler": "clang",
    },
)

But testing this quickly on macOS this doesn't seem to work

@oquenchil
Copy link
Contributor

Where is the error log? It looks like all presubmits are passing.

That compiler target is here . By looking at the Starlark implementation of the rule, it looks like it takes the compiler string as is, it might be that on macOS is not just clang but something slightly different.

@keith
Copy link
Member Author

keith commented Nov 11, 2020

There isn't an error when I use that config it just doesn't match on macOS and the warnings are still produced in the console

@keith keith force-pushed the ks/fix-macos-warnings-for-zstd-jni branch from 63dba0f to 2315f51 Compare November 12, 2020 00:29
@google-cla
Copy link

google-cla bot commented Nov 12, 2020

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no and removed cla: yes labels Nov 12, 2020
The option used here was gcc specific. This adds the relevant clang
option.
@keith keith force-pushed the ks/fix-macos-warnings-for-zstd-jni branch from 2315f51 to fa3fcd5 Compare November 12, 2020 00:30
@google-cla google-cla bot added cla: yes and removed cla: no labels Nov 12, 2020
@keith
Copy link
Member Author

keith commented Nov 12, 2020

#12463

@meisterT
Copy link
Member

This becomes obsolete after the revert.

@meisterT meisterT closed this Nov 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Building @com_github_luben_zstd_jni on macOS is noisy

5 participants