From: Nils Freydank <nils.freydank@posteo.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] TensorFlow
Date: Thu, 14 Feb 2019 08:48:48 +0100 [thread overview]
Message-ID: <3961397.TdM0RJ455Y@pygoscelis> (raw)
In-Reply-To: <b67d1f98-665d-b327-cc27-9f19ca6ccf5d@verizon.net>
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
prev parent reply other threads:[~2019-02-14 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 20:09 [gentoo-user] TensorFlow Alan Grimes
2019-02-14 7:48 ` Nils Freydank [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3961397.TdM0RJ455Y@pygoscelis \
--to=nils.freydank@posteo.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox