Re: [easybuild] Local user intstallation

[Miguel Costa]

Hello Davide,

On 28 Jun 2017 02:43, "Vanzo, Davide"  wrote:

So, I gave it a try and it works fine.

The only annoyance (since it is more a matter of style) is that once I add
the $EB_GLOBAL_PREFIX/modules/all to the $MODULEPATH, Lmod output for
"module avail" gets pretty crowded.


I know what you mean :)

I was simplifying, I don't actually expose modules/all to normal users by
default (they can always add it later, either by changing MODULEPATH
directly or running "module use ...")

Besides the module classes and hidden modules, what works for me is
grouping the modules by toolchain (could this be added as a feature?) and
exposing those groups separately

This has allowed me to, for instance, "deprecate" toolchains that created
problems in many of our applications (again, users can add them back
manually)

You call also use the ordering in MODULEPATH to put a desired group at the
top or bottom of the output of "module avail" (it would be interesting if
lmod had a customizable "module shortlist" command...)

Don't know how all this changes if you're using HMNS (see Alan's message)

Miguel




-- 
Davide Vanzo, PhD
Application Developer
Advanced Computing Center for Research and Education (ACCRE)
Vanderbilt University - Hill Center 201
(615)-875-9137 <(615)%20875-9137>
www.accre.vanderbilt.edu

On Jun 27 2017, at 10:43 am, Vanzo, Davide 
wrote:

> Thank you all for the great suggestions!
>
> DV
>
>
> On Jun 27 2017, at 3:14 am, Miguel Dias Costa 
> wrote:
>
>
>
> On 27/06/17 15:42, Alan O'Cais wrote:
>
> That is a neat trick with the sourcepaths that I will try out today.
>
>
> I have to credit boegel, he told me about it, I had simply assumed that
> would not work :)
>
>
> I think there is a bit more to a user install space than what's been
> mentioned when you have a HMNS, see https://github.com/
> hpcugent/easybuild-framework/issues/2143
>
>
> ah... because there are then two roots to the hierarchy, the global one
> and the local one?
>
> Miguel
>
>
> On 27 June 2017 at 03:09, Fotis Georgatos  wrote:
>
>
> Hi Miguel,
>
> Yeap! i’d also fully applause this approach, it is very similar to what
> we’ve been doing since 2012!
> - $MODULEPATH can include both global and local builds, you just need to
> decide their exact order
>   * fyi. recent versions of Lmod have in ./contrib a pair of use.own.eb
> modulefiles, implementing the above
> - the global install, is nothing more than by yet another user, which just
> happens to be steered by admin
> - i also encourage people to add a versionsuffix with their initials and
> maybe a date, to keep things apart
>
> The trick with EASYBUILD_SOURCEPATH is quite nice, it could also be used
> within use.own.eb/* modulefiles,
> assuming that it is always *prepend*, as you described.
>
> F.
>
> On Jun 27, 2017, at 1:57 AM, Miguel Costa 
> wrote:
> > Hello Davide,
> >
> > I also had doubts initially because of what you mention and also using
> global source paths, but this works for us:
> >
> > - create and manage a cluster-wide software stack with an easybuild
> user, using EASYBUILD_PREFIX=$EB_GLOBAL_PREFIX
> >
> > - for normal users
> >
> >   - set EASYBUILD_PREFIX=$HOME/.local/easybuild but add
> $EB_GLOBAL_PREFIX/modules/all to the $MODULEPATH (so that it finds the
> already globally installed software)
> >
> >   - set 
> > EASYBUILD_SOURCEPATH=$HOME/.local/easybuild/sources:$EB_GLOBAL_PREFIX/sources,
> in this order (so that it downloads to local but looks in global). This was
> recently clarified in the documentation, last line in
> https://easybuild.readthedocs.io/en/latest/Configuration.htm
> l?highlight=sourcepath#sourcepath
> >
> > I think this is enough.
> >
> > Miguel
> >
> > P.S. I encourage users to always add a versionsuffix in case they are
> rebuilding a package that already exists globally, otherwise which one gets
> picked depends on the order of the folders in $MODULEPATH
>
>
> --
> echo "sysadmin know better bash than english" | sed s/min/mins/ \
>   | sed 's/better bash/bash better/' # signal detected in a CERN forum
>
>
>
>
>
>
>
>
>
>
> --
> Dr. Alan O'Cais
> E-CAM Software Manager
> Juelich Supercomputing Centre
> Forschungszentrum Juelich GmbH
> 52425 Juelich, Germany
>
> Phone: +49 2461 61 5213 <+49%202461%20615213>
> Fax: +49 2461 61 6656 <+49%202461%20616656>
> E-mail: a.oc...@fz-juelich.de
> WWW:http://www.fz-juelich.de/ias/jsc/EN
>
>
> 
> 
> 
> 
> 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
> 

Re: [easybuild] installation issue

[Ernesto Eduardo Diaz Conde]

y was wrong, the first two i run as root.

now i do it in the same session without root privileges and this was the
output

admremote@monitoring-system:~$ easy_install --verbose --prefix /tmp/test
easybuild
Creating /tmp/test/lib/python2.7/site-packages/site.py
byte-compiling /tmp/test/lib/python2.7/site-packages/site.py to site.pyc
Searching for easybuild
Reading https://pypi.python.org/simple/easybuild/
Download error on https://pypi.python.org/simple/easybuild/: Tunnel
connection failed: 407 Proxy Authentication Required -- Some packages may
not be found!
Couldn't find index page for 'easybuild' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: Tunnel connection
failed: 407 Proxy Authentication Required -- Some packages may not be found!
No local packages or download links found for easybuild
error: Could not find suitable distribution for
Requirement.parse('easybuild')

i presume that the errror is caused by a conection problem i will try to
fixed, and then will run again


2017-06-27 16:15 GMT-03:00 Kenneth Hoste :

> Hi Ernesto,
>
> On 27/06/2017 21:08, Ernesto Eduardo Diaz Conde wrote:
>
> after do
>
> mkdir -p /tmp/test/lib/python2.7/site-packages
> export PYTHONPATH=/tmp/test/lib/python2.7/site-packages:$PYTHONPATH
>
> i run again
>
> easy_install --verbose --prefix /tmp/test easybuild
>
>
> Are you running all 3 commands in the same session?
>
> The output of easy_install mentions that $PYTHONPATH is defined empty?
>
>
> regards,
>
> Kenneth
>
>
> same output
>
> TEST FAILED: /tmp/test/lib/python2.7/site-packages does NOT support .pth
> files
> error: bad install directory or PYTHONPATH
>
> You are attempting to install a package to a directory that is not
> on PYTHONPATH and which Python does not read ".pth" files from.  The
> installation directory you specified (via --install-dir, --prefix, or
> the distutils default setting) was:
>
> /tmp/test/lib/python2.7/site-packages
>
> and your PYTHONPATH environment variable currently contains:
>
> ''
>
> Here are some of your options for correcting the problem:
>
> * You can choose a different installation directory, i.e., one that is
>   on PYTHONPATH or supports .pth files
>
> * You can add the installation directory to the PYTHONPATH environment
>   variable.  (It must then also be on PYTHONPATH whenever you run
>   Python and want to use the package(s) you are installing.)
>
> * You can set up the installation directory to support ".pth" files by
>   using one of the approaches described here:
>
>   https://pythonhosted.org/setuptools/easy_install.html#
> custom-installation-locations
>
> Please make the appropriate changes for your system and try again.
>
>
> 2017-06-27 15:36 GMT-03:00 Kenneth Hoste :
>
>> Dear Ernesto,
>>
>> OK, I overlooked some, try this please:
>>
>> mkdir -p /tmp/test/lib/python2.7/site-packages
>> export PYTHONPATH=/tmp/test/lib/python2.7/site-packages:$PYTHONPATH
>> easy_install --verbose --prefix /tmp/test easybuild
>>
>>
>> regards,
>>
>> Kenneth
>>
>> On 27/06/2017 19:05, Ernesto Eduardo Diaz Conde wrote:
>>
>> this is the output for
>>
>> easy_install --verbose --prefix /tmp/test easybuild
>>
>> admremote@monitoring-system:~$ easy_install --verbose --prefix /tmp/test
>> easybuild
>> TEST FAILED: /tmp/test/lib/python2.7/site-packages does NOT support .pth
>> files
>> error: bad install directory or PYTHONPATH
>>
>> You are attempting to install a package to a directory that is not
>> on PYTHONPATH and which Python does not read ".pth" files from.  The
>> installation directory you specified (via --install-dir, --prefix, or
>> the distutils default setting) was:
>>
>> /tmp/test/lib/python2.7/site-packages
>>
>> and your PYTHONPATH environment variable currently contains:
>>
>> ''
>>
>> Here are some of your options for correcting the problem:
>>
>> * You can choose a different installation directory, i.e., one that is
>>   on PYTHONPATH or supports .pth files
>>
>> * You can add the installation directory to the PYTHONPATH environment
>>   variable.  (It must then also be on PYTHONPATH whenever you run
>>   Python and want to use the package(s) you are installing.)
>>
>> * You can set up the installation directory to support ".pth" files by
>>   using one of the approaches described here:
>>
>>   https://pythonhosted.org/setuptools/easy_install.html#custom
>> -installation-locations
>>
>> Please make the appropriate changes for your system and try again.
>>
>>
>> 2017-06-27 13:46 GMT-03:00 Kenneth Hoste :
>>
>>> Hi Ernesto,
>>>
>>> (let's keep the mailing list in CC, since this may help others in the
>>> future)
>>>
>>> I meant try this:
>>>
>>> easy_install --verbose --prefix /tmp/test easybuild
>>>
>>>
>>> regards,
>>>
>>> Kenneth
>>>
>>>
>>> On 27/06/2017 17:15, Ernesto Eduardo Diaz Conde wrote:
>>>
>>> Hello Kenneth
>>>
>>> I arrived las week to the office, i see the notification of the 

Re: [easybuild] installation issue

[Kenneth Hoste]

Hi Ernesto,

On 27/06/2017 21:08, Ernesto Eduardo Diaz Conde wrote:

after do

mkdir -p /tmp/test/lib/python2.7/site-packages
export PYTHONPATH=/tmp/test/lib/python2.7/site-packages:$PYTHONPATH

i run again

easy_install --verbose --prefix /tmp/test easybuild


Are you running all 3 commands in the same session?

The output of easy_install mentions that $PYTHONPATH is defined empty?


regards,

Kenneth


same output

TEST FAILED: /tmp/test/lib/python2.7/site-packages does NOT support 
.pth files

error: bad install directory or PYTHONPATH

You are attempting to install a package to a directory that is not
on PYTHONPATH and which Python does not read ".pth" files from.  The
installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

/tmp/test/lib/python2.7/site-packages

and your PYTHONPATH environment variable currently contains:

''

Here are some of your options for correcting the problem:

* You can choose a different installation directory, i.e., one that is
  on PYTHONPATH or supports .pth files

* You can add the installation directory to the PYTHONPATH environment
  variable.  (It must then also be on PYTHONPATH whenever you run
  Python and want to use the package(s) you are installing.)

* You can set up the installation directory to support ".pth" files by
  using one of the approaches described here:

https://pythonhosted.org/setuptools/easy_install.html#custom-installation-locations

Please make the appropriate changes for your system and try again.


2017-06-27 15:36 GMT-03:00 Kenneth Hoste >:


Dear Ernesto,

OK, I overlooked some, try this please:

mkdir -p /tmp/test/lib/python2.7/site-packages
export PYTHONPATH=/tmp/test/lib/python2.7/site-packages:$PYTHONPATH
easy_install --verbose --prefix /tmp/test easybuild


regards,

Kenneth

On 27/06/2017 19:05, Ernesto Eduardo Diaz Conde wrote:

this is the output for

easy_install --verbose --prefix /tmp/test easybuild

admremote@monitoring-system:~$ easy_install --verbose --prefix
/tmp/test easybuild
TEST FAILED: /tmp/test/lib/python2.7/site-packages does NOT
support .pth files
error: bad install directory or PYTHONPATH

You are attempting to install a package to a directory that is not
on PYTHONPATH and which Python does not read ".pth" files from.  The
installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

/tmp/test/lib/python2.7/site-packages

and your PYTHONPATH environment variable currently contains:

''

Here are some of your options for correcting the problem:

* You can choose a different installation directory, i.e., one
that is
  on PYTHONPATH or supports .pth files

* You can add the installation directory to the PYTHONPATH
environment
  variable.  (It must then also be on PYTHONPATH whenever you run
  Python and want to use the package(s) you are installing.)

* You can set up the installation directory to support ".pth"
files by
  using one of the approaches described here:


https://pythonhosted.org/setuptools/easy_install.html#custom-installation-locations



Please make the appropriate changes for your system and try again.


2017-06-27 13:46 GMT-03:00 Kenneth Hoste mailto:kenneth.ho...@ugent.be>>:

Hi Ernesto,

(let's keep the mailing list in CC, since this may help
others in the future)

I meant try this:

easy_install --verbose --prefix /tmp/test easybuild


regards,

Kenneth


On 27/06/2017 17:15, Ernesto Eduardo Diaz Conde wrote:

Hello Kenneth

I arrived las week to the office, i see the notification of
the new version of easybuild, but i continue having the same
error. i do what you tell me

Can you try with "easy_install --verbose ..." to see if that
gives more information and what goes wrong?

this was the outputadmremote@monitoring-system:~$
easy_install --verbose
error: No urls, filenames, or requirements specified (see
--help)


2017-06-15 11:52 GMT-03:00 Ernesto Eduardo Diaz Conde
mailto:eediaz1...@gmail.com>>:

i download the page from the system using wget

2017-06-15 11:48 GMT-03:00 Kenneth Hoste
mailto:kenneth.ho...@ugent.be>>:



On 15/06/2017 16:33, Ernesto Eduardo Diaz Conde wrote:



2017-06-15 6:02 GMT-03:00 Kenneth Hoste
mailto:kenneth.ho...@ugent.be>>:

Dear Ernesto,

It seems that setuptools isn't able to download
EasyBuild from PyPI () for some reason.

Are you seeing the same problem with this command?

  

Re: [easybuild] installation issue

[Ernesto Eduardo Diaz Conde]

after do

mkdir -p /tmp/test/lib/python2.7/site-packages
export PYTHONPATH=/tmp/test/lib/python2.7/site-packages:$PYTHONPATH

i run again

easy_install --verbose --prefix /tmp/test easybuild

same output

TEST FAILED: /tmp/test/lib/python2.7/site-packages does NOT support .pth
files
error: bad install directory or PYTHONPATH

You are attempting to install a package to a directory that is not
on PYTHONPATH and which Python does not read ".pth" files from.  The
installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

/tmp/test/lib/python2.7/site-packages

and your PYTHONPATH environment variable currently contains:

''

Here are some of your options for correcting the problem:

* You can choose a different installation directory, i.e., one that is
  on PYTHONPATH or supports .pth files

* You can add the installation directory to the PYTHONPATH environment
  variable.  (It must then also be on PYTHONPATH whenever you run
  Python and want to use the package(s) you are installing.)

* You can set up the installation directory to support ".pth" files by
  using one of the approaches described here:


https://pythonhosted.org/setuptools/easy_install.html#custom-installation-locations

Please make the appropriate changes for your system and try again.


2017-06-27 15:36 GMT-03:00 Kenneth Hoste :

> Dear Ernesto,
>
> OK, I overlooked some, try this please:
>
> mkdir -p /tmp/test/lib/python2.7/site-packages
> export PYTHONPATH=/tmp/test/lib/python2.7/site-packages:$PYTHONPATH
> easy_install --verbose --prefix /tmp/test easybuild
>
>
> regards,
>
> Kenneth
>
> On 27/06/2017 19:05, Ernesto Eduardo Diaz Conde wrote:
>
> this is the output for
>
> easy_install --verbose --prefix /tmp/test easybuild
>
> admremote@monitoring-system:~$ easy_install --verbose --prefix /tmp/test
> easybuild
> TEST FAILED: /tmp/test/lib/python2.7/site-packages does NOT support .pth
> files
> error: bad install directory or PYTHONPATH
>
> You are attempting to install a package to a directory that is not
> on PYTHONPATH and which Python does not read ".pth" files from.  The
> installation directory you specified (via --install-dir, --prefix, or
> the distutils default setting) was:
>
> /tmp/test/lib/python2.7/site-packages
>
> and your PYTHONPATH environment variable currently contains:
>
> ''
>
> Here are some of your options for correcting the problem:
>
> * You can choose a different installation directory, i.e., one that is
>   on PYTHONPATH or supports .pth files
>
> * You can add the installation directory to the PYTHONPATH environment
>   variable.  (It must then also be on PYTHONPATH whenever you run
>   Python and want to use the package(s) you are installing.)
>
> * You can set up the installation directory to support ".pth" files by
>   using one of the approaches described here:
>
>   https://pythonhosted.org/setuptools/easy_install.html#
> custom-installation-locations
>
> Please make the appropriate changes for your system and try again.
>
>
> 2017-06-27 13:46 GMT-03:00 Kenneth Hoste :
>
>> Hi Ernesto,
>>
>> (let's keep the mailing list in CC, since this may help others in the
>> future)
>>
>> I meant try this:
>>
>> easy_install --verbose --prefix /tmp/test easybuild
>>
>>
>> regards,
>>
>> Kenneth
>>
>>
>> On 27/06/2017 17:15, Ernesto Eduardo Diaz Conde wrote:
>>
>> Hello Kenneth
>>
>> I arrived las week to the office, i see the notification of the new
>> version of easybuild, but i continue having the same error. i do what you
>> tell me
>>
>> Can you try with "easy_install --verbose ..." to see if that gives more
>> information and what goes wrong?
>>
>> this was the outputadmremote@monitoring-system:~$ easy_install --verbose
>> error: No urls, filenames, or requirements specified (see --help)
>>
>>
>> 2017-06-15 11:52 GMT-03:00 Ernesto Eduardo Diaz Conde <
>> eediaz1...@gmail.com>:
>>
>>> i download the page from the system using wget
>>>
>>> 2017-06-15 11:48 GMT-03:00 Kenneth Hoste :
>>>


 On 15/06/2017 16:33, Ernesto Eduardo Diaz Conde wrote:



 2017-06-15 6:02 GMT-03:00 Kenneth Hoste :

> Dear Ernesto,
>
> It seems that setuptools isn't able to download EasyBuild from PyPI ()
> for some reason.
>
> Are you seeing the same problem with this command?
>
> easy_install --prefix /tmp/test easybuild
>
> Yes with command the error is the same

 Can you try with "easy_install --verbose ..." to see if that gives more
 information and what goes wrong?



> Is https://pypi.python.org/pypi/easybuild reachable from that system
>

 Yes the page is reachable fron the system


 How did you test this exactly, which command did you run?


 regards,

 Kenneth



> If not, you can try the offline mode supported by the bootstrap
> script, see http://easybuild.readthedocs.i
> o/en/latest/Installation.html#

Re: [easybuild] Local user intstallation

[Vanzo, Davide]

So, I gave it a try and it works fine.

The only annoyance (since it is more a matter of style) is that once I add the 
$EB_GLOBAL_PREFIX/modules/all to the $MODULEPATH, Lmod output for "module 
avail" gets pretty crowded.

--
Davide Vanzo, PhD
Application Developer
Advanced Computing Center for Research and Education (ACCRE)
Vanderbilt University - Hill Center 201
(615)-875-9137
www.accre.vanderbilt.edu

On Jun 27 2017, at 10:43 am, Vanzo, Davide  wrote:
Thank you all for the great suggestions!

DV


On Jun 27 2017, at 3:14 am, Miguel Dias Costa  wrote:


On 27/06/17 15:42, Alan O'Cais wrote:
That is a neat trick with the sourcepaths that I will try out today.

I have to credit boegel, he told me about it, I had simply assumed that would 
not work :)


I think there is a bit more to a user install space than what's been mentioned 
when you have a HMNS, see 
https://github.com/hpcugent/easybuild-framework/issues/2143

ah... because there are then two roots to the hierarchy, the global one and the 
local one?

Miguel


On 27 June 2017 at 03:09, Fotis Georgatos 
mailto:fo...@mail.cern.ch>> wrote:

Hi Miguel,

Yeap! i’d also fully applause this approach, it is very similar to what we’ve 
been doing since 2012!
- $MODULEPATH can include both global and local builds, you just need to decide 
their exact order
  * fyi. recent versions of Lmod have in ./contrib a pair of use.own.eb 
modulefiles, implementing the above
- the global install, is nothing more than by yet another user, which just 
happens to be steered by admin
- i also encourage people to add a versionsuffix with their initials and maybe 
a date, to keep things apart

The trick with EASYBUILD_SOURCEPATH is quite nice, it could also be used within 
use.own.eb/* modulefiles,
assuming that it is always *prepend*, as you described.

F.

On Jun 27, 2017, at 1:57 AM, Miguel Costa 
mailto:migueldiasco...@gmail.com>> wrote:
> Hello Davide,
>
> I also had doubts initially because of what you mention and also using global 
> source paths, but this works for us:
>
> - create and manage a cluster-wide software stack with an easybuild user, 
> using EASYBUILD_PREFIX=$EB_GLOBAL_PREFIX
>
> - for normal users
>
>   - set EASYBUILD_PREFIX=$HOME/.local/easybuild but add 
> $EB_GLOBAL_PREFIX/modules/all to the $MODULEPATH (so that it finds the 
> already globally installed software)
>
>   - set 
> EASYBUILD_SOURCEPATH=$HOME/.local/easybuild/sources:$EB_GLOBAL_PREFIX/sources,
>  in this order (so that it downloads to local but looks in global). This was 
> recently clarified in the documentation, last line in 
> https://easybuild.readthedocs.io/en/latest/Configuration.html?highlight=sourcepath#sourcepath
>
> I think this is enough.
>
> Miguel
>
> P.S. I encourage users to always add a versionsuffix in case they are 
> rebuilding a package that already exists globally, otherwise which one gets 
> picked depends on the order of the folders in $MODULEPATH


--
echo "sysadmin know better bash than english" | sed s/min/mins/ \
  | sed 's/better bash/bash better/' # signal detected in a CERN forum










--
Dr. Alan O'Cais
E-CAM Software Manager
Juelich Supercomputing Centre
Forschungszentrum Juelich GmbH
52425 Juelich, Germany

Phone: +49 2461 61 5213
Fax: +49 2461 61 6656
E-mail: a.oc...@fz-juelich.de
WWW:http://www.fz-juelich.de/ias/jsc/EN




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

Re: [easybuild] installation issue

[Kenneth Hoste]

Dear Ernesto,

OK, I overlooked some, try this please:

mkdir -p /tmp/test/lib/python2.7/site-packages
export PYTHONPATH=/tmp/test/lib/python2.7/site-packages:$PYTHONPATH
easy_install --verbose --prefix /tmp/test easybuild


regards,

Kenneth

On 27/06/2017 19:05, Ernesto Eduardo Diaz Conde wrote:

this is the output for

easy_install --verbose --prefix /tmp/test easybuild

admremote@monitoring-system:~$ easy_install --verbose --prefix 
/tmp/test easybuild
TEST FAILED: /tmp/test/lib/python2.7/site-packages does NOT support 
.pth files

error: bad install directory or PYTHONPATH

You are attempting to install a package to a directory that is not
on PYTHONPATH and which Python does not read ".pth" files from.  The
installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

/tmp/test/lib/python2.7/site-packages

and your PYTHONPATH environment variable currently contains:

''

Here are some of your options for correcting the problem:

* You can choose a different installation directory, i.e., one that is
  on PYTHONPATH or supports .pth files

* You can add the installation directory to the PYTHONPATH environment
  variable.  (It must then also be on PYTHONPATH whenever you run
  Python and want to use the package(s) you are installing.)

* You can set up the installation directory to support ".pth" files by
  using one of the approaches described here:

https://pythonhosted.org/setuptools/easy_install.html#custom-installation-locations

Please make the appropriate changes for your system and try again.


2017-06-27 13:46 GMT-03:00 Kenneth Hoste >:


Hi Ernesto,

(let's keep the mailing list in CC, since this may help others in
the future)

I meant try this:

easy_install --verbose --prefix /tmp/test easybuild


regards,

Kenneth


On 27/06/2017 17:15, Ernesto Eduardo Diaz Conde wrote:

Hello Kenneth

I arrived las week to the office, i see the notification of the
new version of easybuild, but i continue having the same error. i
do what you tell me

Can you try with "easy_install --verbose ..." to see if that
gives more information and what goes wrong?

this was the outputadmremote@monitoring-system:~$ easy_install
--verbose
error: No urls, filenames, or requirements specified (see --help)


2017-06-15 11:52 GMT-03:00 Ernesto Eduardo Diaz Conde
mailto:eediaz1...@gmail.com>>:

i download the page from the system using wget

2017-06-15 11:48 GMT-03:00 Kenneth Hoste
mailto:kenneth.ho...@ugent.be>>:



On 15/06/2017 16:33, Ernesto Eduardo Diaz Conde wrote:



2017-06-15 6:02 GMT-03:00 Kenneth Hoste
mailto:kenneth.ho...@ugent.be>>:

Dear Ernesto,

It seems that setuptools isn't able to download
EasyBuild from PyPI () for some reason.

Are you seeing the same problem with this command?

easy_install --prefix /tmp/test easybuild

Yes with command the error is the same

Can you try with "easy_install --verbose ..." to see if
that gives more information and what goes wrong?


Is https://pypi.python.org/pypi/easybuild
 reachable
from that system


Yes the page is reachable fron the system


How did you test this exactly, which command did you run?


regards,

Kenneth




If not, you can try the offline mode supported by
the bootstrap script, see

http://easybuild.readthedocs.io/en/latest/Installation.html#offline-bootstrapping-using-supplied-source-tarballs


.


I will try this. Tanks for help me



regards,

Ernesto


On 14/06/2017 15:31, Ernesto Eduardo Diaz Conde wrote:

here is the output

2017-06-14 10:11 GMT-03:00 Ernesto Eduardo Diaz
Conde mailto:eediaz1...@gmail.com>>:

Thanks Kenneth,

The error was the same in diferents OS, in
debian 8, and CentOS 7.3, i will run the
comands that you send me and send the output

Regards
Ernesto

2017-06-13 17:38 GMT-03:00 Kenneth Hoste
mailto:kenneth.ho...@ugent.be>>:

Hi Ernesto,

Hmm, it's not clear to me what's going
wrong here.

Which OS are you on?

Can you try bootstrapping EasyBuild with
debugging enable

Re: [easybuild] installation issue

[Ernesto Eduardo Diaz Conde]

this is the output for

easy_install --verbose --prefix /tmp/test easybuild

admremote@monitoring-system:~$ easy_install --verbose --prefix /tmp/test
easybuild
TEST FAILED: /tmp/test/lib/python2.7/site-packages does NOT support .pth
files
error: bad install directory or PYTHONPATH

You are attempting to install a package to a directory that is not
on PYTHONPATH and which Python does not read ".pth" files from.  The
installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

/tmp/test/lib/python2.7/site-packages

and your PYTHONPATH environment variable currently contains:

''

Here are some of your options for correcting the problem:

* You can choose a different installation directory, i.e., one that is
  on PYTHONPATH or supports .pth files

* You can add the installation directory to the PYTHONPATH environment
  variable.  (It must then also be on PYTHONPATH whenever you run
  Python and want to use the package(s) you are installing.)

* You can set up the installation directory to support ".pth" files by
  using one of the approaches described here:


https://pythonhosted.org/setuptools/easy_install.html#custom-installation-locations

Please make the appropriate changes for your system and try again.


2017-06-27 13:46 GMT-03:00 Kenneth Hoste :

> Hi Ernesto,
>
> (let's keep the mailing list in CC, since this may help others in the
> future)
>
> I meant try this:
>
> easy_install --verbose --prefix /tmp/test easybuild
>
>
> regards,
>
> Kenneth
>
>
> On 27/06/2017 17:15, Ernesto Eduardo Diaz Conde wrote:
>
> Hello Kenneth
>
> I arrived las week to the office, i see the notification of the new
> version of easybuild, but i continue having the same error. i do what you
> tell me
>
> Can you try with "easy_install --verbose ..." to see if that gives more
> information and what goes wrong?
>
> this was the outputadmremote@monitoring-system:~$ easy_install --verbose
> error: No urls, filenames, or requirements specified (see --help)
>
>
> 2017-06-15 11:52 GMT-03:00 Ernesto Eduardo Diaz Conde <
> eediaz1...@gmail.com>:
>
>> i download the page from the system using wget
>>
>> 2017-06-15 11:48 GMT-03:00 Kenneth Hoste :
>>
>>>
>>>
>>> On 15/06/2017 16:33, Ernesto Eduardo Diaz Conde wrote:
>>>
>>>
>>>
>>> 2017-06-15 6:02 GMT-03:00 Kenneth Hoste :
>>>
 Dear Ernesto,

 It seems that setuptools isn't able to download EasyBuild from PyPI ()
 for some reason.

 Are you seeing the same problem with this command?

 easy_install --prefix /tmp/test easybuild

 Yes with command the error is the same
>>>
>>> Can you try with "easy_install --verbose ..." to see if that gives more
>>> information and what goes wrong?
>>>
>>>
>>>
 Is https://pypi.python.org/pypi/easybuild reachable from that system

>>>
>>> Yes the page is reachable fron the system
>>>
>>>
>>> How did you test this exactly, which command did you run?
>>>
>>>
>>> regards,
>>>
>>> Kenneth
>>>
>>>
>>>
 If not, you can try the offline mode supported by the bootstrap script,
 see http://easybuild.readthedocs.io/en/latest/Installation.html#
 offline-bootstrapping-using-supplied-source-tarballs .

>>>
>>> I will try this. Tanks for help me
>>>


 regards,

 Ernesto


 On 14/06/2017 15:31, Ernesto Eduardo Diaz Conde wrote:

 here is the output

 2017-06-14 10:11 GMT-03:00 Ernesto Eduardo Diaz Conde <
 eediaz1...@gmail.com>:

> Thanks Kenneth,
>
> The error was the same in diferents OS, in debian 8, and CentOS 7.3, i
> will run the comands that you send me and send the output
>
> Regards
> Ernesto
>
> 2017-06-13 17:38 GMT-03:00 Kenneth Hoste :
>
>> Hi Ernesto,
>>
>> Hmm, it's not clear to me what's going wrong here.
>>
>> Which OS are you on?
>>
>> Can you try bootstrapping EasyBuild with debugging enabled, as
>> follows:
>>
>> export EASYBUILD_BOOTSTRAP_DEBUG=1
>> python bootstrap_eb.py $PREFIX 2>&1 | tee eb_bootstrap_debug.out
>>
>> And then send back eb_bootstrap_debug.out?
>>
>> regards,
>>
>> Kenneth
>>
>>
>> On 13/06/2017 21:00, Ernesto Eduardo Diaz Conde wrote:
>>
>> Hello
>> I have tried installing the new version of EasyBuil and am getting an
>> error like this:
>>
>>
>> [[INFO]] installing EasyBuild with 'easy_install --quiet --upgrade
>> --prefix=/tmp
>>
>> /tmpGNtTsT/eb_stage1 easybuild'
>> [[ERROR]] Running 'easy_install --quiet --upgrade
>> --prefix=/tmp/tmpGNtTsT/eb_stage1 easybuild' failed: error: Could
>> not find suitable distribution for Requirement.parse('easybuild')
>> Traceback (most recent call last):
>>   File "bootstrap_eb.py", line 337, in run_easy_install
>> easy_install.main(args)
>>   File 
>> "/usr/local/lib/python2.7/dist-packages/setuptools/command/easy_install.py",
>

Re: [easybuild] installation issue

[Kenneth Hoste]

Hi Ernesto,

(let's keep the mailing list in CC, since this may help others in the 
future)


I meant try this:

easy_install --verbose --prefix /tmp/test easybuild


regards,

Kenneth

On 27/06/2017 17:15, Ernesto Eduardo Diaz Conde wrote:

Hello Kenneth

I arrived las week to the office, i see the notification of the new 
version of easybuild, but i continue having the same error. i do what 
you tell me


Can you try with "easy_install --verbose ..." to see if that gives 
more information and what goes wrong?


this was the outputadmremote@monitoring-system:~$ easy_install --verbose
error: No urls, filenames, or requirements specified (see --help)


2017-06-15 11:52 GMT-03:00 Ernesto Eduardo Diaz Conde 
mailto:eediaz1...@gmail.com>>:


i download the page from the system using wget

2017-06-15 11:48 GMT-03:00 Kenneth Hoste mailto:kenneth.ho...@ugent.be>>:



On 15/06/2017 16:33, Ernesto Eduardo Diaz Conde wrote:



2017-06-15 6:02 GMT-03:00 Kenneth Hoste
mailto:kenneth.ho...@ugent.be>>:

Dear Ernesto,

It seems that setuptools isn't able to download EasyBuild
from PyPI () for some reason.

Are you seeing the same problem with this command?

easy_install --prefix /tmp/test easybuild

Yes with command the error is the same

Can you try with "easy_install --verbose ..." to see if that
gives more information and what goes wrong?


Is https://pypi.python.org/pypi/easybuild
 reachable from
that system


Yes the page is reachable fron the system


How did you test this exactly, which command did you run?


regards,

Kenneth




If not, you can try the offline mode supported by the
bootstrap script, see

http://easybuild.readthedocs.io/en/latest/Installation.html#offline-bootstrapping-using-supplied-source-tarballs


.


I will try this. Tanks for help me



regards,

Ernesto


On 14/06/2017 15:31, Ernesto Eduardo Diaz Conde wrote:

here is the output

2017-06-14 10:11 GMT-03:00 Ernesto Eduardo Diaz Conde
mailto:eediaz1...@gmail.com>>:

Thanks Kenneth,

The error was the same in diferents OS, in debian 8,
and CentOS 7.3, i will run the comands that you send
me and send the output

Regards
Ernesto

2017-06-13 17:38 GMT-03:00 Kenneth Hoste
mailto:kenneth.ho...@ugent.be>>:

Hi Ernesto,

Hmm, it's not clear to me what's going wrong here.

Which OS are you on?

Can you try bootstrapping EasyBuild with
debugging enabled, as follows:

export EASYBUILD_BOOTSTRAP_DEBUG=1
python bootstrap_eb.py $PREFIX 2>&1 | tee
eb_bootstrap_debug.out

And then send back eb_bootstrap_debug.out?

regards,

Kenneth


On 13/06/2017 21:00, Ernesto Eduardo Diaz Conde
wrote:

Hello
I have tried installing the new version of
EasyBuil and am getting an error like this:


[[INFO]] installing EasyBuild with
'easy_install --quiet --upgrade --prefix=/tmp
/tmpGNtTsT/eb_stage1 easybuild'
[[ERROR]] Running 'easy_install --quiet
--upgrade --prefix=/tmp/tmpGNtTsT/eb_stage1
easybuild' failed: error: Could not find
suitable distribution for
Requirement.parse('easybuild')
Traceback (most recent call last):
  File "bootstrap_eb.py", line 337, in
run_easy_install
easy_install.main(args)
  File

"/usr/local/lib/python2.7/dist-packages/setuptools/command/easy_install.py",
line 2265, in main
**kw
  File "/usr/lib/python2.7/distutils/core.py",
line 169, in setup
raise SystemExit, "error: " + str(msg)
SystemExit: error: Could not find suitable
distribution for Requirement.parse('easybuild')


I would appreciate the help if someone has
already solved it

Re: [easybuild] Local user intstallation

[Vanzo, Davide]

Thank you all for the great suggestions!

DV


On Jun 27 2017, at 3:14 am, Miguel Dias Costa  wrote:


On 27/06/17 15:42, Alan O'Cais wrote:
That is a neat trick with the sourcepaths that I will try out today.

I have to credit boegel, he told me about it, I had simply assumed that would 
not work :)


I think there is a bit more to a user install space than what's been mentioned 
when you have a HMNS, see 
https://github.com/hpcugent/easybuild-framework/issues/2143

ah... because there are then two roots to the hierarchy, the global one and the 
local one?

Miguel


On 27 June 2017 at 03:09, Fotis Georgatos 
mailto:fo...@mail.cern.ch>> wrote:

Hi Miguel,

Yeap! i’d also fully applause this approach, it is very similar to what we’ve 
been doing since 2012!
- $MODULEPATH can include both global and local builds, you just need to decide 
their exact order
  * fyi. recent versions of Lmod have in ./contrib a pair of use.own.eb 
modulefiles, implementing the above
- the global install, is nothing more than by yet another user, which just 
happens to be steered by admin
- i also encourage people to add a versionsuffix with their initials and maybe 
a date, to keep things apart

The trick with EASYBUILD_SOURCEPATH is quite nice, it could also be used within 
use.own.eb/* modulefiles,
assuming that it is always *prepend*, as you described.

F.

On Jun 27, 2017, at 1:57 AM, Miguel Costa 
mailto:migueldiasco...@gmail.com>> wrote:
> Hello Davide,
>
> I also had doubts initially because of what you mention and also using global 
> source paths, but this works for us:
>
> - create and manage a cluster-wide software stack with an easybuild user, 
> using EASYBUILD_PREFIX=$EB_GLOBAL_PREFIX
>
> - for normal users
>
>   - set EASYBUILD_PREFIX=$HOME/.local/easybuild but add 
> $EB_GLOBAL_PREFIX/modules/all to the $MODULEPATH (so that it finds the 
> already globally installed software)
>
>   - set 
> EASYBUILD_SOURCEPATH=$HOME/.local/easybuild/sources:$EB_GLOBAL_PREFIX/sources,
>  in this order (so that it downloads to local but looks in global). This was 
> recently clarified in the documentation, last line in 
> https://easybuild.readthedocs.io/en/latest/Configuration.html?highlight=sourcepath#sourcepath
>
> I think this is enough.
>
> Miguel
>
> P.S. I encourage users to always add a versionsuffix in case they are 
> rebuilding a package that already exists globally, otherwise which one gets 
> picked depends on the order of the folders in $MODULEPATH


--
echo "sysadmin know better bash than english" | sed s/min/mins/ \
  | sed 's/better bash/bash better/' # signal detected in a CERN forum










--
Dr. Alan O'Cais
E-CAM Software Manager
Juelich Supercomputing Centre
Forschungszentrum Juelich GmbH
52425 Juelich, Germany

Phone: +49 2461 61 5213
Fax: +49 2461 61 6656
E-mail: a.oc...@fz-juelich.de
WWW:http://www.fz-juelich.de/ias/jsc/EN




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

Re: [easybuild] 2017b common toolchains

[Jure Pečar]

On Tue, 27 Jun 2017 10:12:19 +0200
Kenneth Hoste  wrote:

> foss/2017b:
>  GCC 6.3.0 (*) + binutils 2.28
>  OpenMPI 2.1.1
>  OpenBLAS 0.2.19 (*)
>  FFTW 3.3.6(-pl2)
>  ScaLAPACK 2.0.2
> 
> (*) update expected in the coming weeks!

This certainly makes more sense than jumping to 7.1. I'm under impression that 
gcc .4 release is the one causing the least pain so until v7 hits .4, I'd also 
keep away :)


One interesting thing with new gcc is offloading, see 
https://gcc.gnu.org/wiki/Offloading ... do we have any ideas yet how to handle 
this from the software repository perspective, since it is at least partially 
hardware dependant?


And a more general question ... what do easybuilders think about LLVM? Is it at 
the state where having it as a base toolchain would make sense?


-- 

  Jurij Pečar
  HPC Engineer, IT Operations, IT Services
  EMBL Heidelberg, Meyerhofstraße 1, 69117, Heidelberg, Germany
  Room 13-401

Re: [easybuild] building mxnet

[Jure Pečar]

On Mon, 8 May 2017 12:27:55 +0200
Ward Poelmans  wrote:

> OK, they did something I didn't expect. Apparently commit 0d64855f741e04
> for nnvm was also added to mxnet itself. This makes that EB downloads
> the wrong tarball...
> 
> I've changed the commit I use of nnvm for now. I will look into the
> framework so we can specify from which url which tarball should be
> downloaded.

This now works fine. I've build mxnet from eb 3.3.0 for nehalem and sandybridge 
and sanity checks are passing, yay! :)

Just haswell remaining ... and boom. Sanity check for python fails with:

== 2017-06-27 11:05:27,003 extension.py:181 WARNING Extension: MXNet failed to 
install, cmd 
'/g/easybuild/x86_64/CentOS/7/haswell/software/Python/2.7.12-foss-2016b/bin/python
 -c "import mxnet"' (stdin: None) output: terminate called after throwing an 
instance of 'std::system_error'
  what():  Operation not permitted

Which is something I'm seeing for the first time. Google tells me that is is 
somehow related to -pthread or a bug in the code itself. Both seems unlikely 
since builds for different architectures passed.

Any hint how to figure out this one?


-- 

  Jurij Pečar
  HPC Engineer, IT Operations, IT Services
  EMBL Heidelberg, Meyerhofstraße 1, 69117, Heidelberg, Germany
  Room 13-401

Re: [easybuild] Local user intstallation

[Miguel Dias Costa]

On 27/06/17 15:42, Alan O'Cais wrote:

That is a neat trick with the sourcepaths that I will try out today.


I have to credit boegel, he told me about it, I had simply assumed that 
would not work :)




I think there is a bit more to a user install space than what's been 
mentioned when you have a HMNS, see 
https://github.com/hpcugent/easybuild-framework/issues/2143


ah... because there are then two roots to the hierarchy, the global one 
and the local one?


Miguel



On 27 June 2017 at 03:09, Fotis Georgatos > wrote:



Hi Miguel,

Yeap! i’d also fully applause this approach, it is very similar to
what we’ve been doing since 2012!
- $MODULEPATH can include both global and local builds, you just
need to decide their exact order
  * fyi. recent versions of Lmod have in ./contrib a pair of
use.own.eb modulefiles, implementing the above
- the global install, is nothing more than by yet another user,
which just happens to be steered by admin
- i also encourage people to add a versionsuffix with their
initials and maybe a date, to keep things apart

The trick with EASYBUILD_SOURCEPATH is quite nice, it could also
be used within use.own.eb/* modulefiles,
assuming that it is always *prepend*, as you described.

F.

On Jun 27, 2017, at 1:57 AM, Miguel Costa
mailto:migueldiasco...@gmail.com>> wrote:
> Hello Davide,
>
> I also had doubts initially because of what you mention and also
using global source paths, but this works for us:
>
> - create and manage a cluster-wide software stack with an
easybuild user, using EASYBUILD_PREFIX=$EB_GLOBAL_PREFIX
>
> - for normal users
>
>   - set EASYBUILD_PREFIX=$HOME/.local/easybuild but add
$EB_GLOBAL_PREFIX/modules/all to the $MODULEPATH (so that it finds
the already globally installed software)
>
>   - set

EASYBUILD_SOURCEPATH=$HOME/.local/easybuild/sources:$EB_GLOBAL_PREFIX/sources,
in this order (so that it downloads to local but looks in global).
This was recently clarified in the documentation, last line in

https://easybuild.readthedocs.io/en/latest/Configuration.html?highlight=sourcepath#sourcepath


>
> I think this is enough.
>
> Miguel
>
> P.S. I encourage users to always add a versionsuffix in case
they are rebuilding a package that already exists globally,
otherwise which one gets picked depends on the order of the
folders in $MODULEPATH


--
echo "sysadmin know better bash than english" | sed s/min/mins/ \
  | sed 's/better bash/bash better/' # signal detected in a CERN forum










--
Dr. Alan O'Cais
E-CAM Software Manager
Juelich Supercomputing Centre
Forschungszentrum Juelich GmbH
52425 Juelich, Germany

Phone: +49 2461 61 5213
Fax: +49 2461 61 6656
E-mail: a.oc...@fz-juelich.de 
WWW: http://www.fz-juelich.de/ias/jsc/EN




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

[easybuild] 2017b common toolchains

[Kenneth Hoste]

Dear EasyBuilders,

The time has come to look into the 2017b update of the common 
toolchains, i.e. foss/2017b and intel/2017b.


I have already created WIP pull requests for them, see [1, 2].

Currently, the toolchains are defined as specified below, but since 
updates are expected soon for both OpenBLAS (0.2.20?) & GCC (6.4.0), we 
should give it some more time before writing them in stone (especially 
for OpenBLAS since the current last release dates from Sept'16...).


All toolchain components are basically updated to the latest version, 
except for GCC since Intel support made the statement that the 2017 
update 4 versions of the Intel compilers are not supported yet on top of 
GCC 7.x.


foss/2017b:
GCC 6.3.0 (*) + binutils 2.28
OpenMPI 2.1.1
OpenBLAS 0.2.19 (*)
FFTW 3.3.6(-pl2)
ScaLAPACK 2.0.2

intel/2017b:
Intel compilers 2017.4.196 on top of GCC 6.3.0 (*) + binutils 2.28
Intel MPI 2017.3.196
Intel MKL 2017.3.196

(*) update expected in the coming weeks!


I hope we can finalize these toolchain definitions very soon (i.e. when 
GCC 6.4 and the OpenBLAS update are available),
so we have ample time to test these toolchains with existing 2017a (and 
maybe also 2016b) easyconfigs.


Any feedback, comments & suggestions are welcome!


regards,

Kenneth


[1] https://github.com/hpcugent/easybuild-easyconfigs/pull/4618 
(intel/2017b)

[2] https://github.com/hpcugent/easybuild-easyconfigs/pull/4768 (foss/2017b)

Re: [easybuild] Local user intstallation

[Alan O'Cais]

That is a neat trick with the sourcepaths that I will try out today.

I think there is a bit more to a user install space than what's been mentioned 
when you have a HMNS, see 
https://github.com/hpcugent/easybuild-framework/issues/2143

On 27 June 2017 at 03:09, Fotis Georgatos 
mailto:fo...@mail.cern.ch>> wrote:

Hi Miguel,

Yeap! i’d also fully applause this approach, it is very similar to what we’ve 
been doing since 2012!
- $MODULEPATH can include both global and local builds, you just need to decide 
their exact order
  * fyi. recent versions of Lmod have in ./contrib a pair of use.own.eb 
modulefiles, implementing the above
- the global install, is nothing more than by yet another user, which just 
happens to be steered by admin
- i also encourage people to add a versionsuffix with their initials and maybe 
a date, to keep things apart

The trick with EASYBUILD_SOURCEPATH is quite nice, it could also be used within 
use.own.eb/* modulefiles,
assuming that it is always *prepend*, as you described.

F.

On Jun 27, 2017, at 1:57 AM, Miguel Costa 
mailto:migueldiasco...@gmail.com>> wrote:
> Hello Davide,
>
> I also had doubts initially because of what you mention and also using global 
> source paths, but this works for us:
>
> - create and manage a cluster-wide software stack with an easybuild user, 
> using EASYBUILD_PREFIX=$EB_GLOBAL_PREFIX
>
> - for normal users
>
>   - set EASYBUILD_PREFIX=$HOME/.local/easybuild but add 
> $EB_GLOBAL_PREFIX/modules/all to the $MODULEPATH (so that it finds the 
> already globally installed software)
>
>   - set 
> EASYBUILD_SOURCEPATH=$HOME/.local/easybuild/sources:$EB_GLOBAL_PREFIX/sources,
>  in this order (so that it downloads to local but looks in global). This was 
> recently clarified in the documentation, last line in 
> https://easybuild.readthedocs.io/en/latest/Configuration.html?highlight=sourcepath#sourcepath
>
> I think this is enough.
>
> Miguel
>
> P.S. I encourage users to always add a versionsuffix in case they are 
> rebuilding a package that already exists globally, otherwise which one gets 
> picked depends on the order of the folders in $MODULEPATH


--
echo "sysadmin know better bash than english" | sed s/min/mins/ \
  | sed 's/better bash/bash better/' # signal detected in a CERN forum










--
Dr. Alan O'Cais
E-CAM Software Manager
Juelich Supercomputing Centre
Forschungszentrum Juelich GmbH
52425 Juelich, Germany

Phone: +49 2461 61 5213
Fax: +49 2461 61 6656
E-mail: a.oc...@fz-juelich.de
WWW:http://www.fz-juelich.de/ias/jsc/EN




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