Hi Jurij,
On 06/02/2017 14:55, Jure Pečar wrote:
On Sat, 28 Jan 2017 17:43:42 +0100
Kenneth Hoste <[email protected]> wrote:
If there are releases available for each of the submodules, you can make
EB pulls those in, and then you could reassemble things in the build dir
using symlinks via 'preconfigopts' for example in the easyconfig?
That would be one way to automate this while retaining control over
which sources are actually used...
Interesting idea. Will play with it when I get some time.
You could just get that R library built via the extensions mechanism in
EasyBuild, and just make it part of the same installation?
I'm exploring this now ... and have a bit of a chicken-and-egg issue.
If you check mxnet docs at
http://mxnet.io/get_started/ubuntu_setup.html#install-the-mxnet-package-for-r
you'll see that the steps to install the R-package of mxnet are:
* build mxnet
* Rscript install_deps (which installs about 11 additional R packages beside
the ones listed in R eb)
* make rpkg (which installs mxnet R package and only then creates a tarball ...
and tarball is created by R from mxnet:::mxnet.export ... grrr)
* at that point I have a tarball that I can push to sources dir and use as a
source of R extension
I don't see how I could simply map this to existing easybuild facilities.
Maybe I can tear apart the "make rpkg" thing and try to reimplement it in .eb
file ... But still I have to get those required R packages installed first. Any
suggestions?
Maybe we can discuss this on Thursday ...
Balázs (who is now also subscribed to this list) was working on mxnet
during the hackathon, maybe he has some useful information on this...
regards,
Kenneth
