[vtkusers] Issuings running make in my VTK-build directory

[Andrew Lam]

SUCCESS!!! The VTK fix worked! Thank you all very much for taking time out
of your days to help me I really appreciate it.

Thanks,
Andrew

On Thu, Apr 13, 2017 at 1:14 PM, Andrew Lam <werdna.mal222 at gmail.com> wrote:

> David,
>
> Thanks I will pull and try building with the fix. My last attempt did not
> work. I'll let you know my results.
>
> Thanks,
> Andrew
>
> On Thu, Apr 13, 2017 at 1:00 PM, David Gobbi <david.gobbi at gmail.com>
> wrote:
>
>> I've merged a fix for '//' into the VTK master branch, so the fix will be
>> in VTK 8.0.  There was a small but crucial mistake in the code for
>> vtkWrapPython.
>>
>>  - David
>>
>>
>> On Thu, Apr 13, 2017 at 9:44 AM, Andrew Lam <werdna.mal222 at gmail.com>
>> wrote:
>>
>>> Cory,
>>>
>>> Haha I'll show my professor your email and see if he'll buy it. I'm
>>> currently building VTK with all the // paths switched to /. I'll report
>>> back when it finishes.
>>>
>>> Thanks,
>>> Andrew
>>>
>>> On Thu, Apr 13, 2017 at 8:34 AM, Cory Quammen <cory.quammen at kitware.com>
>>> wrote:
>>>
>>>> Andrew, you should get extra credit in your course for uncovering a VTK
>>>> bug!
>>>>
>>>> On Thu, Apr 13, 2017 at 11:28 AM, David Gobbi <david.gobbi at gmail.com>
>>>> wrote:
>>>> > Thanks, Pierre.  I tried this on my own system, and there is indeed a
>>>> bug
>>>> > that causes the command to fail if the input or output filename
>>>> begins with
>>>> > "//".  I have a few guesses as to where this bug occurs, I'll see if
>>>> I can
>>>> > track it down.
>>>> >
>>>> >  - David
>>>> >
>>>> >
>>>> > On Thu, Apr 13, 2017 at 7:08 AM, Pierre Turlais <
>>>> pturlais at seismith.com>
>>>> > wrote:
>>>> >>
>>>> >> Hi,
>>>> >>
>>>> >> I have been able to reproduce the problem ( vtkWrapPython error ) on
>>>> a
>>>> >> CentOS 7 machine with the following :
>>>> >>
>>>> >>  cmake3 //d4-2/VTK/VTK-7.1.1 # Note the double // which kind of
>>>> match you
>>>> >> //home/alam38 .....
>>>> >>
>>>> >> May you should try reconfigure with /home/alam38 ( or understand
>>>> how/why
>>>> >> you get //home/alam38 ).
>>>> >>
>>>> >>  Running the vtkWrapPython command alone with or without the //
>>>> shows the
>>>> >> problem.
>>>> >>
>>>> >> [turlais at wk6 Python]$ pwd
>>>> >> /d4-2/VTK/BLD/Wrapping/Python
>>>> >>
>>>> >> [turlais at wk6 Python]$ ../../bin/vtkWrapPython-7.1
>>>> >> @/d4-2/VTK/BLD/Wrapping/Python/vtkCommonCorePython.Debug.args -o
>>>> >> /d4-2/VTK/BLD/Wrapping/Python/vtkAbstractArrayPython.cxx
>>>> >> /d4-2/VTK/VTK-7.1.1/Common/Core/vtkAbstractArray.h
>>>> >>
>>>> >> [turlais at wk6 Python]$ ../../bin/vtkWrapPython-7.1
>>>> >> @/d4-2/VTK/BLD/Wrapping/Python/vtkCommonCorePython.Debug.args -o
>>>> >> //d4-2/VTK/BLD/Wrapping/Python/vtkAbstractArrayPython.cxx
>>>> >> /d4-2/VTK/VTK-7.1.1/Common/Core/vtkAbstractArray.h
>>>> >> Usage: vtkWrapPython-7.1 [options] infile...
>>>> >>   --help            print this help message
>>>> >>   --version         print the VTK version
>>>> >>   -o <file>         the output file
>>>> >>   -I <dir>          add an include directory
>>>> >>   -D <macro[=def]>  define a preprocessor macro
>>>> >>   -U <macro>        undefine a preprocessor macro
>>>> >>   @<file>           read arguments from a file
>>>> >>   --hints <file>    the hints file to use
>>>> >>   --types <file>    the type hierarchy file to use
>>>> >>   --concrete        force concrete class (ignored, deprecated)
>>>> >>   --abstract        force abstract class (ignored, deprecated)
>>>> >>   --vtkobject       vtkObjectBase-derived class (ignored, deprecated)
>>>> >>   --special         non-vtkObjectBase class (ignored, deprecated)
>>>> >>
>>>> >> Regards,
>>>> >> Pierre TURLAIS
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20170413/39d88344/attachment.html>