Ole,

On 09/29/16 11:22, Ole Holm Nielsen wrote:
> On 09/29/2016 11:17 AM, Kenneth Hoste wrote:
>> I'm not sure what your question is w.r.t. documentation...
>> Do you mean your own (internal) documentation, or the EasyBuild
>> documentation at http://easybuild.readthedocs.io/?
>> The --try-* options don't have a dedicated entry in the EasyBuild docs
>> yet, but they're considered stable; unless you're taking it a bit too
>> far, way beyond just tweaking the toolchain (version), they should work
>> (that is, produce 'correct' easyconfigs, there are no guarantees that
>> the installation will actually work).
>
> I'm referring to our own internal documentation: How may we ever
> remember how to build a specific application module or a toolchain, if
> we don't have an easyconfig file and don't remember some specific
> --try-toolchain.  That's why I think documentation may become an issue.

The final easyconfig file will be archived.  For one in the
'easybuild' directory of the package's installation directory
and second in the easyconfig archive (see '--repositorypath').

Markus


>>> On 09/29/2016 10:48 AM, Kenneth Hoste wrote:
>>>> Hi Ole,
>>>>
>>>> On 29/09/16 10:37, Pablo Escobar Lopez wrote:
>>>>> have you tried "eb Python-3.5.2-foss-2016.04.eb
>>>>> --try-toolchain=foss,2016.09 -r"   ?
>>>>
>>>> +1 on this, the problem is that there are no easyconfigs available for
>>>> the dependencies of Python 3.5.2 with foss/2016.09.
>>>>
>>>> If you combine --try-toolchain (or --try-toolchain-version) with
>>>> --robot, EasyBuild will first construct the full dependency graph using
>>>> the foss/2016.04, and then generate easyconfigs (in a temp dir) for
>>>> each
>>>> of the components using foss/2016.09, and then proceed to building and
>>>> installing everything.
>>>>
>>>>
>>>> regards,
>>>>
>>>> Kenneth
>>>>>
>>>>> 2016-09-29 8:55 GMT+02:00 Ole Holm Nielsen <[email protected]
>>>>> <mailto:[email protected]>>:
>>>>>
>>>>>     I need to build Python 3.5 for the EB 2.9.0 toolchain
>>>>> foss-2016.09.
>>>>>     I copied the file Python-3.5.2-foss-2016.04.eb and replaced 04
>>>>> by 09.
>>>>>
>>>>>     Unfortunately, irresolvable dependencies are found:
>>>>>
>>>>>     # eb Python-3.5.2-foss-2016.09.eb -r
>>>>>     == temporary log file in case of crash
>>>>>     /tmp/eb-mvPeVH/easybuild-tixAOo.log
>>>>>     == resolving dependencies ...
>>>>>     ERROR: Irresolvable dependencies encountered:
>>>>>     bzip2/1.0.6-foss-2016.09,
>>>>>     zlib/1.2.8-foss-2016.09, libreadline/6.3-foss-2016.09,
>>>>>     ncurses/6.0-foss-2016.09, SQLite/3.13.0-foss-2016.09,
>>>>>     Tk/8.6.5-foss-2016.09, GMP/6.1.1-foss-2016.09,
>>>>> XZ/5.2.2-foss-2016.09,
>>>>>     libffi/3.2.1-foss-2016.09
>>>>>
>>>>>     I suppose that these dependencies could be built independently
>>>>> of the
>>>>>     foss toolchain.
>>>>>
>>>>>     Question: Does anyone have a working EB file
>>>>>     Python-3.5.2-foss-2016.09.eb?
>>>>>
>>>>>     Thanks a lot,
>>>>>     Ole
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Pablo Escobar López
>>>>> HPC systems engineer
>>>>> sciCORE, University of Basel
>>>>> SIB Swiss Institute of Bioinformatics
>>>>> http://scicore.unibas.ch
>>>>
>>>
>>
>


--
Dr. Markus Geimer
Juelich Supercomputing Centre
Institute for Advanced Simulation
Forschungszentrum Juelich GmbH
52425 Juelich, Germany

Phone:  +49-2461-61-1773
Fax:    +49-2461-61-6656
E-mail: [email protected]
WWW:    http://www.fz-juelich.de/jsc/



------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------

Reply via email to