Hi Alan,

thanks for the warning.  I tried putting 'intel-mkl' and 'intel-mpi'
into the components, respectively, and at least the build worked fine.

For this to work, I needed to modify the imkl easyblock a bit, see
https://github.com/hpcugent/easybuild-easyblocks/issues/899.

The directories I get are small enough, I guess:

$ du -sh ~/eb/software/im*
2.7G    /home/hilboll/eb/software/imkl
764M    /home/hilboll/eb/software/impi

Cheers,
  Andreas.


Alan O'Cais writes:

> Hi Andreas,
>
> I've done this and it is a bad idea! Unless you tweak things you're 
> installations are bloated with installations from RPMs you don't need...and 
> this will probably come back to hurt you later. Below is an extract from an 
> internal email when I did this back in February:
> I think there are probably some issues with doing the installations directly 
> from the Parallel Studio tarball and you tell by looking at the size of the 
> installation directories.
>
> The compilers are fine since if you compare the size of the old and new 
> installation directories you can see they are the same:
> -bash-4.2$ du -sh icc/2016.* ifort/2016.*
> 661M icc/2016.1.150-GCC-4.9.3-2.25
> 672M icc/2016.2.181-GCC-4.9.3-2.25
> 646M ifort/2016.1.150-GCC-4.9.3-2.25
> 664M ifort/2016.2.181-GCC-4.9.3-2.25
> I think they are a good template for how things should be done. The relevant 
> line in the easyconfigs of these that control what happens is:
> ( from 
> /usr/local/software/jureca/Stage1/software/Core/EasyBuild/2.6.0/lib/python2.7/site-packages/easybuild_easyconfigs-2.6.0-py2.7.egg/easybuild/easyconfigs/i/icc/icc-2016.1.150-GCC-4.9.3-2.25.eb)
> # full list of components can be obtained from pset/mediaconfig.xml in 
> unpacked sources
> # cfr. 
> https://software.intel.com/en-us/articles/intel-composer-xe-2015-silent-installation-guide
> components = ['intel-comp', 'intel-ccomp', 'intel-icc', 'intel-openmp', 
> 'intel-ipsc?_']
> which basically means you need to tell the installer which components to 
> install.
>
> You can see that when I tried to use the same tarball for imkl and impi, that 
> I ended up with bloated installations (even though they work) because it 
> installs everything rather than what it needs:
> -bash-4.2$ du -sh 2016.*/impi/*
> 821M 2016.1.150-GCC-4.9.3-2.25/impi/5.1.2.150<http://5.1.2.150/>
> 7,6G 2016.2.181-GCC-4.9.3-2.25/impi/5.1.3.181<http://5.1.3.181/>
> du -sh 8*/*
> 2,9G 8.1.5-GCC-4.9.3-2.25/imkl
> 13G 8.2.5-GCC-4.9.3-2.25/imkl
> The same is true for tbb, ipp, vtune,... We will need to fine tune the 
> easyconfigs for these with components to trim back the installations (or we 
> just use the specific tarballs rather than the bundle).
>
> On 22 April 2016 at 15:21, Andreas Hilboll 
> <hilb...@uni-bremen.de<mailto:hilb...@uni-bremen.de>> wrote:
> Thanks, guys,
>
> turns out the existing easyconfigs for impi and imkl seem to work just
> fine (i.e., build without problems) when I just hard-code the Parallel
> Studio tgz filename in the easyconfig files.
>
> I'll report back in case I run into problems, but this seems to work
> just fine for me.
>
> Cheers,
>   Andreas.
>
>
> Kenneth Hoste writes:
>
>> Hi Andreas,
>>
>> You should be able to download the separate tarballs for impi and imkl
>> from the Intel website.
>> Just the RPMs is not enough for what's in place in EasyBuild, since you
>> need to install script too provided by Intel...
>>
>> There's currently no supported to install the whole Parallel Studio
>> suite in one go, although that could be looked into...
>>
>>
>> regards,
>>
>> Kenneth
>>
>> On 22/04/16 14:20, Andreas Hilboll wrote:
>>> Hi EasyBuilders,
>>>
>>> I'm trying to get the Intel toolchains working on my system.  However,
>>> there seems to be something off with the packaging.  What I have is .tgz
>>> files parallel_studio_xe_2016.tgz, parallel_studio_xe_2016_update1.tgz,
>>> parallel_studio_xe_2016_update2.tgz.
>>>
>>> I could build the icc and ifort and iccifort easyconfigs from these
>>> files, but do have problems with impi and imkl, as the .tgz files I have
>>> don't include them as .tgz file, as seems to be required by the impi and
>>> imkl easyconfigs. However, these .tgz files do contain RPM files, e.g.,
>>>
>>> - intel-mpi-doc-5.1.3-181.x86_64.rpm
>>> - intel-mpirt-l-ps-181-16.0.2-181.i486.rpm
>>> - intel-mpi-sdk-mic-181-5.1.3-181.x86_64.rpm
>>> - intel-mpi-psxe-062-5.1.3-062.x86_64.rpm
>>> - intel-mpi-rt-mic-181-5.1.3-181.x86_64.rpm
>>> - intel-mpi-rt-core-181-5.1.3-181.x86_64.rpm
>>> - intel-mpi-sdk-core-181-5.1.3-181.x86_64.rpm
>>>
>>> - intel-mkl-181-11.3.2-181.x86_64.rpm
>>> - intel-mkl-common-181-11.3.2-181.noarch.rpm
>>> - intel-mkl-devel-181-11.3.2-181.i486.rpm
>>> - intel-mkl-devel-181-11.3.2-181.x86_64.rpm
>>>
>>> I'd appreciate some guidance in building the impi and imkl easyconfigs
>>> from these rpm files.  Any ideas?
>>>
>>> Cheers,
>>>    Andreas.
>>>
>>>
>>>
>
>
> --
> Dr. Andreas Hilboll
>
> Center for Marine Environmental Sciences (MARUM)
>                     - AND -
>     Institute of Environmental Physics (IUP)
>
> University of Bremen
>
> U3145
> Otto-Hahn-Allee 1
> D-28359 Bremen
> Germany
>
> +49(0)421 218 62133<tel:%2B49%280%29421%20218%2062133>  (phone)
> +49(0)421 218 98 62133<tel:%2B49%280%29421%20218%2098%2062133> (fax)
> http://www.iup.uni-bremen.de/~hilboll


-- 
Dr. Andreas Hilboll

Center for Marine Environmental Sciences (MARUM)
                    - AND -
    Institute of Environmental Physics (IUP)

University of Bremen

U3145
Otto-Hahn-Allee 1
D-28359 Bremen
Germany

+49(0)421 218 62133  (phone)
+49(0)421 218 98 62133 (fax)
http://www.iup.uni-bremen.de/~hilboll

Reply via email to