-
Notifications
You must be signed in to change notification settings - Fork 90
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
Problems with build on macOS Sierra #82
Comments
I'm doing the same as you did but after replacing
|
@MyOwnClone could you finish the installation? |
Is there any update on this issue? I'm facing with the exactly same problem of not having the whl file. |
I am having this exact issue. No whl file to be found. |
Same problem here. |
Hi, i expect that the version of bazel has changes since the instructions
were written and is incompatible. I think the easiest way forward would be
to figure out which version of bazel was available at the time of the
instructions, and explicitly use that version.
…On Sun, Oct 14, 2018, 17:51 Raymond Phan ***@***.***> wrote:
Same problem here. whl file is not produced. Building on Mac OS 10.13.6
(Mojave).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#82 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHiqIwjwOwN-0KxPcLr0uvH33Kjg6mwks5uk7HmgaJpZM4STnCq>
.
|
Looking for similar solution, think I sort of found two possible avenues of solution i'm going to test this weekend. @acrogenesis, @MyOwnClone @bcaldir, @rayryeng, @KendallPark, @hughperkins |
@datatalking Thanks for this, but I've moved onto a Macbook with a M1 chip and there's already an established pipeline for getting TF and it uses the M1 GPU. I don't think I'll need (or am able) to test things out for you as I don't need the OpenCL flavour anymore. |
Thanks for replying, I was able to get my nvidia GPU working after rebuilding the whl.
… On Jan 3, 2023, at 5:25 PM, Ray Phan ***@***.***> wrote:
@datatalking <https://github.com/datatalking> Thanks for this, but I've moved onto a Macbook with a M1 chip and there's already an established pipeline for getting TF. I don't think I'll need (or am able) to test things out for you.
—
Reply to this email directly, view it on GitHub <#82 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC2ECWL3KR3LSO7E4CIQ62LWQTGRHANCNFSM4ESOOCVA>.
You are receiving this because you were mentioned.
|
Hi,
thanks for great project, awesome work. I've had some problems trying to build tf-coriander from sources on macOS Sierra. At first, I want to point out that maybe I've misunderstood the instructions in the https://github.com/hughperkins/tf-coriander/blob/master/doc/build-from-source.md article, or maybe I've just missed something and I am doing something completely wrong. In this case, I apologize.
If I understand correctly, according to mentioned page, I normally clone the repository, go to it and call
bash ./install_deps.sh
. This worked, or seemed to work. Than, I've calledbash ./build.sh
from the same folder. This is output from repeated call, so something is expected to be already up to date:After that, according to instruction page, there should be whl wheel in soft/tensorflowpkg folder. But these instructions are IMHO wrong, because no TF build have taken place. This is confirmed by the absence of the tensorflowpkg subfolder in soft folder and also the whl file is of course not present. But as I remember, TF must be built by calling bazel, so I have tried to build TF by using:
bazel build --jobs 4 //tensorflow/tools/pip_package:build_pip_package
This yielded a lot of errors, saying that set() syntax is deprecated and I should use depset(). I have replaced all set() calls with depset() calls in main bzl file and re-run command. This is what I got:
I think that most important is the
trying to mutate a frozen object
part...But I do not know how to fix the build in this stage. Am I doing it absolutely wrong or did I understand something wrong? Is documentation correct?Thanks for the response,
Tom
The text was updated successfully, but these errors were encountered: