-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: use Bazel 1.1.0 #8739
build: use Bazel 1.1.0 #8739
Conversation
Signed-off-by: Lizan Zhou <lizan@tetrate.io>
Signed-off-by: Lizan Zhou <lizan@tetrate.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this works and docs still build etc. then ship it. I have no idea why it is so inelegant to be passing file paths around in Bazel aspects, so basically "as long as it works" is the best we can do.
Signed-off-by: Lizan Zhou <lizan@tetrate.io>
Signed-off-by: Lizan Zhou <lizan@tetrate.io>
@@ -11,7 +11,10 @@ configure_make( | |||
"--enable-shared=no", | |||
"--enable-frame-pointers", | |||
"--disable-libunwind", | |||
], | |||
] + select({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@keith I believe this is workaround for bazelbuild/bazel#9154
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should update rules_foriegn_cc instead where this is fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@keith No that doesn't fix, I guess rules_foreign_cc only fixed cmake, not configure_make, I still need this one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should fix it there too then 😞
Signed-off-by: Lizan Zhou <lizan@tetrate.io>
This reverts commit 5ff7bc8. Signed-off-by: Lizan Zhou <lizan@tetrate.io>
@@ -1,16 +1,36 @@ | |||
diff --git a/mocktracer/BUILD b/mocktracer/BUILD |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we get this fixed upstream? CC @g-easy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CC @rnburn for OpenTracing ;)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@htuch let's not block on the upstream patches? |
@lizan I'm inclined as a general principle to make a best effort to merge patches upstream first. Not a huge fan of building up patches. But, if you think this is time sensitive, or is blocking something else, I'm cool with making that async. |
@htuch agreed on upstream first, but I'd also like to get bazel up-to-date before stable release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed if we can't land the patches by Monday let's land this before we cut 1.12.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, let's get this in for 1.12.0.
Signed-off-by: Lizan Zhou lizan@tetrate.io