Skip to content
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

Support building TensorFlow Serving on OS X #1

Closed
kirilg opened this issue Feb 16, 2016 · 3 comments
Closed

Support building TensorFlow Serving on OS X #1

kirilg opened this issue Feb 16, 2016 · 3 comments

Comments

@kirilg
Copy link
Contributor

kirilg commented Feb 16, 2016

No description provided.

@kirilg
Copy link
Contributor Author

kirilg commented Mar 31, 2016

Even though we don't yet have full support for it, it does work if you run it in a docker container - http://tensorflow.github.io/serving/docker

We should still add full support without requiring docker.

@Shaikjalal
Copy link

I have issues compiling serving on mac, i guess its still not supported for mac.
tensorflow_serving/core/test_util/BUILD:52:1: C++ compilation of rule '//tensorflow_serving/core/test_util:fake_loader' failed: osx_cc_wrapper.sh failed: error executing command external/bazel_tools/tools/cpp/osx_cc_wrapper.sh '-D_FORTIFY_SOURCE=1' -fstack-protector -fcolor-diagnostics -Wall -Wthread-safety -Wself-assign -fno-omit-frame-pointer '-std=c++0x' -iquote . -iquote ... (remaining 101 argument(s) skipped): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
In file included from tensorflow_serving/core/test_util/fake_loader.cc:16:
./tensorflow_serving/core/test_util/fake_loader.h:59:10: error: thread-local storage is not supported for the current target
static thread_local bool was_deleted_in_this_thread_;
^
tensorflow_serving/core/test_util/fake_loader.cc:24:1: error: thread-local storage is not supported for the current target
thread_local bool FakeLoader::was_deleted_in_this_thread_;
^
2 errors generated.
INFO: Elapsed time: 1583.096s, Critical Path: 1409.25s

kirilg referenced this issue in kirilg/serving Sep 7, 2016
…a given servable:

 (1) have BasicManager always forget about a servable that goes to state kEnd;
 (2) when AspiredVersionsManager gets a re-aspire request for a servable not in state kEnd, it blocks until that servable reaches kEnd (and everything gets reset)

Regarding #1: independent of the re-aspire issue, I think that's a cleaner contract and it also ensures the manager won't accumulate state proportional to the # of failed servables it has ever dealt with.
Change: 132115088
pythonner pushed a commit to pythonner/serving that referenced this issue Sep 8, 2016
…a given servable:

 (1) have BasicManager always forget about a servable that goes to state kEnd;
 (2) when AspiredVersionsManager gets a re-aspire request for a servable not in state kEnd, it blocks until that servable reaches kEnd (and everything gets reset)

Regarding tensorflow#1: independent of the re-aspire issue, I think that's a cleaner contract and it also ensures the manager won't accumulate state proportional to the # of failed servables it has ever dealt with.
Change: 132115088
@misterpeddy
Copy link
Member

Closing as the recommended way to build is using the development docker image.

minglotus-6 added a commit that referenced this issue Jun 30, 2021
minglotus-6 added a commit that referenced this issue Jun 30, 2021
Update pip source for python 2.7 #1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants