On 08/01/2018 21:28, Jakob Schiøtz wrote:
On 8 Jan 2018, at 20:27, Kenneth Hoste wrote:
On 08/01/2018 15:48, Jakob Schiøtz wrote:
Hi Kenneth,
I have now tested your TensorFlow 1.4.0 eb on our machines with a real-world
script. It works, but it runs three times
> On 8 Jan 2018, at 20:27, Kenneth Hoste wrote:
>
> On 08/01/2018 15:48, Jakob Schiøtz wrote:
>> Hi Kenneth,
>>
>> I have now tested your TensorFlow 1.4.0 eb on our machines with a real-world
>> script. It works, but it runs three times slower than with the prebuild
On 08/01/2018 15:48, Jakob Schiøtz wrote:
Hi Kenneth,
I have now tested your TensorFlow 1.4.0 eb on our machines with a real-world
script. It works, but it runs three times slower than with the prebuild
TensorFlow 1.2.1 :-(
The prebuild version complains that it was build without AVX2 etc,
On 05/01/2018 17:28, Jakob Schiøtz wrote:
Hi again, Kenneth.
It turns out that I was wrong about the lack of internet access from the
compute nodes. In principle, there should be nothing stopping me from testing
building with GPUs next week, except for my lack of knowledge :-)
I see this
Hi Jakob,
On 05/01/2018 16:10, Jakob Schiøtz wrote:
On 5 Jan 2018, at 15:18, Kenneth Hoste wrote:
On 05/01/2018 14:13, Jakob Schiøtz wrote:
Hi again,
Yes, I have overlooked that - I just switched my repo to your branch and tried
to build :-)
Now I get an error
On 08/01/2018 13:58, Caspar van Leeuwen wrote:
I disagree, because the requirement that the variable 'BAR_BIN' that is set is
a requirement from Foo, not a 'feature' from Bar. Bar knows absolutely nothing
about this variable, and is very happy to run without it - thus it has no place
in a Bar
On 08/01/2018 14:09, Mikael Öhman wrote:
Alans answer is probably the best, but
`BAR_BIN`: '`which bar`'
might work as an alternativ to the Tcl specific hack (untested).
This won't work: `which bar` has no meaning in a module file (which is
not a shell script).
K.
On Mon, Jan 8, 2018
On 08/01/2018 15:07, Åke Sandgren wrote:
On 01/08/2018 01:58 PM, Caspar van Leeuwen wrote:
I disagree, because the requirement that the variable 'BAR_BIN' that is set is
a requirement from Foo, not a 'feature' from Bar. Bar knows absolutely nothing
about this variable, and is very happy to
Hi Kenneth,
I have now tested your TensorFlow 1.4.0 eb on our machines with a real-world
script. It works, but it runs three times slower than with the prebuild
TensorFlow 1.2.1 :-(
The prebuild version complains that it was build without AVX2 etc, so I do not
really understand why it is so
On Mon, Jan 8, 2018 at 3:07 PM, Åke Sandgren
wrote:
>
>
> On 01/08/2018 01:58 PM, Caspar van Leeuwen wrote:
> > I disagree, because the requirement that the variable 'BAR_BIN' that is
> set is a requirement from Foo, not a 'feature' from Bar. Bar knows
> absolutely
On 01/08/2018 01:58 PM, Caspar van Leeuwen wrote:
> I disagree, because the requirement that the variable 'BAR_BIN' that is set
> is a requirement from Foo, not a 'feature' from Bar. Bar knows absolutely
> nothing about this variable, and is very happy to run without it - thus it
> has no
Alans answer is probably the best, but
`BAR_BIN`: '`which bar`'
might work as an alternativ to the Tcl specific hack (untested).
On Mon, Jan 8, 2018 at 2:01 PM, Alan O'Cais wrote:
> Hi Caspar,
>
> You can use
> modextravars = { 'BAR_BIN': '%(installdir)s/bin'}
> in the
Hi Caspar,
You can use
modextravars = { 'BAR_BIN': '%(installdir)s/bin'}
in the Bar easyconfig. If Bar is a dep of Foo, then when Foo is loaded Bar
will be too and the value will be set. If you *only *want this to be set if
Foo is loaded then that is custom behaviour and you will need to write a
I disagree, because the requirement that the variable 'BAR_BIN' that is set is
a requirement from Foo, not a 'feature' from Bar. Bar knows absolutely nothing
about this variable, and is very happy to run without it - thus it has no place
in a Bar module. To illustrate that more: what if someone
I'm sorry, maybe I should have clarified: Foo requires BAR_BIN to be present at
runtime , so yes, I really do want it to be set in the module file of Foo. Foo
provides a (GUI) wrapper for Bar, but it needs to know the location of the Bar
binary. Rather than searching the path - as other
I think you are misunderstanding the scope of modextravars, it is there to set
additional variables in the resultant module file from the installation (it is
not relevant to the install process of the software, only the final module file
that is written). The modextravars should be set in the
Dear EasyBuilders,
Question: I have a Package Foo that provides a wrapper for a software package
Bar. Thus, in the EasyConfig for Foo, I list Bar as a dependency.
Now, Foo requires an environment variable BAR_BIN to be set that points to the
Bar binary. Thus, what I would like to do
You could use ConfigureMake easyblock and skip configure step.
Cheers
2018-01-08 21:15 GMT+10:30 Espen Tangen :
> For instance Lua/5.3.4 - how do I do it?
>
>
>
> I have started with the binary block, and altered slightly the Lua config
> that does exist for mclays
For instance Lua/5.3.4 - how do I do it?
I have started with the binary block, and altered slightly the Lua config that
does exist for mclays flavored one.
Any tips?
Et.
Dear EasyBuilders,
After over 5 years of (stable) EasyBuild releases, we felt it was time
to try and get a better view on the EasyBuild community through a short
user survey.
Please take some time to fill it out at
https://nl.surveymonkey.com/r/easybuild_user_survey .
This should take only
20 matches
Mail list logo