I don’t recall any special reason that libcudart and the rest of the cuda
libs (other than the driver lib libcuda.so.1) were not linked statically.
Is there any reason they are not?

On Wed, Feb 6, 2019 at 3:03 PM Timur Shenkao <t...@timshenkao.su> wrote:

> From my experience with MxNet (and TF), nothing good comes out of such
> attempts.
> It will look for several CUDA 9 specific dependencies.
> I ended having several CUDA installations (9.2, 10, etc.) on one server.
>
> On Wed, Feb 6, 2019 at 8:58 PM Seok Hyun Jin <sj...@cornell.edu> wrote:
>
> > Hi,
> >
> > I’m trying to run MxNet compiled with Cuda 9 on a machine with only Cuda
> > 10.
> > For other Cuda applications, this seems to be possible as long as I
> specify
> > the correct target GPU generation and statically link the runtime into
> the
> > application when I run ‘nvcc’ (at the cost of having a much fatter
> binary).
> >
> > But does this hold true for MxNet as well? Is there anything about MxNet
> > that makes it not runnable on a machine with a more recent Cuda version?
> >
> > I'm using containerized build for Jetson to build the libmxnet.so myself.
> >
> > I tried running MxNet with Cuda 9 on Cuda 10 machine but it keeps looking
> > for libcudart.so.9.0 .
> >
> > Thanks!
> >
> > Best,
> >
> > Jin
> >
>

Reply via email to