On 01/20/2017 02:52 PM, Siddiqui, Shahzeb wrote:
Hi Jack,
Can you please send us the easyconfig file so that I can try it out.
Thanks,
Howdy,
I posted it to the list two days ago:
https://lists.ugent.be/wws/arc/easybuild/2017-01/msg00036.html
but you can also get it in the tarball here:
h
Hi Jack,
Can you please send us the easyconfig file so that I can try it out.
Thanks,
-Original Message-
From: easybuild-requ...@lists.ugent.be
[mailto:easybuild-requ...@lists.ugent.be] On Behalf Of Jack Perdue
Sent: Friday, January 20, 2017 9:54 AM
To: easybuild@lists.ugent.be
Subject:
On 20/01/2017 10:49, Alvarez, Damian wrote:
I like it. I wanted actually to make PR including an extra “contact” field in
the easyconfig file (we currently have it simply included in the description),
but yours is way more complete.
+1, this sounds like a very well worked out proposal provi
On 20/01/2017 10:10, Markus Geimer wrote:
(unfortunately, I don't think EasyBuild has a tag for a "module load"
message).
It should be fairly straightforward to support that as well (if
you want to hard-code this into the modulefile rather than using
Lmod's admin.list approach).
This *is* al
Hi
I used old Ifort (version 12). I need to compile Open-MPI for example
and another programs. I tried to edit some easyconfig files. However
does no work. I see toolchains. My question is. Can I use my local
compilers inside some files?
For example I need compile VASP with OpenMPI and Ifort
On 01/20/2017 08:01 AM, Kenneth Hoste wrote:
On 20/01/2017 14:56, Jack Perdue wrote:
On 01/20/2017 07:31 AM, Siddiqui, Shahzeb wrote:
Ken,
Can you have your team look into this issue, try to build
Intel-Python I have provided and get a working solution.
Thanks
-Original Message-
F
On 20/01/2017 14:56, Jack Perdue wrote:
On 01/20/2017 07:31 AM, Siddiqui, Shahzeb wrote:
Ken,
Can you have your team look into this issue, try to build
Intel-Python I have provided and get a working solution.
Thanks
-Original Message-
From: easybuild-requ...@lists.ugent.be
[mailt
On 01/20/2017 07:31 AM, Siddiqui, Shahzeb wrote:
Ken,
Can you have your team look into this issue, try to build Intel-Python I have
provided and get a working solution.
Thanks
-Original Message-
From: easybuild-requ...@lists.ugent.be
[mailto:easybuild-requ...@lists.ugent.be] On Behal
Ken,
Can you have your team look into this issue, try to build Intel-Python I have
provided and get a working solution.
Thanks
-Original Message-
From: easybuild-requ...@lists.ugent.be
[mailto:easybuild-requ...@lists.ugent.be] On Behalf Of Ole Holm Nielsen
Sent: Thursday, January 19,
Am I reading about one of the developments planned for the User Meeting?
On 20 January 2017 at 11:03, Markus Geimer wrote:
> On 01/20/17 10:49, Alvarez, Damian wrote:
> > I like it. I wanted actually to make PR including an extra “contact”
> > field in the easyconfig file (we currently have it s
On 01/20/17 10:49, Alvarez, Damian wrote:
> I like it. I wanted actually to make PR including an extra “contact”
> field in the easyconfig file (we currently have it simply included in
> the description), but yours is way more complete. However, just as a
> side note, empty fields should not be cre
I like it. I wanted actually to make PR including an extra “contact” field in
the easyconfig file (we currently have it simply included in the description),
but yours is way more complete. However, just as a side note, empty fields
should not be created. Having an “usage section” that is empty i
All,
>> I have noticed a slightly annoying (if small) side effect of the move
>> to lua module files. Specifically, module help and whatis statements
>> will now be split up across multiple lines if they are so formatted in
>> the easyconfig. An example follows at the end of this message.
>> [...]
On Thu, Jan 19, 2017 at 10:38 PM, Ben Roberts wrote:
> This is a problem for me and my site as we prepare our lists of modules by
> looking at the output of “module whatis”. While we could post-process that
> output, it is somewhat tedious and error prone to have to do so. The
> formatting may als
14 matches
Mail list logo