Dear Joachim,
On 14/03/2018 11:35, Joachim Hein wrote:
Hi,
I am trying TensorFlow-1.5.0-goolfc-2017b-Python-3.6.3.eb . It is
looking for a file cudnn-9.0-linux-x64-v7.0.5.15.tgz , however I am
currently getting cudnn-9.0-linux-x64-v7.tgz from the Nvidea download
site. The sha256 sum of the file I just downloaded agrees with the
one in the EB-config. After renaming my download to the name expected
by EB, cuDNN builds.
Can the config be upgraded to handle both, old and new name? Is that
something EB supports? Otherwise we should leave a comment inside the
config, that renaming is a work around (one needs a manual download of
sources anyway).
Any comments?
It's not a matter of old vs new name, it's that the cuDNN tarballs
aren't properly versioned (I think)...
The 'v7' doesn't specify which exact version it is, so without forcing
people to rename we'd run into checksum failures instead when people
download a newer (or older) version.
regards,
Kenneth
Best wishes
Joachim
