>
> -rpath has nothing to do with undefined references at link time. It's for
> "baking in" the library path to an executable so it can be found at runtime
> regardless of your LD_LIBRARY_PATH variable.
>
> The problem here seems to be that you are have built a version of VTK in
> which "libvtkDICOMParser" is required by libvtkIO, something I've never
> encountered before.
>
> It also appears that you are using the Intel compiler to build libmesh?
> Did you use the same compiler to build VTK?
>
Yes, the VTK is built with the same intel compilers I'm using for building
LibMesh. ldd libvtkIO.so gives me this:
linux-vdso.so.1 => (0x00007fff727ff000)
libvtkFiltering.so.5.10 (0x00002b4c2fcea000)
libvtkDICOMParser.so.5.10 (0x00002b4c3034a000)
libvtkNetCDF.so.5.10 (0x00002b4c30565000)
libvtkNetCDF_cxx.so (0x00002b4c3087d000)
libLSDyna.so.5.10 (0x00002b4c30a9c000)
libvtkmetaio.so.5.10 (0x00002b4c30cac000)
..
..
If you've written your own VTK code, it's likely that you will need to link
> against more libraries than are required by Libmesh alone...
Yes, I link with the required VTK libraries when compiling my code and it
works fine. Right now I'm running the code without VTK support in libmesh.
Thanks,
Harshad
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
