[gentoo-user] tensorflow-2.3.1 failed to compile"

[gentoo-user] tensorflow-2.3.1 failed to compile"

[gevisz]

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?

Re: [gentoo-user] tensorflow-2.3.1 failed to compile"

[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

Re: [gentoo-user] tensorflow-2.3.1 failed to compile"

[gevisz]

сб, 17 окт. 2020 г. в 15:28, Michael Orlitzky <mjo@gentoo.org>:
> 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"

[gevisz]

сб, 17 окт. 2020 г. в 20:34, gevisz <gevisz@gmail.com>:
>
> сб, 17 окт. 2020 г. в 15:28, Michael Orlitzky <mjo@gentoo.org>:
> > 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"

[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.

Re: [gentoo-user] tensorflow-2.3.1 failed to compile"

[gevisz]

сб, 17 окт. 2020 г. в 20:06, Michael Orlitzky <mjo@gentoo.org>:
>
> 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.