Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] hwloc detection problem when configuring starpu-svn-trunk and starpu-1.2.0rc5

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] hwloc detection problem when configuring starpu-svn-trunk and starpu-1.2.0rc5


Chronologique Discussions 
  • From: Florent Pruvost <florent.pruvost@inria.fr>
  • To: Samuel Thibault <samuel.thibault@inria.fr>, starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] hwloc detection problem when configuring starpu-svn-trunk and starpu-1.2.0rc5
  • Date: Thu, 18 Aug 2016 15:41:47 +0200
  • List-archive: <http://lists.gforge.inria.fr/pipermail/starpu-devel/>
  • List-id: "Developers list. For discussion of new features, code changes, etc." <starpu-devel.lists.gforge.inria.fr>

Le 18/08/2016 15:33, Samuel Thibault a écrit :
Florent Pruvost, on Thu 18 Aug 2016 15:28:05 +0200, wrote:
Le 18/08/2016 14:17, Nathalie Furmento a écrit :
It's likely you need to add in your LD_LIBRARY_PATH the
path to the OpenCL library.
In spack, the LD_LIBRARY_PATH is unset to avoid being polluted by the
external environment.
Mmm... That might have to be reconsidered: how can starpu etc. work if
cuda etc. are not installed in the standard location?

It is ok because either spack don't know a low level dependency installed in the standard system paths either the dependency is known from spack and it manages the paths accordingly.
For cuda for instance we tell spack "cuda is here" and it handles it.

Here what is surprising is that hwloc detects opencl in a path the linker is not aware...?




Archives gérées par MHonArc 2.6.19+.

Haut de le page