[gentoo-user] tensorflow-2.5.0-r1 compilation failed
ERROR: /var/tmp/portage/sci-libs/tensorflow-2.5.0-r1/work/tensorflow-2.5.0-python3_9/tensorflow/BUILD:974:20: Linking of rule '//tensorflow:libtensorflow.so.2.5.0' failed (Exit 1): gcc failed: error executing command (cd /var/tmp/portage/sci-libs/tensorflow-2.5.0-r1/work/tensorflow-2.5.0-python3_9-bazel-base/execroot/org_tensorflow && \ exec env - \ HOME=/var/tmp/portage/sci-libs/tensorflow-2.5.0-r1/homedir \ KERAS_HOME=/var/tmp/portage/sci-libs/tensorflow-2.5.0-r1/temp/.keras \ PATH=/var/tmp/portage/sci-libs/tensorflow-2.5.0-r1/temp/python3.9/bin:/usr/lib/portage/python3.9/ebuild-helpers:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/lib/llvm/12/bin \ PWD=/proc/self/cwd \ PYTHON_BIN_PATH=/usr/bin/python3.9 \ PYTHON_LIB_PATH=/usr/lib/python3.9/site-packages \ TF2_BEHAVIOR=1 \ TF_SYSTEM_LIBS=absl_py,astor_archive,astunparse_archive,boringssl,com_github_googlecloudplatform_google_cloud_cpp,com_github_grpc_grpc,com_google_protobuf,curl,cython,dill_archive,double_conversion,enum34_archive,flatbuffers,functools32_archive,gast_archive,gif,hwloc,icu,jsoncpp_git,libjpeg_turbo,lmdb,nasm,nsync,opt_einsum_archive,org_sqlite,pasta,pcre,png,pybind11,six_archive,snappy,tblib_archive,termcolor_archive,typing_extensions_archive,wrapt,zlib \ /usr/bin/gcc @bazel-out/k8-opt/bin/tensorflow/libtensorflow.so.2.5.0-2.params) Execution platform: @local_execution_config_platform//:platform bazel-out/k8-opt/bin/tensorflow/core/profiler/_objs/profiler_analysis_proto_cc_impl/profiler_analysis.grpc.pb.pic.o:profiler_analysis.grpc.pb.cc:function grpc::CompletionQueue::~CompletionQueue(): error: undefined reference to 'absl::lts_20210324::Mutex::~Mutex()' bazel-out/k8-opt/bin/tensorflow/core/profiler/_objs/profiler_analysis_proto_cc_impl/profiler_analysis.grpc.pb.pic.o:profiler_analysis.grpc.pb.cc:function grpc::CompletionQueue::~CompletionQueue(): error: undefined reference to 'absl::lts_20210324::Mutex::~Mutex()' bazel-out/k8-opt/bin/tensorflow/core/profiler/_objs/profiler_analysis_proto_cc_impl/profiler_analysis.grpc.pb.pic.o:profiler_analysis.grpc.pb.cc:function grpc::internal::BlockingUnaryCallImpl::BlockingUnaryCallImpl(grpc::ChannelInterface*, grpc::internal::RpcMethod const&, grpc::ClientContext*, google::protobuf::MessageLite const&, google::protobuf::MessageLite*): error: undefined reference to 'absl::lts_20210324::Mutex::~Mutex()' bazel-out/k8-opt/bin/tensorflow/core/profiler/_objs/profiler_analysis_proto_cc_impl/profiler_analysis.grpc.pb.pic.o:profiler_analysis.grpc.pb.cc:function grpc::internal::BlockingUnaryCallImpl::BlockingUnaryCallImpl(grpc::ChannelInterface*, grpc::internal::RpcMethod const&, grpc::ClientContext*, google::protobuf::MessageLite const&, google::protobuf::MessageLite*): error: undefined reference to 'absl::lts_20210324::Mutex::~Mutex()' bazel-out/k8-opt/bin/tensorflow/core/debug/_objs/debug_service_proto_cc_impl/debug_service.grpc.pb.pic.o:debug_service.grpc.pb.cc:function grpc::internal::ClientCallbackReaderWriterImpl::Read(tensorflow::EventReply*): error: undefined reference to 'absl::lts_20210324::Mutex::Lock()' bazel-out/k8-opt/bin/tensorflow/core/debug/_objs/debug_service_proto_cc_impl/debug_service.grpc.pb.pic.o:debug_service.grpc.pb.cc:function grpc::internal::ClientCallbackReaderWriterImpl::Read(tensorflow::EventReply*): error: undefined reference to 'absl::lts_20210324::Mutex::Unlock()' bazel-out/k8-opt/bin/tensorflow/core/debug/_objs/debug_service_proto_cc_impl/debug_service.grpc.pb.pic.o:debug_service.grpc.pb.cc:function grpc::internal::ClientCallbackReaderWriterImpl::Read(tensorflow::EventReply*): error: undefined reference to 'absl::lts_20210324::Mutex::Unlock()' bazel-out/k8-opt/bin/tensorflow/core/debug/_objs/debug_service_proto_cc_impl/debug_service.grpc.pb.pic.o:debug_service.grpc.pb.cc:function grpc::internal::ClientCallbackReaderWriterImpl::Write(tensorflow::Event const*, grpc::WriteOptions): error: undefined reference to 'absl::lts_20210324::Mutex::Lock()' bazel-out/k8-opt/bin/tensorflow/core/debug/_objs/debug_service_proto_cc_impl/debug_service.grpc.pb.pic.o:debug_service.grpc.pb.cc:function grpc::internal::ClientCallbackReaderWriterImpl::Write(tensorflow::Event const*, grpc::WriteOptions): error: undefined reference to 'absl::lts_20210324::Mutex::Unlock()' bazel-out/k8-opt/bin/tensorflow/core/debug/_objs/debug_service_proto_cc_impl/debug_service.grpc.pb.pic.o:debug_service.grpc.pb.cc:function grpc::internal::ClientCallbackReaderWriterImpl::Write(tensorflow::Event const*, grpc::WriteOptions): error: undefined reference to 'absl::lts_20210324::Mutex::Unlock()' bazel-out/k8-opt/bin/tensorflow/core/debug/_objs/debug_service_proto_cc_impl/debug_service.grpc.pb.pic.o:debug_service.grpc.pb.cc:function grpc::internal::ClientCallbackReaderWriterImpl::WritesDone(): error: undefined reference to 'absl::lts_20210324::Mutex::Lock()'
Re: [gentoo-user] tensorflow-2.3.1 failed to compile"
сб, 17 окт. 2020 г. в 20:06, Michael Orlitzky : > > On 10/17/20 3:56 PM, gevisz wrote: > > > > Well, compilation of tensorflow-2.3.1 failed exactly with the same error. :( > > > > Can you file a bug with the full build log? Someone with a faster > computer may be able to investigate. Hm, there is actually a bug with a similar error reported under the number 747547 on bugs.gentoo.org exactly on the same date when my first update of tensorflow failed. Probably, I just should confirm it and make a reference to this thread.
Re: [gentoo-user] tensorflow-2.3.1 failed to compile"
On 10/17/20 3:56 PM, gevisz wrote: Well, compilation of tensorflow-2.3.1 failed exactly with the same error. :( Can you file a bug with the full build log? Someone with a faster computer may be able to investigate.
Re: [gentoo-user] tensorflow-2.3.1 failed to compile"
сб, 17 окт. 2020 г. в 20:34, gevisz :
>
> сб, 17 окт. 2020 г. в 15:28, Michael Orlitzky :
> > On 10/17/20 8:10 AM, gevisz wrote:
> > >
> > > Any thoughts on how to proceed with this obstacle other than to
> > > depclean tensorflow and try to reinstall it again?
> > > > The problem is that all versions of tensorflow and almost all of its
> > > dependencies are masked by default. So it is almost impossible to
> > > guess which versions of them should be unmasked for the successful
> > > compilation.
> >
> > My strategy was to run emerge with --autounmask=y and then to add the
> > dependencies to package.accept_keywords one-by-one. If any of the
> > dependencies that it suggests to you are actually incompatible, it's a
> > bug in the tensorflow ebuild (or the ebuild of one of its dependencies).
> >
> > This is what I've currently got, but I originally generated the list for
> > tensorflow-2.2 and then upgraded, so it may not be perfect. (It takes me
> > three days to compile, so I'm not going to experiment!)
> >
> > # tensorflow
> > =dev-python/pandas-1.1.2 ~amd64
> > =dev-python/gast-0.3.3 ~amd64
> > =dev-python/astunparse-1.6.3 ~amd64
> > =net-libs/grpc-1.28.1-r1 ~amd64
> > =sci-libs/tensorflow-2.3.1 ~amd64
> > =net-libs/google-cloud-cpp-0.10.0-r1 ~amd64
> > =sci-visualization/tensorboard-2.3.0 ~amd64
> > =dev-util/bazel-3.2.0 ~amd64
> > =sci-libs/tensorflow-estimator-2.3.0 ~amd64
> > =sys-apps/hwloc-2.1.0 ~amd64
> > =dev-python/grpcio-tools-1.28.1 ~amd64
> > =dev-cpp/abseil-cpp-20200225.2 ~amd64
> > =dev-python/google-auth-oauthlib-0.4.1 ~amd64
> > =dev-python/google-pasta-0.2.0 ~amd64
>
> Thank you. I have depcleaned all masked packages and in line with your
> suggestions started to build a list of package unmask rules for
> emerging tensorflow-2.3.1. However, I do it manually using
> emerge -vp tensorflow
> As the result, so far I've got the following list:
> >=sci-libs/tensorflow-2.2.0-r2::gentoo ~amd64
> >=net-libs/grpc-1.28::gentoo ~amd64
> >=sys-apps/hwloc-2::gentoo ~amd64
> >=dev-python/astunparse-1.6.3::gentoo ~amd64
> >=dev-python/gast-0.3.3::gentoo ~amd64
> >=dev-python/google-pasta-0.1.8::gentoo ~amd64
> >=net-libs/google-cloud-cpp-0.10.0::gentoo ~amd64
> >=sci-visualization/tensorboard-2.3.0::gentoo ~amd64
> >=sci-libs/tensorflow-estimator-2.3.0::gentoo ~amd64
> =dev-util/bazel-3*::gentoo ~amd64
> >=dev-python/grpcio-tools-1.28::gentoo ~amd64
> ~dev-python/grpcio-1.32.0::gentoo ~amd64
> >=dev-python/google-auth-oauthlib-0.4.1::gentoo ~amd64
> =dev-cpp/abseil-cpp-20200225*:=::gentoo ~amd64
> >=dev-libs/protobuf-3.13.0:=::gentoo ~amd64
>
> However, now I have got the following
> WARNING: One or more updates/rebuilds have been skipped due to a
> dependency conflict:
>
> dev-libs/protobuf:0
>
> (dev-libs/protobuf-3.13.0:0/24::gentoo, ebuild scheduled for merge)
> USE="zlib -emacs -examples -static-libs -test" ABI_X86="(64) -32
> (-x32)" conflicts with
> ~dev-libs/protobuf-3.12.4 required by
> (dev-python/protobuf-python-3.12.4-r1:0/23::gentoo, ebuild scheduled
> for merge) USE="" ABI_X86="(64)" PYTHON_TARGETS="python3_7 -python3_6
> -python3_8 (-python3_9)"
>
> I am going to solve it by adding the line
> >=dev-python/protobuf-python-3.13.0-r1::gentoo ~amd64
> (and it indeed solves the dependency conflict)
> However, in this case I am quite close to my previous configuration
> when compilation of tensorflow failed.
>
> Now, I am going to compile. On my computer, it will also take a lot of
> time. So, I will report the result till the end of the next week. :)
Well, compilation of tensorflow-2.3.1 failed exactly with the same error. :(
FAILED: Build did NOT complete successfully
* ERROR: sci-libs/tensorflow-2.3.1::gentoo failed (compile phase):
* ebazel failed
*
* Call stack:
* ebuild.sh, line 125: Called src_compile
* environment, line 4177: Called ebazel 'build'
'//tensorflow:libtensorflow_framework.so'
'//tensorflow:libtensorflow.so'
* environment, line 2389: Called die
* The specific snippet of code:
* "${@}" || die "ebazel failed"
*
* If you need support, post the output of `emerge --info
'=sci-libs/tensorflow-2.3.1::gentoo'`,
* the complete build log and the output of `emerge -pqv
'=sci-libs/tensorflow-2.3.1::gentoo'`.
* The complete build log is located at
'/var/log/portage/sci-libs:tensorflow-2.3.1:20201017-180429.log'.
* The ebuild environment file is located at
'/var/tmp/portage/sci-libs/tensorflow-2.3.1/temp/environment'.
* Working directory:
'/var/tmp/portage/sci-libs/tensorflow-2.3.1/work/tensorflow-2.3.1-python3_7'
* S: '/var/tmp/portage/sci-libs/tensorflow-2.3.1/work/tensorflow-2.3.1'
Re: [gentoo-user] tensorflow-2.3.1 failed to compile"
сб, 17 окт. 2020 г. в 15:28, Michael Orlitzky : > On 10/17/20 8:10 AM, gevisz wrote: > > > > Any thoughts on how to proceed with this obstacle other than to > > depclean tensorflow and try to reinstall it again? > > > The problem is that all versions of tensorflow and almost all of its > > dependencies are masked by default. So it is almost impossible to > > guess which versions of them should be unmasked for the successful > > compilation. > > My strategy was to run emerge with --autounmask=y and then to add the > dependencies to package.accept_keywords one-by-one. If any of the > dependencies that it suggests to you are actually incompatible, it's a > bug in the tensorflow ebuild (or the ebuild of one of its dependencies). > > This is what I've currently got, but I originally generated the list for > tensorflow-2.2 and then upgraded, so it may not be perfect. (It takes me > three days to compile, so I'm not going to experiment!) > > # tensorflow > =dev-python/pandas-1.1.2 ~amd64 > =dev-python/gast-0.3.3 ~amd64 > =dev-python/astunparse-1.6.3 ~amd64 > =net-libs/grpc-1.28.1-r1 ~amd64 > =sci-libs/tensorflow-2.3.1 ~amd64 > =net-libs/google-cloud-cpp-0.10.0-r1 ~amd64 > =sci-visualization/tensorboard-2.3.0 ~amd64 > =dev-util/bazel-3.2.0 ~amd64 > =sci-libs/tensorflow-estimator-2.3.0 ~amd64 > =sys-apps/hwloc-2.1.0 ~amd64 > =dev-python/grpcio-tools-1.28.1 ~amd64 > =dev-cpp/abseil-cpp-20200225.2 ~amd64 > =dev-python/google-auth-oauthlib-0.4.1 ~amd64 > =dev-python/google-pasta-0.2.0 ~amd64 Thank you. I have depcleaned all masked packages and in line with your suggestions started to build a list of package unmask rules for emerging tensorflow-2.3.1. However, I do it manually using emerge -vp tensorflow As the result, so far I've got the following list: >=sci-libs/tensorflow-2.2.0-r2::gentoo ~amd64 >=net-libs/grpc-1.28::gentoo ~amd64 >=sys-apps/hwloc-2::gentoo ~amd64 >=dev-python/astunparse-1.6.3::gentoo ~amd64 >=dev-python/gast-0.3.3::gentoo ~amd64 >=dev-python/google-pasta-0.1.8::gentoo ~amd64 >=net-libs/google-cloud-cpp-0.10.0::gentoo ~amd64 >=sci-visualization/tensorboard-2.3.0::gentoo ~amd64 >=sci-libs/tensorflow-estimator-2.3.0::gentoo ~amd64 =dev-util/bazel-3*::gentoo ~amd64 >=dev-python/grpcio-tools-1.28::gentoo ~amd64 ~dev-python/grpcio-1.32.0::gentoo ~amd64 >=dev-python/google-auth-oauthlib-0.4.1::gentoo ~amd64 =dev-cpp/abseil-cpp-20200225*:=::gentoo ~amd64 >=dev-libs/protobuf-3.13.0:=::gentoo ~amd64 However, now I have got the following WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: dev-libs/protobuf:0 (dev-libs/protobuf-3.13.0:0/24::gentoo, ebuild scheduled for merge) USE="zlib -emacs -examples -static-libs -test" ABI_X86="(64) -32 (-x32)" conflicts with ~dev-libs/protobuf-3.12.4 required by (dev-python/protobuf-python-3.12.4-r1:0/23::gentoo, ebuild scheduled for merge) USE="" ABI_X86="(64)" PYTHON_TARGETS="python3_7 -python3_6 -python3_8 (-python3_9)" I am going to solve it by adding the line >=dev-python/protobuf-python-3.13.0-r1::gentoo ~amd64 (and it indeed solves the dependency conflict) However, in this case I am quite close to my previous configuration when compilation of tensorflow failed. Now, I am going to compile. On my computer, it will also take a lot of time. So, I will report the result till the end of the next week. :)
Re: [gentoo-user] tensorflow-2.3.1 failed to compile"
On 10/17/20 8:10 AM, gevisz wrote: Any thoughts on how to proceed with this obstacle other than to depclean tensorflow and try to reinstall it again? > The problem is that all versions of tensorflow and almost all of its dependencies are masked by default. So it is almost impossible to guess which versions of them should be unmasked for the successful compilation. My strategy was to run emerge with --autounmask=y and then to add the dependencies to package.accept_keywords one-by-one. If any of the dependencies that it suggests to you are actually incompatible, it's a bug in the tensorflow ebuild (or the ebuild of one of its dependencies). This is what I've currently got, but I originally generated the list for tensorflow-2.2 and then upgraded, so it may not be perfect. (It takes me three days to compile, so I'm not going to experiment!) # tensorflow =dev-python/pandas-1.1.2 ~amd64 =dev-python/gast-0.3.3 ~amd64 =dev-python/astunparse-1.6.3 ~amd64 =net-libs/grpc-1.28.1-r1 ~amd64 =sci-libs/tensorflow-2.3.1 ~amd64 =net-libs/google-cloud-cpp-0.10.0-r1 ~amd64 =sci-visualization/tensorboard-2.3.0 ~amd64 =dev-util/bazel-3.2.0 ~amd64 =sci-libs/tensorflow-estimator-2.3.0 ~amd64 =sys-apps/hwloc-2.1.0 ~amd64 =dev-python/grpcio-tools-1.28.1 ~amd64 =dev-cpp/abseil-cpp-20200225.2 ~amd64 =dev-python/google-auth-oauthlib-0.4.1 ~amd64 =dev-python/google-pasta-0.2.0 ~amd64
[gentoo-user] tensorflow-2.3.1 failed to compile"
A week ago, on October 10, 2020, tensorflow-2.3.1 gracefully failed to compile with the following ERROR: sci-libs/tensorflow-2.3.1::gentoo failed (compile phase) and a few weeks before tensorflow-2.2.0-r2 caused a dependency conflict during a regular system update, so I updated my system excluding tensorflow and on October 10 tried, after another update excluding tensorflow, tried to update it to the last available version. Before doing it, I also unmasked some of its most recent dependencies (I think it was protobuf-3.13.0) to avoid dependency conflict. Any thoughts on how to proceed with this obstacle other than to depclean tensorflow and try to reinstall it again? The problem is that all versions of tensorflow and almost all of its dependencies are masked by default. So it is almost impossible to guess which versions of them should be unmasked for the successful compilation. Is there any hope that in the future at least some version of tensorflow will be considered "stable" in Gentoo?
[gentoo-user] Tensorflow 2.1.0 failing to compile
Hey Jason, Please let me know what I am missing and if I should add anything more. Thanks a lot for your work in porting it :D Supplementary information (build log last 200 lines, make.conf, eix-installed -a) in email. Cheers, Aisha Last 200 lines of build.log: bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. INFO: From ProtoCompile tensorflow/stream_executor/dnn.pb.cc: bazel-out/k8-py2-opt/bin/external/com_google_protobuf: warning: directory does not exist. INFO: From ProtoCompile tensorflow/core/protobuf/tpu/optimization_parameters.pb.cc: bazel-out/k8-py2-opt/bin/external/com_google_protobuf: warning: directory does not exist. INFO: From ProtoCompile tensorflow/compiler/xla/xla_data.pb.cc: bazel-out/k8-py2-opt/bin/external/com_google_protobuf: warning: directory does not exist. INFO: From ProtoCompile tensorflow/core/profiler/profiler_analysis_pb2.py: bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. INFO: From ProtoCompile tensorflow/core/protobuf/error_codes_pb2.py: bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. INFO: From ProtoCompile tensorflow/core/protobuf/tpu/compilation_result_pb2.py: bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. INFO: From ProtoCompile tensorflow/python/training/checkpoint_state_pb2.py: bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. INFO: From ProtoCompile tensorflow/core/profiler/profiler_service_monitor_result_pb2.py: bazel-out/k8-py2-opt/bin/external/com_google_protobuf/.: warning: directory does not exist. INFO: From Executing genrule //tensorflow/python:framework/fast_tensor_util.pyx_cython_translation: /usr/lib64/python3.6/site-packages/Cython/Compiler/Main.py:369: FutureWarning: Cython directive 'language_level' not set, using 2 for now (Py2). This will change in a later release! File: /var/tmp/portage/sci-libs/tensorflow-2.1.0/work/tensorflow-2.1.0-python3_6-bazel-base/execroot/org_tensorflow/tensorflow/python/framework/fast_tensor_util.pyx tree = Parsing.p_module(s, pxd, full_module_name) INFO: From Executing genrule //tensorflow/python:framework/fast_tensor_util.pyx_cython_translation: /usr/lib64/python3.6/site-packages/Cython/Compiler/Main.py:369: FutureWarning: Cython directive 'language_level' not set, using 2 for now (Py2). This will change in a later release! File: /var/tmp/portage/sci-libs/tensorflow-2.1.0/work/tensorflow-2.1.0-python3_6-bazel-base/execroot/org_tensorflow/tensorflow/python/framework/fast_tensor_util.pyx tree = Parsing.p_module(s, pxd, full_module_name) INFO: From Executing genrule //tensorflow/python:framework/fast_tensor_util.pyx_cython_translation [for host]:
Re: [gentoo-user] TensorFlow
Hi Alan, Am Dienstag, 12. Februar 2019, 21:09:08 CET schrieb Alan Grimes: > [...] > It has been about two weeks since I've sync'd so this may or may not > still be valid, updating is an extremely risky operation on my machine > so I'm on a once every 3-6 months schedule... what is risky about it at your machine? You have at least three different ways to check for updates if you really can't upgrade on a regular basis: 1. sync your portage tree, but do not install updates (yet) 2. check online on gentoo.org or inside the mirror at github.com https://gitweb.gentoo.org/repo/gentoo.git/tree/sci-libs/tensorflow 3. check the packages page: https://packages.gentoo.org/packages/sci-libs/tensorflow With regards to the persistence of bugs you should consult bugs.gentoo.org and search for your specific issue/bug. > current state: > [...] I’m sorry I can't help with that linker problem, but at least I can say that tensorflow-1.13.0_rc1 built here without errors (and seems to run aswell). But watch out, you need bazel-0.20.0 (see bug https://bugs.gentoo.org/ 677280 for details). -- GPG fingerprint: '00EF D31F 1B60 D5DB ADB8 31C1 C0EC E696 0E54 475B' Nils Freydank
[gentoo-user] TensorFlow
I wanna take a whack at an AI challenge, https://www.aicrowd.com/challenges/unity-obstacle-tower-challenge Ok, so I'm like "emerge tensorflow" It has been about two weeks since I've sync'd so this may or may not still be valid, updating is an extremely risky operation on my machine so I'm on a once every 3-6 months schedule... current state: # tortoise /home/atg/source # emerge tensorflow These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] net-libs/google-cloud-cpp-0.2.0-r1::gentoo USE="test" 0 KiB [ebuild N ] sci-visualization/tensorboard-1.12.1::gentoo PYTHON_TARGETS="python2_7 python3_6 -python3_5" 0 KiB [ebuild N ] sci-libs/tensorflow-1.12.0::gentoo USE="cuda python -mpi" CPU_FLAGS_X86="avx avx2 sse sse2 sse3 sse4_1 sse4_2 -fma3 -fma4" PYTHON_TARGETS="python2_7 python3_6 -python3_5" 0 KiB [..] [ 15%] Linking CXX executable internal_throw_delegate_test cd /var/tmp/portage/net-libs/google-cloud-cpp-0.2.0-r1/work/google-cloud-cpp-0.2.0_build/google/cloud && /usr/bin/cmake -E cmake_link_script CMakeFiles/internal_throw_delegate_test.dir/link.txt --verbose=1 /usr/bin/x86_64-pc-linux-gnu-g++ -march=native -pipe -O3 -Wl,-O1 -Wl,--as-needed CMakeFiles/internal_throw_delegate_test.dir/internal/throw_delegate_test.cc.o -o internal_throw_delegate_test -Wl,-rpath,/var/tmp/portage/net-libs/google-cloud-cpp-0.2.0-r1/work/google-cloud-cpp-0.2.0_build/google/cloud:/usr/local/lib64 libgoogle_cloud_cpp_testing.so libgoogle_cloud_cpp_common.so.0.1.0 /usr/lib64/libgmock_main.so /usr/lib64/libgmock.so /usr/local/lib64/libgtest.so -lpthread /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: CMakeFiles/internal_throw_delegate_test.dir/internal/throw_delegate_test.cc.o:(.data.rel.ro._ZTI38ThrowDelegateTest_InvalidArgument_Test[_ZTI38ThrowDelegateTest_InvalidArgument_Test]+0x10): undefined reference to `typeinfo for testing::Test' /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: CMakeFiles/internal_throw_delegate_test.dir/internal/throw_delegate_test.cc.o:(.data.rel.ro._ZTI33ThrowDelegateTest_RangeError_Test[_ZTI33ThrowDelegateTest_RangeError_Test]+0x10): undefined reference to `typeinfo for testing::Test' /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: CMakeFiles/internal_throw_delegate_test.dir/internal/throw_delegate_test.cc.o:(.data.rel.ro._ZTI35ThrowDelegateTest_RuntimeError_Test[_ZTI35ThrowDelegateTest_RuntimeError_Test]+0x10): undefined reference to `typeinfo for testing::Test' /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: CMakeFiles/internal_throw_delegate_test.dir/internal/throw_delegate_test.cc.o:(.data.rel.ro._ZTI33ThrowDelegateTest_LogicError_Test[_ZTI33ThrowDelegateTest_LogicError_Test]+0x10): undefined reference to `typeinfo for testing::Test' collect2: error: ld returned 1 exit status make[2]: *** [google/cloud/CMakeFiles/internal_throw_delegate_test.dir/build.make:89: google/cloud/internal_throw_delegate_test] Error 1 make[2]: Leaving directory '/var/tmp/portage/net-libs/google-cloud-cpp-0.2.0-r1/work/google-cloud-cpp-0.2.0_build' make[1]: *** [CMakeFiles/Makefile2:221: google/cloud/CMakeFiles/internal_throw_delegate_test.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs I've tried toggling the "test" flag on the package, no change. Would trying to get Nvidia's containers working be a better way to waste my time on this? Or should I give up and use google's cloud service? =\ -- Please report bounces from this address to a...@numentics.com Powers are not rights.
