Dear Yann,
The problem seems to be that the installation is taking longer than
EasyBuild is expecting, which makes it conclude that the installer is
asking as question that it doesn't know the answer too.
Since there is no output at all, there's no question to recognize
either, so assuming there's a question to answer a bit silly in this
specific context, we should improve that (at the risk of waiting
indefinitely...)
The CUDA installer used to be an interactive command, it seems like
that's no longer the case (it doesn't produce any output for me either,
but it does finish after about 1 minute).
For you, it ran for about 6 minutes before giving up, based on the
timestaps in the log.
Please try this:
* take a copy of the custom easyblock for CUDA (cuda.py, see
https://github.com/easybuilders/easybuild-easyblocks/blob/master/easybuild/easyblocks/c/cuda.py)
* change the "maxhits=300" to a higher value, for example
"maxhits=1000"; that will make EasyBuild wait longer before it kills the
installer
* make 'eb' use the modified easyblock using "eb --include-easyblocks
/path/to/cuda.py CUDA-10.1.105-GCC/8.2.0-2.31.1.eb"
Let me know if that helps...
How long does the installation take when you do it manually?
regards,
Kenneth
On 07/08/2019 15:27, Yann Sagon wrote:
Sorry, I forgot to reply to the mailing list.
I still have the issue.
-----Message d'origine-----
De : Yann Sagon
Envoyé : mercredi, 31 juillet 2019 15:13
À : 'Kenneth Hoste' <kenneth.ho...@ugent.be>
Objet : RE: [easybuild] Failed to compile CUDA 10.1.105 on CentOS7
Dear Kenneth,
-----Message d'origine-----
De : Kenneth Hoste <kenneth.ho...@ugent.be> Envoyé : mercredi, 31 juillet 2019 14:30
À : Yann Sagon <yann.sa...@unige.ch> Cc : easybuild@lists.ugent.be Objet : Re:
[easybuild] Failed to compile CUDA 10.1.105 on CentOS7
It looks like the cuda-installer script isn't producing any output at all,
which makes EasyBuild trip on it since it's expecting an interactive
installation script (which produces output that EasyBuild can match against
known question patterns).
What happens if you run the ./cuda-installer manually yourself?
Here is the result:
[sagon@node025 CUDA] $ ls /opt/ebsofts/Compiler/GCC/8.2.0-2.31.1/CUDA/10.1.105/
ls: cannot access /opt/ebsofts/Compiler/GCC/8.2.0-2.31.1/CUDA/10.1.105/: No
such file or directory
[sagon@node025 CUDA] $ ./cuda_10.1.105_418.39_linux.run --silent --toolkit
--toolkitpath=/opt/ebsofts/Compiler/GCC/8.2.0-2.31.1/CUDA/10.1.105
--defaultroot=/opt/ebsofts/Compiler/GCC/8.2.0-2.31.1/CUDA/10.1.105
[sagon@node025 CUDA] $ ls /opt/ebsofts/Compiler/GCC/8.2.0-2.31.1/CUDA/10.1.105/
bin doc EULA.txt extras include jre lib64 libnsight libnvvp
NsightCompute-2019.1 nsightee_plugins NsightSystems-2018.3 nvml nvvm share
src targets tools version.txt
[sagon@node025 CUDA]
So indeed the installer is really silent. Not sure how to correct that.
Best
