Sébastien Blaise wrote:
vtkXMLDataParser (0xa02c998): Error reading beginning of compression
header. Read 0 of 12 bytes.
At quick glance your compression header writing code looks okay. However,
this error occurs before the parser even tries to interpret the compression
header, so something el
Sébastien Blaise wrote:
ERROR: In
/build/buildd/paraview-3.2.2/VTK/IO/vtkXMLUnstructuredDataReader.cxx,
line 515
vtkXMLUnstructuredGridReader (0xa030228): Cannot read points array from
Points in piece 0. The data array in the element may be too short.
Note that the error occurs when reading t
Jack Howarth wrote:
-DPYTHON_LIBRARIES=%p/lib/python2.6/config \
-DPYTHON_DEBUG_LIBRARIES=%p/lib/python2.6/config \
-DPYTHON_LIBRARY=%p/lib/python2.6/config/libpython2.6.a
-DPYTHON_DEBUG_LIBRARY=%p/lib/python2.6/libpython2.6.a
The persistent cache variables are singular. The plural
names are
Utkarsh Ayachit wrote:
Can you check is a file named VTK/Parallel/vtkSocketCommunicatorHash.h
was generated. Look at it's contents. Does it look something as such:
#ifndef vtkSocketCommunicatorHash
# define vtkSocketCommunicatorHash "5827858305bd3f3ec0c8b5e8836b390f"
#endif
What version of CMa
Ricardo Reis wrote:
On Tue, 30 Jun 2009, Brad King wrote:
Utkarsh Ayachit wrote:
Can you check is a file named VTK/Parallel/vtkSocketCommunicatorHash.h
was generated. Look at it's contents. Does it look something as such:
#ifndef vtkSocketCommunicatorHash
# define vtkSocketCommunicato
Ricardo Reis wrote:
$ ../../bin/vtkHashSource
../../bin/vtkHashSource: error while loading shared libraries:
libvtksys.so.pv3.7: cannot open shared object file: No such file or
directory
Ah, so the executable fails to run because it cannot find shared
libraries it needs. Did you change any R
Ricardo Reis wrote:
On Tue, 30 Jun 2009, Brad King wrote:
Ricardo Reis wrote:
$ ../../bin/vtkHashSource
../../bin/vtkHashSource: error while loading shared libraries:
libvtksys.so.pv3.7: cannot open shared object file: No such file or
directory
Ah, so the executable fails to run because
Ricardo Reis wrote:
> On Tue, 30 Jun 2009, Brad King wrote:
>
>>> I always set VTK_USE_RPATH NO
>>>
>>> because if not I'm unable to install it to other dir (I usually use
>>> /opt/paraview).
>>
>> Okay, I've committed a fix to ma
Eric E. Monson wrote:
> CMake 2.7.20090713
It's a subtle bug in CMake that I introduced in version 2.7.20090710
(three days before your version) with another change.
I've committed a work-around to ParaView because it actually cleans
up the source anyway.
Meanwhile, I'm fixing CMake for the 2.8.
Michael Wild wrote:
Just out of curiosity: Do you use the -k flag with git-cvsimport? The
man-page says that it's highly recommended, but broke things for me.
We're not using git-cvsimport. The mirror is converted incrementally
from CVS using fromcvs/togit. We are using it's "-kk" option to
Michael Wild wrote:
>
> On 1. Nov, 2009, at 17:00 , Brad King wrote:
>
>> Michael Wild wrote:
>>> Just out of curiosity: Do you use the -k flag with git-cvsimport? The
>>> man-page says that it's highly recommended, but broke things for me.
>>
>
Jean M. Favre wrote:
> Second question: I don't see what method should be used for
> parallelizing the construction of the octree.
vtkHyperOctree uses a compact representation within a few
contiguous arrays and use indexes instead of pointers.
It allocates all octree nodes in these arrays. New no
Dave Partyka wrote:
> Hi All,
>
> We are going to be locking the following CVS repositories tomorrow
> (April 16th) to commence the Git Transition. After the transition is
> complete, you will have to patch in any changes you have in your local
> CVS sandboxes into a new git clone of any of these
Brad King wrote:
> CVS commits to these repositories have been disabled. I will complete
> the final conversions of history today and over the weekend.
We're pleased to announce the completion of the repository conversion.
The CVS repositories have been permanently frozen (though I&#
Brad King wrote:
> IMPORTANT NOTE: The official histories now published at the above
> URLs are *incompatible* with all previous Git repositories for these
> projects. You *must* do a *fresh* clone from scratch. Please do not
> try to pull into an existing clone that was created
On 03/02/2011 06:31 PM, Burlen Loring wrote:
> I'm trying to link paraview static and include python. In the executable
> link line there are a couple "-Wl,-Bdynamic" appearing and I am not able
> to locate their source.
>
> Can anyone help figure out where these comes from and how to turn them
On 03/03/2011 04:08 PM, Burlen Loring wrote:
> On 03/03/2011 05:39 AM, Brad King wrote:
>> On 03/02/2011 06:31 PM, Burlen Loring wrote:
>>> Can anyone help figure out where these comes from and how to turn them off?
>> http://www.cmake.org/cmake/
On 03/05/2011 02:25 PM, burlen wrote:
> OK but why would LINK_SEARCH_END_STATIC result in "-Wl,-Bstatic
> -Wl,-Bdynamic" being used ? Shouldn't it be just "-Bstatic" ?
You can read the logic in cmComputeLinkInformation.cxx to figure this out.
> Why is CMake's default to make a substitution like
On 04/11/2011 01:57 PM, Utkarsh Ayachit wrote:
> rpaths are stripped to ensure that installed executable don't depend
> on anything that is not installed. To circumvent the LD_LIBRARY_PATH
> issues, Paraview uses what we call "shared-forwarding". The paraview
> executable that gets installed in "bi
On 5/3/2012 10:37 AM, Michael Jackson wrote:
Doesn't make sense to me but, hey if it works. Great.
The array contains the value "6.44569e-302" that is outside the
range "float" can hold so the Mac streams library gives up when
parsing. Test with this code:
#include
#include
int main()
{
20 matches
Mail list logo
