Hi Bart, On Oct 1, 2013, at 10:31 PM, Bart Verleye wrote: > I have installed a new toolchain, gmpolf-3.0.4. > Now I want to install Paraview, which depends on quite a few other packages.
To save a few keystrokes, you can find pre-calculated templates for many of the common building blocks over here (shameless rip from pkgsrc's Makefiles): https://github.com/fgeorgatos/easybuild.experimental/tree/master/contrib/pkgsrc/20130506 (sorry to the rest for being repetitive, but you know how convenient this can be...) > During the installation, I came up with following comments: > > - --try-toolchain is not recursive. Is that 'not yet', or is there a reason > behind that? "Not yet", there is an open issue somewhere about it, AFAIK. > - --try-toolchain produces a eb file, but does not copy it to the lib > directory at the end. Perhaps that could be added? It's a bugture (contraption of bug-feature): manual work is expected. In principle that requires heavy editing and is considered more of a template. > - in one of my attemps, at the end of an installation, this error came up: > (should only have 'files' and 'dirs' keys, values should be lists (at least > one non-empty)). > This could be checked before compilation as part of the eb-file sanity check. IMHO, the error-level should then be non-zero; I believe then the right thing will happen, no? > During the installation of Qt, some "Project Messages" pop up, and the > waiting time during the configuration is sometimes large. As a result, eb > stops and prints: [...] > However, this message is not an error, and if I configure myself, without eb, > the whole process runs through. How can I avoid eb from stopping on these > messages? Either the output has a keyword that makes EasyBuild tick (and requires tuning), or the error-level is incorrect or, there is a bug (eh, or all of the above :). Which case are we talking about here? cheers, Fotis -- echo "sysadmin know better bash than english" | sed s/min/mins/ \ | sed 's/better bash/bash better/' # Yelling in a CERN forum
