Loris Bennett <[email protected]> writes: > Hi, > > I need to create an EC for PyCUDA for the fosscuda-2019b toolchain. > > The existing ECs are > > * $CFGS1/PyCUDA-2016.1.2-intel-2016b-Python-2.7.12.eb > * $CFGS1/PyCUDA-2017.1.1-intel-2018a-Python-2.7.14.eb > * $CFGS1/PyCUDA-2018.1-intel-2018a-Python-3.6.4-CUDA-9.1.85.eb > > I would assume my EC should be called > > PyCUDA-2019.1.2-fosscuda-2019b-Python-3.7.4.eb > > However, is there any reason why it should be called > > PyCUDA-2019.1.2-foss-2019b-Python-3.7.4-CUDA-10.1.243.eb > > instead? What's the convention here?
As I am also going to need Boost.Python, does anyone know whether this needs to be build explicitly against CUDA? The available ECs seem to suggest that it doesn't: * $CFGS1/b/Boost.Python/Boost.Python-1.64.0-gompi-2019a.eb * $CFGS1/b/Boost.Python/Boost.Python-1.64.0-gompic-2019a.eb * $CFGS1/b/Boost.Python/Boost.Python-1.65.1-intel-2017b-Python-2.7.14.eb * $CFGS1/b/Boost.Python/Boost.Python-1.66.0-foss-2018a-Python-3.6.4.eb * $CFGS1/b/Boost.Python/Boost.Python-1.66.0-intel-2018a-Python-2.7.14.eb * $CFGS1/b/Boost.Python/Boost.Python-1.66.0-intel-2018a-Python-3.6.4.eb * $CFGS1/b/Boost.Python/Boost.Python-1.67.0-foss-2018b-Python-2.7.15.eb * $CFGS1/b/Boost.Python/Boost.Python-1.67.0-foss-2018b-Python-3.6.6.eb * $CFGS1/b/Boost.Python/Boost.Python-1.67.0-fosscuda-2018b-Python-2.7.15.eb * $CFGS1/b/Boost.Python/Boost.Python-1.67.0-intel-2018b-Python-2.7.15.eb * $CFGS1/b/Boost.Python/Boost.Python-1.67.0-intel-2018b-Python-3.6.6.eb * $CFGS1/b/Boost.Python/Boost.Python-1.70.0-gompi-2019a.eb * $CFGS1/b/Boost.Python/Boost.Python-1.70.0-iimpi-2019a.eb * $CFGS1/b/Boost.Python/Boost.Python-1.71.0-gompi-2019b.eb * $CFGS1/b/Boost.Python/Boost.Python-1.72.0-gompi-2020a.eb * $CFGS1/b/Boost.Python/Boost.Python-1.72.0-iimpi-2020a.eb * $CFGS1/m/minieigen/minieigen-0.5.4_fix-boost-python.patch Cheers, Loris -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email [email protected]
