On 18 May 2010 10:55, Stefan Behnel <[email protected]> wrote: > Lisandro Dalcin, 18.05.2010 15:38: >> On 18 May 2010 01:59, Stefan Behnel wrote: >>> Lisandro Dalcin, 17.05.2010 18:55: >>>> On 17 May 2010 13:19, Robert Bradshaw wrote: >>>>> On May 16, 2010, at 3:47 PM, Lisandro Dalcin wrote: >>>>>> petsc4py would also qualify, but the dependency on numpy and core >>>>>> PETSc could make it more cumbersome. >>>>> >>>>> Could either of these be installed in, and run from, your home >>>>> directory? That would make things much easier (no root/admin >>>>> privileges required). >>>> >>>> Of course, they can be installed at any place. However, the idea is to >>>> also test against multiple Python versions, right? Then numpy should >>>> also be available across Python versions ... >>> >>> Currently, we just pass tgz archives of the installed build results between >>> build jobs. Adding a NumPy install step to that shouldn't be hard. It's >>> used in a lot of Cython code, so it certainly qualifies as a standard >>> dependency. >>> >>> If you can give me a Linux bash script that runs a cmmi build for your >>> external libraries to install them into a suitable subdirectory, and get >>> your code to pick it up from another subdirectory (in a different build >>> job) afterwards (maybe using LD_LIBRARY_PATH and friends), I'll set up a >>> Hudson build job that runs it for you. >>> >> >> Isn't any MPI implementation, like MPICH2 or Open MPI, available as a >> package from the distro Hudson runs? > > Quite likely - maybe someone can install it. Which one would be better for > you? Or would it help (and be possible) to install both in parallel? >
Well, having MPICH2 and Open MPI in parallel would be nice, however the distro has to provide good support for this (e.g. environmental modules support, "module load something"). If parallel installs are not possible, then I would prefer MPICH2, but Open MPI would work, too. > >> I would prefer such option, as >> building any of these MPI from sources takes time, it will load the >> machine paying very little to us. > > Hudson only has to do it once, so that the packaged binary becomes > available. Artifacts created in one build job can be reused in another, and > Hudson keeps a trace back to the original build job that the artifact > originated from. > Sorry, could you point me to some docs about this infrastructure? Or examples of some build that depends on external libraries? I'm a bit lost about this. -- Lisandro Dalcin --------------- CIMEC (INTEC/CONICET-UNL) Predio CONICET-Santa Fe Colectora RN 168 Km 472, Paraje El Pozo Tel: +54-342-4511594 (ext 1011) Tel/Fax: +54-342-4511169 _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
