-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Migrating to Bazel v4.2.x #2516
Comments
Hi @vidheyoza, Have you tried running on the Bazel 4.2.x versions ? Did you face any errors with the above version ? Please let us know with the error logs. Thanks! |
I tried running 3.7.2 and 4.2.1, but both give me the same error. There is an open issue on Bazel's public repo here where I talk about the error in more detail. Briefly, when I try installing bazel on the platform with either x64, I am getting errors with my tensorflow installation, so I have to stick to arm64, for which bazel doesn't have a direct installer script. When I use amd64, I can install tensorflow 1.14.0 needed for my fork of media pipe. Bazel installation doesn't throw any errors as well, but when I use it to build my fork of mediapipe, I get the following error:
Devs at bazel recommended downloading the binary for the required version directly into the location needed, but my docker container can't find that bazel executable even after changing permissions for its directory or even itself directly. I get this error when trying to use the directly downloaded bazel binary (for 3.7.2 as well as 4.2.1):
The devs said 4.2.x should be working with M1 Macs, but there still needs to be some bugs ironed out I suppose. the issue linked above has an ongoing discussion with them about this, so please do have a look at it since I think it will be helpful. |
UPDATE: as linked in the issue above, there was a problem with the installation of bazel, so they guided me with solutions and one of them worked. I am now working with solving the problem of tensorflow. Does mediapipe require a
|
I also had the same problem. Is there any update ? |
MediaPipe will not upgrade to bazel 4.2 until tensorflow does so. |
(that last link is broken) https://github.com/tensorflow/tensorflow/blob/master/.bazelversion |
Bazel version is updated to 4.2.1 https://github.com/google/mediapipe/releases/tag/v0.8.9 |
Please make sure that this is a feature request.
System information (Please provide as much relevant information as possible)
Describe the feature and the current behavior/state:
Since the launch of the M1 Mac machines, there has been a lot of discrepancies with building natively with different tools including Bazel, which is justified since it is a relatively new architecture. However, Bazel has started giving full support for M1 machines since v4.2.x. With that spirit in mind, I would like to know how easy/difficult it would be to get mediapipe to build with v4.2.x which released not more than a month ago (and move away from the current 3.7.2 which has been the version for almost a year).
Will this change the current api? How?
I'm not sure, but I don't think it will.
Who will benefit with this feature?
Everyone using mediapipe natively and wanting to build it from scratch will benefit from it. On top of that, any docker container running on M1 is also benefitted from it since docker also requires some degree of support from M1 which in turn requires bazel v4.2.x.
Please specify the use cases for this feature:
As described above, any native or dockerized mediapipe install benefits from moving to v4.2.x.
The text was updated successfully, but these errors were encountered: