{lib}[intel/2016b] Tensorflow v0.12.1 w/ Python 3.5.2#4084
{lib}[intel/2016b] Tensorflow v0.12.1 w/ Python 3.5.2#4084boegel merged 2 commits intoeasybuilders:developfrom
Conversation
|
Test report by @boegel |
|
Test report by @boegel |
| source_urls = ['https://github.com/google/protobuf/archive/v%(version)s/'] | ||
| sources = [SOURCE_TAR_GZ] | ||
|
|
||
| preconfigopts = "./autogen.sh &&" |
There was a problem hiding this comment.
you need autotools as build dep for this.
|
|
||
| pymaj = '3' | ||
| pymin = '5' | ||
| pymajmin = pymaj + pymin |
There was a problem hiding this comment.
don't we have constants for this?
|
I can't test it easily right now, but it looks ok in theory. Do you think it might be worthwhile to offer a compiled version? |
|
@rjeschmi I usually prefer building from source, but I just don't have the time to dive into that now for Tensorflow. It certainly couldn't hurt, imho. The build instructions are at https://www.tensorflow.org/get_started/os_setup#installing_from_sources; they require a custom build tool So, that's most likely a custom easyblock... I think @gppezzi has some experience with building |
|
Hah, the |
|
Test report by @boegel |
|
We did already build TF from sources, we have an open PR for TF with and without Cuda on Cray (but this is WIP). |
|
@gppezzi Do you have a particular reason for not using a |
|
I just don't think that it is worth the efforts right now: TF seems to be changing very quickly and, by time we manage to have a working easyblock, things will change. IMO chances of re-using the easyblock for a new version (or on a different system) are very low. Also, we need more time to better understand this build tool (the procedure is currently a huge mess). |
|
Test report by @boegel |
|
@boegel why is the |
(created using
eb --new-pr)