On Thu, Jun 5, 2014 at 3:33 PM, Miguel Angel Salazar de Troya <
salazardetr...@gmail.com> wrote:
> Thanks for your response. I am trying to modify the
> ProjectVector::operator() function to be able to handle the LAGRANGE_VEC.
> One of the first things this function does is this (line 782 at
> sys
Thanks for your response. I am trying to modify the
ProjectVector::operator() function to be able to handle the LAGRANGE_VEC.
One of the first things this function does is this (line 782 at
system_projection.C )
AutoPtr fe (FEBase::build(dim, base_fe_type))
This function does not handle the fe_ty
On Thu, 5 Jun 2014, John Peterson wrote:
Seriously?!
/usr/lib/vtk/*.so starts to sound like a viable option...
With surprisingly little exaggeration, and I disagree:
$ ls /usr/lib/x86_64-linux-gnu/libvtk*.so | wc
471 471 26374
Since this turned out not to be urgent for anyone
On Thu, Jun 5, 2014 at 12:37 PM, Roy Stogner
wrote:
>
> On Wed, 4 Jun 2014, Josué Barroso wrote:
>
> I think that I can work with vtk 5.8It worked at the configuration step
>>
>
> Glad to hear it!
>
> Upon first inspection, the problem with VTK 6 seems to be that they
> now have a separate .so f
On Wed, 4 Jun 2014, Josué Barroso wrote:
I think that I can work with vtk 5.8It worked at the configuration step
Glad to hear it!
Upon first inspection, the problem with VTK 6 seems to be that they
now have a separate .so file for nearly every individual API function,
with the exceptions of
Hi,
I contacted the netCDF support. They basically couldn't tell me what
exactly was going wrong, but at the end they said
> I'm going to recommend that you start over with the current
> release of netCDF-C, version 4.3.2, and build and install that. Then
> I recommend that you build and instal
