Hi John,
If you have a chance, please see if the branch in #860 (
> https://github.com/libMesh/libmesh/pull/860) fixes the VTK linking issue
> for you.
These changes worked for me. I can now compile with VTK.
Thanks,
Harshad
--
On Tue, Mar 8, 2016 at 9:19 AM, Harshad Sahasrabudhe
wrote:
> as you are definitely building shared libs. I don't know exactly what the
>> CMAKE_BUILD_TYPE does, but I agree that could be the cause...
>
>
> Sorry, that's for the static build. I posted the wrong command. Here's the
> one I'm usin
>
> -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 "libvtkDICOMP
Yes, I have VTK code in my program. I also output files in the VTK format
from libmesh.
On Fri, Mar 4, 2016 at 1:41 PM, John Peterson wrote:
>
>
> > On Mar 4, 2016, at 9:53 AM, Harshad Sahasrabudhe
> wrote:
> >
> > Hi John,
> >
> > I tried configuring with VTK 6.3.0, but I still get the same li
>
> as you are definitely building shared libs. I don't know exactly what the
> CMAKE_BUILD_TYPE does, but I agree that could be the cause...
Sorry, that's for the static build. I posted the wrong command. Here's the
one I'm using
cmake -DBUILD_EXAMPLES=OFF -DBUILD_SHARED_LIBS=ON -DBUILD_TESTIN
>
> -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 "libvtkDIC
>
> Can you post your VTK cmake commands to the list?
cmake -DBUILD_EXAMPLES=OFF -DBUILD_SHARED_LIBS=OFF -DBUILD_TESTING=OFF
-DCMAKE_INSTALL_PREFIX=$(PWD)
I guess not building it with -DCMAKE_BUILD_TYPE=Release creates all the
different libraries.
On Tue, Mar 8, 2016 at 10:47 AM, John Peterson
> On Mar 8, 2016, at 7:02 AM, Harshad Sahasrabudhe wrote:
>
> Yes, I have VTK code in my program. I also output files in the VTK format
> from libmesh.
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...
> On Mar 8, 2016, at 7:00 AM, Harshad Sahasrabudhe wrote:
>
> Hi John and Vasileios,
>
> Thanks for looking into this. I get the same error for many different
> versions of VTK (including 5.8), so the problem isn't with the VTK version. I
> might have found the root of the problem with linki
On Tue, Mar 8, 2016 at 9:12 AM, Harshad Sahasrabudhe
wrote:
> Can you post your VTK cmake commands to the list?
>
>
> cmake -DBUILD_EXAMPLES=OFF -DBUILD_SHARED_LIBS=OFF -DBUILD_TESTING=OFF
> -DCMAKE_INSTALL_PREFIX=$(PWD)
>
> I guess not building it with -DCMAKE_BUILD_TYPE=Release creates all the
On Tue, Mar 8, 2016 at 7:40 AM, Harshad Sahasrabudhe
wrote:
> -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
Hi John and Vasileios,
Thanks for looking into this. I get the same error for many different
versions of VTK (including 5.8), so the problem isn't with the VTK version.
I might have found the root of the problem with linking. In libmesh version
0.9.4, the link test with VTK looks like this:
confi
Hi Harshad,
I have had the same problem awhile ago, and frankly the only workaround I
found was to use VTK version 5.8
Hope this helps.
cheers,
Vas
On 4 March 2016 at 16:53, Harshad Sahasrabudhe wrote:
> Hi John,
>
> I tried configuring with VTK 6.3.0, but I still get the same linking
> err
> On Mar 4, 2016, at 9:53 AM, Harshad Sahasrabudhe wrote:
>
> Hi John,
>
> I tried configuring with VTK 6.3.0, but I still get the same linking errors.
> I'm not sure what the problem could be. Maybe we need to link with more VTK
> libraries to resolve the undefined references?
Have you wri
> On Mar 4, 2016, at 9:53 AM, Harshad Sahasrabudhe wrote:
>
> Hi John,
>
> I tried configuring with VTK 6.3.0, but I still get the same linking errors.
> I'm not sure what the problem could be. Maybe we need to link with more VTK
> libraries to resolve the undefined references?
How are you
Hi John,
I tried configuring with VTK 6.3.0, but I still get the same linking
errors. I'm not sure what the problem could be. Maybe we need to link with
more VTK libraries to resolve the undefined references?
I have attached the config.log.
Thanks,
Harshad
On Thu, Mar 3, 2016 at 5:02 PM, John
On Thu, Mar 3, 2016 at 9:46 AM, Harshad Sahasrabudhe
wrote:
> Hi John,
>
> I re-configured and re-checked that the two flags libmesh_LIBS and LIBS
> were not set in the environment. I have attached the config.log.
>
OK, so I think the extra flags are just coming from our call to
AC_HAVE_LIBRARY:
Hi John,
I re-configured and re-checked that the two flags libmesh_LIBS and LIBS
were not set in the environment. I have attached the config.log.
Thanks,
Harshad
On Thu, Mar 3, 2016 at 11:04 AM, John Peterson wrote:
>
>
> On Thu, Mar 3, 2016 at 7:05 AM, Harshad Sahasrabudhe
> wrote:
>
>> Hi,
On Thu, Mar 3, 2016 at 7:05 AM, Harshad Sahasrabudhe
wrote:
> Hi,
>
> I wasn't able to configure LibMesh 0.9.5 with VTK 5.10. The configuration
> options I used worked for 0.9.4. Here's the relevant config.log:
>
> The test compilation line looks like this:
>
> configure:35934: mpiicpc -o confte
Sorry I forgot to link the config.log: http://pastebin.com/sBgt714N
On Thu, Mar 3, 2016 at 9:05 AM, Harshad Sahasrabudhe
wrote:
> Hi,
>
> I wasn't able to configure LibMesh 0.9.5 with VTK 5.10. The configuration
> options I used worked for 0.9.4. Here's the relevant config.log:
>
> The test comp
20 matches
Mail list logo
