1 |
сб, 17 окт. 2020 г. в 20:34, gevisz <gevisz@×××××.com>: |
2 |
> |
3 |
> сб, 17 окт. 2020 г. в 15:28, Michael Orlitzky <mjo@g.o>: |
4 |
> > On 10/17/20 8:10 AM, gevisz wrote: |
5 |
> > > |
6 |
> > > Any thoughts on how to proceed with this obstacle other than to |
7 |
> > > depclean tensorflow and try to reinstall it again? |
8 |
> > > > The problem is that all versions of tensorflow and almost all of its |
9 |
> > > dependencies are masked by default. So it is almost impossible to |
10 |
> > > guess which versions of them should be unmasked for the successful |
11 |
> > > compilation. |
12 |
> > |
13 |
> > My strategy was to run emerge with --autounmask=y and then to add the |
14 |
> > dependencies to package.accept_keywords one-by-one. If any of the |
15 |
> > dependencies that it suggests to you are actually incompatible, it's a |
16 |
> > bug in the tensorflow ebuild (or the ebuild of one of its dependencies). |
17 |
> > |
18 |
> > This is what I've currently got, but I originally generated the list for |
19 |
> > tensorflow-2.2 and then upgraded, so it may not be perfect. (It takes me |
20 |
> > three days to compile, so I'm not going to experiment!) |
21 |
> > |
22 |
> > # tensorflow |
23 |
> > =dev-python/pandas-1.1.2 ~amd64 |
24 |
> > =dev-python/gast-0.3.3 ~amd64 |
25 |
> > =dev-python/astunparse-1.6.3 ~amd64 |
26 |
> > =net-libs/grpc-1.28.1-r1 ~amd64 |
27 |
> > =sci-libs/tensorflow-2.3.1 ~amd64 |
28 |
> > =net-libs/google-cloud-cpp-0.10.0-r1 ~amd64 |
29 |
> > =sci-visualization/tensorboard-2.3.0 ~amd64 |
30 |
> > =dev-util/bazel-3.2.0 ~amd64 |
31 |
> > =sci-libs/tensorflow-estimator-2.3.0 ~amd64 |
32 |
> > =sys-apps/hwloc-2.1.0 ~amd64 |
33 |
> > =dev-python/grpcio-tools-1.28.1 ~amd64 |
34 |
> > =dev-cpp/abseil-cpp-20200225.2 ~amd64 |
35 |
> > =dev-python/google-auth-oauthlib-0.4.1 ~amd64 |
36 |
> > =dev-python/google-pasta-0.2.0 ~amd64 |
37 |
> |
38 |
> Thank you. I have depcleaned all masked packages and in line with your |
39 |
> suggestions started to build a list of package unmask rules for |
40 |
> emerging tensorflow-2.3.1. However, I do it manually using |
41 |
> emerge -vp tensorflow |
42 |
> As the result, so far I've got the following list: |
43 |
> >=sci-libs/tensorflow-2.2.0-r2::gentoo ~amd64 |
44 |
> >=net-libs/grpc-1.28::gentoo ~amd64 |
45 |
> >=sys-apps/hwloc-2::gentoo ~amd64 |
46 |
> >=dev-python/astunparse-1.6.3::gentoo ~amd64 |
47 |
> >=dev-python/gast-0.3.3::gentoo ~amd64 |
48 |
> >=dev-python/google-pasta-0.1.8::gentoo ~amd64 |
49 |
> >=net-libs/google-cloud-cpp-0.10.0::gentoo ~amd64 |
50 |
> >=sci-visualization/tensorboard-2.3.0::gentoo ~amd64 |
51 |
> >=sci-libs/tensorflow-estimator-2.3.0::gentoo ~amd64 |
52 |
> =dev-util/bazel-3*::gentoo ~amd64 |
53 |
> >=dev-python/grpcio-tools-1.28::gentoo ~amd64 |
54 |
> ~dev-python/grpcio-1.32.0::gentoo ~amd64 |
55 |
> >=dev-python/google-auth-oauthlib-0.4.1::gentoo ~amd64 |
56 |
> =dev-cpp/abseil-cpp-20200225*:=::gentoo ~amd64 |
57 |
> >=dev-libs/protobuf-3.13.0:=::gentoo ~amd64 |
58 |
> |
59 |
> However, now I have got the following |
60 |
> WARNING: One or more updates/rebuilds have been skipped due to a |
61 |
> dependency conflict: |
62 |
> |
63 |
> dev-libs/protobuf:0 |
64 |
> |
65 |
> (dev-libs/protobuf-3.13.0:0/24::gentoo, ebuild scheduled for merge) |
66 |
> USE="zlib -emacs -examples -static-libs -test" ABI_X86="(64) -32 |
67 |
> (-x32)" conflicts with |
68 |
> ~dev-libs/protobuf-3.12.4 required by |
69 |
> (dev-python/protobuf-python-3.12.4-r1:0/23::gentoo, ebuild scheduled |
70 |
> for merge) USE="" ABI_X86="(64)" PYTHON_TARGETS="python3_7 -python3_6 |
71 |
> -python3_8 (-python3_9)" |
72 |
> |
73 |
> I am going to solve it by adding the line |
74 |
> >=dev-python/protobuf-python-3.13.0-r1::gentoo ~amd64 |
75 |
> (and it indeed solves the dependency conflict) |
76 |
> However, in this case I am quite close to my previous configuration |
77 |
> when compilation of tensorflow failed. |
78 |
> |
79 |
> Now, I am going to compile. On my computer, it will also take a lot of |
80 |
> time. So, I will report the result till the end of the next week. :) |
81 |
|
82 |
Well, compilation of tensorflow-2.3.1 failed exactly with the same error. :( |
83 |
|
84 |
FAILED: Build did NOT complete successfully |
85 |
* ERROR: sci-libs/tensorflow-2.3.1::gentoo failed (compile phase): |
86 |
* ebazel failed |
87 |
* |
88 |
* Call stack: |
89 |
* ebuild.sh, line 125: Called src_compile |
90 |
* environment, line 4177: Called ebazel 'build' |
91 |
'//tensorflow:libtensorflow_framework.so' |
92 |
'//tensorflow:libtensorflow.so' |
93 |
* environment, line 2389: Called die |
94 |
* The specific snippet of code: |
95 |
* "${@}" || die "ebazel failed" |
96 |
* |
97 |
* If you need support, post the output of `emerge --info |
98 |
'=sci-libs/tensorflow-2.3.1::gentoo'`, |
99 |
* the complete build log and the output of `emerge -pqv |
100 |
'=sci-libs/tensorflow-2.3.1::gentoo'`. |
101 |
* The complete build log is located at |
102 |
'/var/log/portage/sci-libs:tensorflow-2.3.1:20201017-180429.log'. |
103 |
* The ebuild environment file is located at |
104 |
'/var/tmp/portage/sci-libs/tensorflow-2.3.1/temp/environment'. |
105 |
* Working directory: |
106 |
'/var/tmp/portage/sci-libs/tensorflow-2.3.1/work/tensorflow-2.3.1-python3_7' |
107 |
* S: '/var/tmp/portage/sci-libs/tensorflow-2.3.1/work/tensorflow-2.3.1' |