subject:"\[Paraview\] CMake error from VTKConfig.cmake"

Re: [Paraview] CMake error from VTKConfig.cmake

2018-05-30 Thread Christoph Grüninger

Dear Utkarsh,
thanks for the hint, adding `-DVTK_USE_SYSTEM_LZMA:BOOL=ON`, it helped.

Now I get another linker error:

[  259s]
/home/abuild/rpmbuild/BUILD/ParaView-v5.5.0/VTK/ThirdParty/libharu/vtklibharu/src/hpdf_page_operator.c:2280:
undefined reference to `sincos'

I found some hints that ParaViews provides a patched version of hpdf,
but I could get it compiled. Any idea?

Thanks a lot!
Christoph

Am 29.05.2018 um 15:08 schrieb Utkarsh Ayachit:
> Christoph,
> 
> While I didn't encounter the lzma link issue myself, since you're using
> system zlib etc., shouldn't the LZMA also be set to use system? Try setting
> `-DVTK_USE_SYSTEM_LZMA:BOOL=ON`. Maybe same should be done for
> `VTK_USE_SYSTEM_LZ4`.
> 
> Utkarsh
> On Tue, Apr 24, 2018 at 11:11 AM Utkarsh Ayachit <
> utkarsh.ayac...@kitware.com> wrote:
> 
>> Oh right! I forgot about that. Let me try to see if I can reproduce
>> that one too.
> 
>> Utkarsh
> 
>> On Tue, Apr 24, 2018 at 12:41 AM, Christoph Grüninger
>>  wrote:
>>> Hi Utkarsh,
>>> thanks for the patches! They seem to work, the CMake configuration
>>> problems are gone, including the ugly CMake warnings.
>>>
>>> Now I run again into the linker bug I mentioned last week.
>>>
>>> Bye
>>> Christoph
>>>
>>> --
>>> Unfortunately, plots are notoriously hard to get right. Partly, the
>>> default settings of programs like gnuplot or Excel are to blame for
>>> this since these programs make it very convenient to create bad plots.
>>> -- Till Tantau, "The TikZ and PGF Packages"
> 

-- 
Unfortunately, plots are notoriously hard to get right. Partly, the
default settings of programs like gnuplot or Excel are to blame for
this since these programs make it very convenient to create bad plots.
-- Till Tantau, "The TikZ and PGF Packages"
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] CMake error from VTKConfig.cmake

2018-05-29 Thread Utkarsh Ayachit

Christoph,

While I didn't encounter the lzma link issue myself, since you're using
system zlib etc., shouldn't the LZMA also be set to use system? Try setting
`-DVTK_USE_SYSTEM_LZMA:BOOL=ON`. Maybe same should be done for
`VTK_USE_SYSTEM_LZ4`.

Utkarsh
On Tue, Apr 24, 2018 at 11:11 AM Utkarsh Ayachit <
utkarsh.ayac...@kitware.com> wrote:

> Oh right! I forgot about that. Let me try to see if I can reproduce
> that one too.

> Utkarsh

> On Tue, Apr 24, 2018 at 12:41 AM, Christoph Grüninger
>  wrote:
> > Hi Utkarsh,
> > thanks for the patches! They seem to work, the CMake configuration
> > problems are gone, including the ugly CMake warnings.
> >
> > Now I run again into the linker bug I mentioned last week.
> >
> > Bye
> > Christoph
> >
> > --
> > Unfortunately, plots are notoriously hard to get right. Partly, the
> > default settings of programs like gnuplot or Excel are to blame for
> > this since these programs make it very convenient to create bad plots.
> > -- Till Tantau, "The TikZ and PGF Packages"
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] CMake error from VTKConfig.cmake

2018-04-23 Thread Christoph Grüninger

Hi Utkarsh,
thanks for the patches! They seem to work, the CMake configuration
problems are gone, including the ugly CMake warnings.

Now I run again into the linker bug I mentioned last week.

Bye
Christoph

-- 
Unfortunately, plots are notoriously hard to get right. Partly, the
default settings of programs like gnuplot or Excel are to blame for
this since these programs make it very convenient to create bad plots.
-- Till Tantau, "The TikZ and PGF Packages"
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] CMake error from VTKConfig.cmake

2018-04-22 Thread Utkarsh Ayachit

(cc-ing the correct, Mark this time :)).

Thanks, Mark/Christoph. I think I know what's causing the VTKm version issue.

Can you try the attached patches? The VTKm one has to be applied under
ParaView/VTK/ThirdParty/vtkm/vtk-m/.

Utkarsh



> On Sat, Apr 21, 2018 at 7:28 PM, Christoph Grüninger  
> wrote:
>> Hi Utkarsh,
>> please find attached the full log, including the error message.
>>
>> Building the examples is now disabled.
>>
>> Bye
>> Christoph
>>
>>
>> Am 16.04.2018 um 18:14 schrieb Utkarsh Ayachit:
>>> Christoph,
>>>
>>> I am totally unfamiliar with OpenSUSE and my initial attempts to even
>>> install a C++ compiler are going no where :). Mind making it easier
>>> for me and just post the full error message that you're getting? Maybe
>>> attaching the 
>>> /home/abuild/rpmbuild/BUILD/ParaView-v5.5.0/build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake
>>> file will throw some light. Also is this failing when building the
>>> Examples or just ther full ParaView build? I'd suggest disabling
>>> examples, if that's the issue. The ParaView RPM should probably not
>>> include examples any ways.
>>>
>>> Utkarsh
From cf7268335b63632048bc2e9866715901b653fc9a Mon Sep 17 00:00:00 2001
From: Utkarsh Ayachit 
Date: Sun, 22 Apr 2018 20:26:35 -0400
Subject: [PATCH] fixes issues with ParaViewDetermineVersion.

The code had 2 issues:
1. used obsolete 'output' if Git executable was missing. There was a
   possibility that output variable was never set and used some garbage
   value from parent scope.

2. version pattern matching was too liberal and would match absolute
   any long txt so long as it has some numbers in it that matched a
   typical version number.
---
 CMake/ParaViewDetermineVersion.cmake | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/CMake/ParaViewDetermineVersion.cmake b/CMake/ParaViewDetermineVersion.cmake
index 41e67a0..75eb3ad 100644
--- a/CMake/ParaViewDetermineVersion.cmake
+++ b/CMake/ParaViewDetermineVersion.cmake
@@ -45,6 +45,8 @@ function(determine_version source_dir git_command var_prefix)
 ERROR_QUIET
 OUTPUT_STRIP_TRAILING_WHITESPACE
 ERROR_STRIP_TRAILING_WHITESPACE)
+else()
+  set(output)
 endif()
   else()
 set(result 0)
@@ -65,7 +67,7 @@ endfunction()
 
 # Extracts components from a version string. See determine_version() for usage.
 function(extract_version_components version_string var_prefix)
-  string(REGEX MATCH "([0-9]+)\\.([0-9]+)\\.([0-9]+)[-]*(.*)"
+  string(REGEX MATCH "^([0-9]+)\\.([0-9]+)\\.([0-9]+)[-]*(.*)$"
 version_matches "${version_string}")
   if(CMAKE_MATCH_0)
 set(full ${CMAKE_MATCH_0})
-- 
2.7.4

From f41519f9691d254e5734fb7651bbad5dc6a1fda3 Mon Sep 17 00:00:00 2001
From: Utkarsh Ayachit 
Date: Sun, 22 Apr 2018 20:29:18 -0400
Subject: [PATCH] Fix issues with VTKmDetermineVersion.

The code had 2 issues:
1. used obsolete 'output' if Git executable was missing. There was a
   possibility that output variable was never set and used some garbage
   value from parent scope.

2. version pattern matching was too liberal and would match
   absolute any long txt so long as it has some numbers in it that matched
   a typical version number.
---
 CMake/VTKmDetermineVersion.cmake | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/CMake/VTKmDetermineVersion.cmake b/CMake/VTKmDetermineVersion.cmake
index 7b990be..92ffd94 100644
--- a/CMake/VTKmDetermineVersion.cmake
+++ b/CMake/VTKmDetermineVersion.cmake
@@ -51,6 +51,8 @@ function(determine_version source_dir git_command var_prefix)
 ERROR_QUIET
 OUTPUT_STRIP_TRAILING_WHITESPACE
 ERROR_STRIP_TRAILING_WHITESPACE)
+else()
+  set(output)
 endif()
   else()
 set(result 0)
@@ -75,7 +77,7 @@ endfunction()
 
 # Extracts components from a version string. See determine_version() for usage.
 function(extract_version_components version_string var_prefix)
-  string(REGEX MATCH "([0-9]+)\\.([0-9]+)\\.([0-9]+)[-]*(.*)"
+  string(REGEX MATCH "^([0-9]+)\\.([0-9]+)\\.([0-9]+)[-]*(.*)$"
 version_matches "${version_string}")
   if(CMAKE_MATCH_0)
 set(full ${CMAKE_MATCH_0})
-- 
2.7.4

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] CMake error from VTKConfig.cmake

2018-04-22 Thread Utkarsh Ayachit

A workaround to overcome this bug is to add
`-DVTKm_GIT_DESCRIBE=1.1.0` to cmake options.

Utkarsh

On Sun, Apr 22, 2018 at 8:31 PM, Utkarsh Ayachit
 wrote:
> Thanks, Mark/Christoph. I think I know what's causing the VTKm version issue.
>
> Can you try the attached patches? The VTKm one has to be applied under
> ParaView/VTK/ThirdParty/vtkm/vtk-m/.
>
> Utkarsh
>
> On Sat, Apr 21, 2018 at 7:28 PM, Christoph Grüninger  
> wrote:
>> Hi Utkarsh,
>> please find attached the full log, including the error message.
>>
>> Building the examples is now disabled.
>>
>> Bye
>> Christoph
>>
>>
>> Am 16.04.2018 um 18:14 schrieb Utkarsh Ayachit:
>>> Christoph,
>>>
>>> I am totally unfamiliar with OpenSUSE and my initial attempts to even
>>> install a C++ compiler are going no where :). Mind making it easier
>>> for me and just post the full error message that you're getting? Maybe
>>> attaching the 
>>> /home/abuild/rpmbuild/BUILD/ParaView-v5.5.0/build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake
>>> file will throw some light. Also is this failing when building the
>>> Examples or just ther full ParaView build? I'd suggest disabling
>>> examples, if that's the issue. The ParaView RPM should probably not
>>> include examples any ways.
>>>
>>> Utkarsh
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] CMake error from VTKConfig.cmake

2018-04-17 Thread Robert Maynard

This is all very weird to me. The contents of VTKm_VERSION_FULL is
done by `VTKmDetermineVersion.cmake` which is running an external
command. This smells like the variable we are using (output) already
exists with the contents of the configuration run and now is being
added to.

Mark, are you able to verify that renaming the 'output' variable in
`VTKmDetermineVersion.cmake` corrects the problem?

On Mon, Apr 16, 2018 at 3:43 PM, Utkarsh Ayachit
 wrote:
> Wow! cc-ing Rob. Rob, see below for what's ending up in VTMConfig for
> ParaView 5.5. Any suggestions?
>
> Mark, Christoph, for now, I'd recommend turning off PARAVIEW_USE_VTKM
> cmake option in your build. It should not impact the default ParaView
> capabilities by a whole lot.
>
> Utkarsh
>
> On Mon, Apr 16, 2018 at 3:34 PM, Mark Olesen  
> wrote:
>> May be related:
>> https://gitlab.kitware.com/paraview/paraview/issues/18116
>>
>>
>> I can build 5.5.0 on opensuse leap 42.3, but do get *really* weird junk in
>> the VTKmConfig.cmake file:
>>
>> # The VTKm version number
>> set(VTKm_VERSION_MAJOR "4")
>> set(VTKm_VERSION_MINOR "8")
>> set(VTKm_VERSION_PATCH "5")
>> set(VTKm_VERSION_FULL "4.8.5
>> -- Check for working Fortran compiler: /usr/bin/gfortran
>> -- Check for working Fortran compiler: /usr/bin/gfortran  -- works
>> -- Detecting Fortran compiler ABI info
>> -- Detecting Fortran compiler ABI info - done
>> -- Checking whether /usr/bin/gfortran supports Fortran 90
>> -- Checking whether /usr/bin/gfortran supports Fortran 90 -- yes
>> -- Configuring done
>> -- Generating done
>> -- Build files have been written to:
>> /home/mol/test/build/ParaView-5.5.0/CMakeFiles/CheckFortran
>> ")
>> set(VTKm_VERSION "4.8")
>>
>>
>> The version "4.8.5" look suspiciously like my gcc version.
>> The rest of the information "Check for working Fortran" etc, really looks
>> like misdirected output somewhere in the cmake files.
>>
>> /mark
>>
>>
>>
>> On 04/16/18 18:14, Utkarsh Ayachit wrote:
>>>
>>> Christoph,
>>>
>>> I am totally unfamiliar with OpenSUSE and my initial attempts to even
>>> install a C++ compiler are going no where :). Mind making it easier
>>> for me and just post the full error message that you're getting? Maybe
>>> attaching the
>>> /home/abuild/rpmbuild/BUILD/ParaView-v5.5.0/build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake
>>> file will throw some light. Also is this failing when building the
>>> Examples or just ther full ParaView build? I'd suggest disabling
>>> examples, if that's the issue. The ParaView RPM should probably not
>>> include examples any ways.
>>>
>>> Utkarsh
>>>
>>> On Sun, Apr 15, 2018 at 4:00 PM, Christoph Grüninger 
>>> wrote:

 Hi Utkarsh,
 I used openSuse build service (OBS) which currently builds it on Leap
 42.2 and Tumblewheed. If you want to give it a shot, try the package
 which I branched:
 home:mathletic:branches:science/paraview

 Bye
 Christoph


 Am 15.04.2018 um 16:40 schrieb Utkarsh Ayachit:
>
> Christoph,
>
> What openSuse version are you building on? I'll see if I can reproduce
> using the same version Docker image, if available. Will make it easier
> to track down.
>
> Utkarsh
>
> On Sun, Apr 15, 2018 at 7:08 AM, Christoph Grüninger
>  wrote:
>>
>> Dear ParaView community,
>> I tried to update openSuse's ParaView RPM. Unfortunately I get the
>> following CMake error.
>>
>>> CMake Error at
>>> build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake:289:
>>>Parse error.  Function missing ending ")".  Instead found
>>> unterminated
>>>string with text ")
>>>
>>>  endif()
>>>
>>>endforeach()
>>>
>>>
>>>
>>>check_required_components(VTKm)
>>>
>>>".
>>> Call Stack (most recent call first):
>>>build/VTK/VTKConfig.cmake:92 (find_package)
>>>CMake/ParaViewModuleTop.cmake:89 (include)
>>>CMakeLists.txt:676 (include)
>>>
>>>
>>> CMake Error at build/VTK/VTKConfig.cmake:92 (find_package):
>>>find_package Error reading CMake code from
>>>
>>> "/home/abuild/rpmbuild/BUILD/ParaView-v5.5.0/build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake".
>>> Call Stack (most recent call first):
>>>CMake/ParaViewModuleTop.cmake:89 (include)
>>>CMakeLists.txt:676 (include)
>>
>>
>> Can someone please have a look whether it is a bug or a wrong
>> configuration from openSuse? The CMake call is
>>
>> %cmake  -DPV_INSTALL_LIB_DIR:PATH=%{_lib}/%{name} \
>>  -DVTK_INSTALL_INCLUDE_DIR:PATH=include/%{name} \
>>  -DVTK_INSTALL_ARCHIVE_DIR:PATH=%{_lib}/%{name} \
>>  -DVTK_INSTALL_LIBRARY_DIR:PATH=%{_lib}/%{name} \
>>

Re: [Paraview] CMake error from VTKConfig.cmake

2018-04-16 Thread Christoph Grüninger

Hi Utkarsh,
thanks for the hint. But I got a linker error instead. I attached the
error below. pthread is found by CMake.

Regarding the log and/or VTKmConfig.cmake, it'll take me a couple of
days to provide these. I use the online frontend and have no access to
arbitrary files. I have to use obs to create a local copy and compile it
here.

Bye
Chirstoph


Error:

> [  487s] /usr/bin/gcc -fPIC -fmessage-length=0 -grecord-gcc-switches -O2 
> -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables 
> -fasynchronous-unwind-tables -fstack-clash-protection -DNDEBUG   -w -w -O2 -g 
> -DNDEBUG  -Wl,-lc -Wl,--as-needed -Wl,--no-undefined -Wl,-z,now   -shared 
> -Wl,-soname,libvtklzma-pv5.5.so.1 -o ../../../../lib/libvtklzma-pv5.5.so.1 
> CMakeFiles/vtklzma.dir/src/common/tuklib_cpucores.c.o 
> CMakeFiles/vtklzma.dir/src/common/tuklib_physmem.c.o 
> CMakeFiles/vtklzma.dir/src/liblzma/check/check.c.o 
> CMakeFiles/vtklzma.dir/src/liblzma/check/crc32_fast.c.o 
> CMakeFiles/vtklzma.dir/src/liblzma/check/crc32_table.c.o 
> CMakeFiles/vtklzma.dir/src/liblzma/check/crc64_fast.c.o 
> CMakeFiles/vtklzma.dir/src/liblzma/check/crc64_table.c.o 
> CMakeFiles/vtklzma.dir/src/liblzma/check/sha256.c.o 
> CMakeFiles/vtklzma.dir/src/liblzma/common/alone_decoder.c.o 
> CMakeFiles/vtklzma.dir/src/liblzma/common/alone_encoder.c.o 
> CMakeFiles/vtklzma.dir/src/liblzma/common/auto_decoder.c.o CMakeFiles/vtk
 lzma.dir/src/liblzma/common/block_buffer_decoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/block_buffer_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/block_decoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/block_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/block_header_decoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/block_header_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/block_util.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/common.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/easy_buffer_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/easy_decoder_memusage.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/easy_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/easy_encoder_memusage.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/easy_preset.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/filter_buffer_decoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/filter_buffer_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/filter_common.c.
 o CMakeFiles/vtklzma.dir/src/liblzma/common/filter_decoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/filter_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/filter_flags_decoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/filter_flags_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/hardware_cputhreads.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/hardware_physmem.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/index.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/index_decoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/index_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/index_hash.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/outqueue.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/stream_buffer_decoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/stream_buffer_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/stream_decoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/stream_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/stream_encoder_mt.c.o CMak
 eFiles/vtklzma.dir/src/liblzma/common/stream_flags_common.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/stream_flags_decoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/stream_flags_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/vli_decoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/vli_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/common/vli_size.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/delta/delta_common.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/delta/delta_decoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/delta/delta_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/lzma/fastpos_table.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/lzma/lzma2_decoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/lzma/lzma2_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/lzma/lzma_decoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/lzma/lzma_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/lzma/lzma_encoder_optimum_fast.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/lzma/lzma_encoder_optimum_normal.c.o 
CMakeFiles/vtklzma.dir/s
 rc/liblzma/lzma/lzma_encoder_presets.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/lz/lz_decoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/lz/lz_encoder.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/lz/lz_encoder_mf.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/rangecoder/price_table.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/simple/arm.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/simple/armthumb.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/simple/ia64.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/simple/powerpc.c.o 
CMakeFiles/vtklzma.dir/src/liblzma/simple/simple_coder.c.o

Re: [Paraview] CMake error from VTKConfig.cmake

2018-04-16 Thread Utkarsh Ayachit

Wow! cc-ing Rob. Rob, see below for what's ending up in VTMConfig for
ParaView 5.5. Any suggestions?

Mark, Christoph, for now, I'd recommend turning off PARAVIEW_USE_VTKM
cmake option in your build. It should not impact the default ParaView
capabilities by a whole lot.

Utkarsh

On Mon, Apr 16, 2018 at 3:34 PM, Mark Olesen  wrote:
> May be related:
> https://gitlab.kitware.com/paraview/paraview/issues/18116
>
>
> I can build 5.5.0 on opensuse leap 42.3, but do get *really* weird junk in
> the VTKmConfig.cmake file:
>
> # The VTKm version number
> set(VTKm_VERSION_MAJOR "4")
> set(VTKm_VERSION_MINOR "8")
> set(VTKm_VERSION_PATCH "5")
> set(VTKm_VERSION_FULL "4.8.5
> -- Check for working Fortran compiler: /usr/bin/gfortran
> -- Check for working Fortran compiler: /usr/bin/gfortran  -- works
> -- Detecting Fortran compiler ABI info
> -- Detecting Fortran compiler ABI info - done
> -- Checking whether /usr/bin/gfortran supports Fortran 90
> -- Checking whether /usr/bin/gfortran supports Fortran 90 -- yes
> -- Configuring done
> -- Generating done
> -- Build files have been written to:
> /home/mol/test/build/ParaView-5.5.0/CMakeFiles/CheckFortran
> ")
> set(VTKm_VERSION "4.8")
>
>
> The version "4.8.5" look suspiciously like my gcc version.
> The rest of the information "Check for working Fortran" etc, really looks
> like misdirected output somewhere in the cmake files.
>
> /mark
>
>
>
> On 04/16/18 18:14, Utkarsh Ayachit wrote:
>>
>> Christoph,
>>
>> I am totally unfamiliar with OpenSUSE and my initial attempts to even
>> install a C++ compiler are going no where :). Mind making it easier
>> for me and just post the full error message that you're getting? Maybe
>> attaching the
>> /home/abuild/rpmbuild/BUILD/ParaView-v5.5.0/build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake
>> file will throw some light. Also is this failing when building the
>> Examples or just ther full ParaView build? I'd suggest disabling
>> examples, if that's the issue. The ParaView RPM should probably not
>> include examples any ways.
>>
>> Utkarsh
>>
>> On Sun, Apr 15, 2018 at 4:00 PM, Christoph Grüninger 
>> wrote:
>>>
>>> Hi Utkarsh,
>>> I used openSuse build service (OBS) which currently builds it on Leap
>>> 42.2 and Tumblewheed. If you want to give it a shot, try the package
>>> which I branched:
>>> home:mathletic:branches:science/paraview
>>>
>>> Bye
>>> Christoph
>>>
>>>
>>> Am 15.04.2018 um 16:40 schrieb Utkarsh Ayachit:

 Christoph,

 What openSuse version are you building on? I'll see if I can reproduce
 using the same version Docker image, if available. Will make it easier
 to track down.

 Utkarsh

 On Sun, Apr 15, 2018 at 7:08 AM, Christoph Grüninger
  wrote:
>
> Dear ParaView community,
> I tried to update openSuse's ParaView RPM. Unfortunately I get the
> following CMake error.
>
>> CMake Error at
>> build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake:289:
>>Parse error.  Function missing ending ")".  Instead found
>> unterminated
>>string with text ")
>>
>>  endif()
>>
>>endforeach()
>>
>>
>>
>>check_required_components(VTKm)
>>
>>".
>> Call Stack (most recent call first):
>>build/VTK/VTKConfig.cmake:92 (find_package)
>>CMake/ParaViewModuleTop.cmake:89 (include)
>>CMakeLists.txt:676 (include)
>>
>>
>> CMake Error at build/VTK/VTKConfig.cmake:92 (find_package):
>>find_package Error reading CMake code from
>>
>> "/home/abuild/rpmbuild/BUILD/ParaView-v5.5.0/build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake".
>> Call Stack (most recent call first):
>>CMake/ParaViewModuleTop.cmake:89 (include)
>>CMakeLists.txt:676 (include)
>
>
> Can someone please have a look whether it is a bug or a wrong
> configuration from openSuse? The CMake call is
>
> %cmake  -DPV_INSTALL_LIB_DIR:PATH=%{_lib}/%{name} \
>  -DVTK_INSTALL_INCLUDE_DIR:PATH=include/%{name} \
>  -DVTK_INSTALL_ARCHIVE_DIR:PATH=%{_lib}/%{name} \
>  -DVTK_INSTALL_LIBRARY_DIR:PATH=%{_lib}/%{name} \
>  -DVTK_INSTALL_DATA_DIR=share/%{name} \
>  -DVTK_INSTALL_DOC_DIR=share/doc/packages/%{name} \
>  -DCMAKE_CXX_COMPILER:FILEPATH=$CXX \
>  -DCMAKE_C_COMPILER:FILEPATH=$CC \
>  -DCMAKE_SKIP_RPATH:BOOL=OFF \
>  -DPARAVIEW_BUILD_QT_GUI:BOOL=ON \
>  -DPARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=ON \
>  -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
>  -DVTK_WRAP_PYTHON:BOOL=ON \
>  -DVTK_WRAP_PYTHON_SIP:BOOL=ON \
>  -DVTK_OPENGL_HAS_OSMESA:BOOL=OFF \
>  -DVTK_USE_SYSTEM_EXPAT:BOOL=ON \
>  -DVTK_USE_SYSTEM_FREETYPE:BOOL=ON \

Re: [Paraview] CMake error from VTKConfig.cmake

2018-04-16 Thread Mark Olesen


May be related:
https://gitlab.kitware.com/paraview/paraview/issues/18116


I can build 5.5.0 on opensuse leap 42.3, but do get *really* weird junk 
in the VTKmConfig.cmake file:


# The VTKm version number
set(VTKm_VERSION_MAJOR "4")
set(VTKm_VERSION_MINOR "8")
set(VTKm_VERSION_PATCH "5")
set(VTKm_VERSION_FULL "4.8.5
-- Check for working Fortran compiler: /usr/bin/gfortran
-- Check for working Fortran compiler: /usr/bin/gfortran  -- works
-- Detecting Fortran compiler ABI info
-- Detecting Fortran compiler ABI info - done
-- Checking whether /usr/bin/gfortran supports Fortran 90
-- Checking whether /usr/bin/gfortran supports Fortran 90 -- yes
-- Configuring done
-- Generating done
-- Build files have been written to: 
/home/mol/test/build/ParaView-5.5.0/CMakeFiles/CheckFortran

")
set(VTKm_VERSION "4.8")


The version "4.8.5" look suspiciously like my gcc version.
The rest of the information "Check for working Fortran" etc, really 
looks like misdirected output somewhere in the cmake files.


/mark


On 04/16/18 18:14, Utkarsh Ayachit wrote:

Christoph,

I am totally unfamiliar with OpenSUSE and my initial attempts to even
install a C++ compiler are going no where :). Mind making it easier
for me and just post the full error message that you're getting? Maybe
attaching the 
/home/abuild/rpmbuild/BUILD/ParaView-v5.5.0/build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake
file will throw some light. Also is this failing when building the
Examples or just ther full ParaView build? I'd suggest disabling
examples, if that's the issue. The ParaView RPM should probably not
include examples any ways.

Utkarsh

On Sun, Apr 15, 2018 at 4:00 PM, Christoph Grüninger  wrote:

Hi Utkarsh,
I used openSuse build service (OBS) which currently builds it on Leap
42.2 and Tumblewheed. If you want to give it a shot, try the package
which I branched:
home:mathletic:branches:science/paraview

Bye
Christoph


Am 15.04.2018 um 16:40 schrieb Utkarsh Ayachit:

Christoph,

What openSuse version are you building on? I'll see if I can reproduce
using the same version Docker image, if available. Will make it easier
to track down.

Utkarsh

On Sun, Apr 15, 2018 at 7:08 AM, Christoph Grüninger  wrote:

Dear ParaView community,
I tried to update openSuse's ParaView RPM. Unfortunately I get the
following CMake error.


CMake Error at 
build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake:289:
   Parse error.  Function missing ending ")".  Instead found unterminated
   string with text ")

 endif()

   endforeach()



   check_required_components(VTKm)

   ".
Call Stack (most recent call first):
   build/VTK/VTKConfig.cmake:92 (find_package)
   CMake/ParaViewModuleTop.cmake:89 (include)
   CMakeLists.txt:676 (include)


CMake Error at build/VTK/VTKConfig.cmake:92 (find_package):
   find_package Error reading CMake code from
   
"/home/abuild/rpmbuild/BUILD/ParaView-v5.5.0/build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake".
Call Stack (most recent call first):
   CMake/ParaViewModuleTop.cmake:89 (include)
   CMakeLists.txt:676 (include)


Can someone please have a look whether it is a bug or a wrong
configuration from openSuse? The CMake call is

%cmake  -DPV_INSTALL_LIB_DIR:PATH=%{_lib}/%{name} \
 -DVTK_INSTALL_INCLUDE_DIR:PATH=include/%{name} \
 -DVTK_INSTALL_ARCHIVE_DIR:PATH=%{_lib}/%{name} \
 -DVTK_INSTALL_LIBRARY_DIR:PATH=%{_lib}/%{name} \
 -DVTK_INSTALL_DATA_DIR=share/%{name} \
 -DVTK_INSTALL_DOC_DIR=share/doc/packages/%{name} \
 -DCMAKE_CXX_COMPILER:FILEPATH=$CXX \
 -DCMAKE_C_COMPILER:FILEPATH=$CC \
 -DCMAKE_SKIP_RPATH:BOOL=OFF \
 -DPARAVIEW_BUILD_QT_GUI:BOOL=ON \
 -DPARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=ON \
 -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
 -DVTK_WRAP_PYTHON:BOOL=ON \
 -DVTK_WRAP_PYTHON_SIP:BOOL=ON \
 -DVTK_OPENGL_HAS_OSMESA:BOOL=OFF \
 -DVTK_USE_SYSTEM_EXPAT:BOOL=ON \
 -DVTK_USE_SYSTEM_FREETYPE:BOOL=ON \
 -DVTK_USE_SYSTEM_JPEG:BOOL=ON \
 -DVTK_USE_SYSTEM_PNG:BOOL=ON \
 -DVTK_USE_SYSTEM_TIFF:BOOL=ON \
 -DVTK_USE_SYSTEM_ZLIB:BOOL=ON \
 -DVTK_USE_SYSTEM_ZOPE:BOOL=ON \
 -DVTK_USE_SYSTEM_TWISTED:BOOL=ON \
 -DVTK_USE_SYSTEM_GL2PS:BOOL=OFF \
 -DBUILD_DOCUMENTATION:BOOL=ON \
 -DBUILD_EXAMPLES:BOOL=ON \
 -DBUILD_TESTING:BOOL=OFF

Unrelated, but still irritating are dozens of CMake warnings like:


CMake Warning (dev) at 
build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake:278:
   Syntax Warning in cmake code at column 25

   Argument not separated from preceding token by whitespace.
Call Stack (most recent call first):
   build/VTK/VTKConfig.cmake:92 (find_package)
   CMake/ParaViewModuleTop.cmake:89 (include)
   CMakeLists.txt:676 (include)
This warning is for project developers.  Use

Re: [Paraview] CMake error from VTKConfig.cmake

2018-04-15 Thread Christoph Grüninger

Hi Utkarsh,
I used openSuse build service (OBS) which currently builds it on Leap
42.2 and Tumblewheed. If you want to give it a shot, try the package
which I branched:
home:mathletic:branches:science/paraview

Bye
Christoph


Am 15.04.2018 um 16:40 schrieb Utkarsh Ayachit:
> Christoph,
> 
> What openSuse version are you building on? I'll see if I can reproduce
> using the same version Docker image, if available. Will make it easier
> to track down.
> 
> Utkarsh
> 
> On Sun, Apr 15, 2018 at 7:08 AM, Christoph Grüninger  
> wrote:
>> Dear ParaView community,
>> I tried to update openSuse's ParaView RPM. Unfortunately I get the
>> following CMake error.
>>
>>> CMake Error at 
>>> build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake:289:
>>>   Parse error.  Function missing ending ")".  Instead found unterminated
>>>   string with text ")
>>>
>>> endif()
>>>
>>>   endforeach()
>>>
>>>
>>>
>>>   check_required_components(VTKm)
>>>
>>>   ".
>>> Call Stack (most recent call first):
>>>   build/VTK/VTKConfig.cmake:92 (find_package)
>>>   CMake/ParaViewModuleTop.cmake:89 (include)
>>>   CMakeLists.txt:676 (include)
>>>
>>>
>>> CMake Error at build/VTK/VTKConfig.cmake:92 (find_package):
>>>   find_package Error reading CMake code from
>>>   
>>> "/home/abuild/rpmbuild/BUILD/ParaView-v5.5.0/build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake".
>>> Call Stack (most recent call first):
>>>   CMake/ParaViewModuleTop.cmake:89 (include)
>>>   CMakeLists.txt:676 (include)
>>
>> Can someone please have a look whether it is a bug or a wrong
>> configuration from openSuse? The CMake call is
>>
>> %cmake  -DPV_INSTALL_LIB_DIR:PATH=%{_lib}/%{name} \
>> -DVTK_INSTALL_INCLUDE_DIR:PATH=include/%{name} \
>> -DVTK_INSTALL_ARCHIVE_DIR:PATH=%{_lib}/%{name} \
>> -DVTK_INSTALL_LIBRARY_DIR:PATH=%{_lib}/%{name} \
>> -DVTK_INSTALL_DATA_DIR=share/%{name} \
>> -DVTK_INSTALL_DOC_DIR=share/doc/packages/%{name} \
>> -DCMAKE_CXX_COMPILER:FILEPATH=$CXX \
>> -DCMAKE_C_COMPILER:FILEPATH=$CC \
>> -DCMAKE_SKIP_RPATH:BOOL=OFF \
>> -DPARAVIEW_BUILD_QT_GUI:BOOL=ON \
>> -DPARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=ON \
>> -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
>> -DVTK_WRAP_PYTHON:BOOL=ON \
>> -DVTK_WRAP_PYTHON_SIP:BOOL=ON \
>> -DVTK_OPENGL_HAS_OSMESA:BOOL=OFF \
>> -DVTK_USE_SYSTEM_EXPAT:BOOL=ON \
>> -DVTK_USE_SYSTEM_FREETYPE:BOOL=ON \
>> -DVTK_USE_SYSTEM_JPEG:BOOL=ON \
>> -DVTK_USE_SYSTEM_PNG:BOOL=ON \
>> -DVTK_USE_SYSTEM_TIFF:BOOL=ON \
>> -DVTK_USE_SYSTEM_ZLIB:BOOL=ON \
>> -DVTK_USE_SYSTEM_ZOPE:BOOL=ON \
>> -DVTK_USE_SYSTEM_TWISTED:BOOL=ON \
>> -DVTK_USE_SYSTEM_GL2PS:BOOL=OFF \
>> -DBUILD_DOCUMENTATION:BOOL=ON \
>> -DBUILD_EXAMPLES:BOOL=ON \
>> -DBUILD_TESTING:BOOL=OFF
>>
>> Unrelated, but still irritating are dozens of CMake warnings like:
>>
>>> CMake Warning (dev) at 
>>> build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake:278:
>>>   Syntax Warning in cmake code at column 25
>>>
>>>   Argument not separated from preceding token by whitespace.
>>> Call Stack (most recent call first):
>>>   build/VTK/VTKConfig.cmake:92 (find_package)
>>>   CMake/ParaViewModuleTop.cmake:89 (include)
>>>   CMakeLists.txt:676 (include)
>>> This warning is for project developers.  Use -Wno-dev to suppress it.
>>
>> Bye
>> Christoph
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] CMake error from VTKConfig.cmake

2018-04-15 Thread Utkarsh Ayachit

Christoph,

What openSuse version are you building on? I'll see if I can reproduce
using the same version Docker image, if available. Will make it easier
to track down.

Utkarsh

On Sun, Apr 15, 2018 at 7:08 AM, Christoph Grüninger  wrote:
> Dear ParaView community,
> I tried to update openSuse's ParaView RPM. Unfortunately I get the
> following CMake error.
>
>> CMake Error at 
>> build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake:289:
>>   Parse error.  Function missing ending ")".  Instead found unterminated
>>   string with text ")
>>
>> endif()
>>
>>   endforeach()
>>
>>
>>
>>   check_required_components(VTKm)
>>
>>   ".
>> Call Stack (most recent call first):
>>   build/VTK/VTKConfig.cmake:92 (find_package)
>>   CMake/ParaViewModuleTop.cmake:89 (include)
>>   CMakeLists.txt:676 (include)
>>
>>
>> CMake Error at build/VTK/VTKConfig.cmake:92 (find_package):
>>   find_package Error reading CMake code from
>>   
>> "/home/abuild/rpmbuild/BUILD/ParaView-v5.5.0/build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake".
>> Call Stack (most recent call first):
>>   CMake/ParaViewModuleTop.cmake:89 (include)
>>   CMakeLists.txt:676 (include)
>
> Can someone please have a look whether it is a bug or a wrong
> configuration from openSuse? The CMake call is
>
> %cmake  -DPV_INSTALL_LIB_DIR:PATH=%{_lib}/%{name} \
> -DVTK_INSTALL_INCLUDE_DIR:PATH=include/%{name} \
> -DVTK_INSTALL_ARCHIVE_DIR:PATH=%{_lib}/%{name} \
> -DVTK_INSTALL_LIBRARY_DIR:PATH=%{_lib}/%{name} \
> -DVTK_INSTALL_DATA_DIR=share/%{name} \
> -DVTK_INSTALL_DOC_DIR=share/doc/packages/%{name} \
> -DCMAKE_CXX_COMPILER:FILEPATH=$CXX \
> -DCMAKE_C_COMPILER:FILEPATH=$CC \
> -DCMAKE_SKIP_RPATH:BOOL=OFF \
> -DPARAVIEW_BUILD_QT_GUI:BOOL=ON \
> -DPARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=ON \
> -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
> -DVTK_WRAP_PYTHON:BOOL=ON \
> -DVTK_WRAP_PYTHON_SIP:BOOL=ON \
> -DVTK_OPENGL_HAS_OSMESA:BOOL=OFF \
> -DVTK_USE_SYSTEM_EXPAT:BOOL=ON \
> -DVTK_USE_SYSTEM_FREETYPE:BOOL=ON \
> -DVTK_USE_SYSTEM_JPEG:BOOL=ON \
> -DVTK_USE_SYSTEM_PNG:BOOL=ON \
> -DVTK_USE_SYSTEM_TIFF:BOOL=ON \
> -DVTK_USE_SYSTEM_ZLIB:BOOL=ON \
> -DVTK_USE_SYSTEM_ZOPE:BOOL=ON \
> -DVTK_USE_SYSTEM_TWISTED:BOOL=ON \
> -DVTK_USE_SYSTEM_GL2PS:BOOL=OFF \
> -DBUILD_DOCUMENTATION:BOOL=ON \
> -DBUILD_EXAMPLES:BOOL=ON \
> -DBUILD_TESTING:BOOL=OFF
>
> Unrelated, but still irritating are dozens of CMake warnings like:
>
>> CMake Warning (dev) at 
>> build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake:278:
>>   Syntax Warning in cmake code at column 25
>>
>>   Argument not separated from preceding token by whitespace.
>> Call Stack (most recent call first):
>>   build/VTK/VTKConfig.cmake:92 (find_package)
>>   CMake/ParaViewModuleTop.cmake:89 (include)
>>   CMakeLists.txt:676 (include)
>> This warning is for project developers.  Use -Wno-dev to suppress it.
>
> Bye
> Christoph
>
> --
> Unfortunately, plots are notoriously hard to get right. Partly, the
> default settings of programs like gnuplot or Excel are to blame for
> this since these programs make it very convenient to create bad plots.
> -- Till Tantau, "The TikZ and PGF Packages"
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: 
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://public.kitware.com/mailman/listinfo/paraview
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview

[Paraview] CMake error from VTKConfig.cmake

2018-04-15 Thread Christoph Grüninger

Dear ParaView community,
I tried to update openSuse's ParaView RPM. Unfortunately I get the
following CMake error.

> CMake Error at 
> build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake:289:
>   Parse error.  Function missing ending ")".  Instead found unterminated
>   string with text ")
> 
> endif()
> 
>   endforeach()
> 
>   
> 
>   check_required_components(VTKm)
> 
>   ".
> Call Stack (most recent call first):
>   build/VTK/VTKConfig.cmake:92 (find_package)
>   CMake/ParaViewModuleTop.cmake:89 (include)
>   CMakeLists.txt:676 (include)
> 
> 
> CMake Error at build/VTK/VTKConfig.cmake:92 (find_package):
>   find_package Error reading CMake code from
>   
> "/home/abuild/rpmbuild/BUILD/ParaView-v5.5.0/build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake".
> Call Stack (most recent call first):
>   CMake/ParaViewModuleTop.cmake:89 (include)
>   CMakeLists.txt:676 (include)

Can someone please have a look whether it is a bug or a wrong
configuration from openSuse? The CMake call is

%cmake  -DPV_INSTALL_LIB_DIR:PATH=%{_lib}/%{name} \
-DVTK_INSTALL_INCLUDE_DIR:PATH=include/%{name} \
-DVTK_INSTALL_ARCHIVE_DIR:PATH=%{_lib}/%{name} \
-DVTK_INSTALL_LIBRARY_DIR:PATH=%{_lib}/%{name} \
-DVTK_INSTALL_DATA_DIR=share/%{name} \
-DVTK_INSTALL_DOC_DIR=share/doc/packages/%{name} \
-DCMAKE_CXX_COMPILER:FILEPATH=$CXX \
-DCMAKE_C_COMPILER:FILEPATH=$CC \
-DCMAKE_SKIP_RPATH:BOOL=OFF \
-DPARAVIEW_BUILD_QT_GUI:BOOL=ON \
-DPARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=ON \
-DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
-DVTK_WRAP_PYTHON:BOOL=ON \
-DVTK_WRAP_PYTHON_SIP:BOOL=ON \
-DVTK_OPENGL_HAS_OSMESA:BOOL=OFF \
-DVTK_USE_SYSTEM_EXPAT:BOOL=ON \
-DVTK_USE_SYSTEM_FREETYPE:BOOL=ON \
-DVTK_USE_SYSTEM_JPEG:BOOL=ON \
-DVTK_USE_SYSTEM_PNG:BOOL=ON \
-DVTK_USE_SYSTEM_TIFF:BOOL=ON \
-DVTK_USE_SYSTEM_ZLIB:BOOL=ON \
-DVTK_USE_SYSTEM_ZOPE:BOOL=ON \
-DVTK_USE_SYSTEM_TWISTED:BOOL=ON \
-DVTK_USE_SYSTEM_GL2PS:BOOL=OFF \
-DBUILD_DOCUMENTATION:BOOL=ON \
-DBUILD_EXAMPLES:BOOL=ON \
-DBUILD_TESTING:BOOL=OFF

Unrelated, but still irritating are dozens of CMake warnings like:

> CMake Warning (dev) at 
> build/VTK/ThirdParty/vtkm/vtk-m/lib/cmake/paraview-5.5/vtkm/VTKmConfig.cmake:278:
>   Syntax Warning in cmake code at column 25
> 
>   Argument not separated from preceding token by whitespace.
> Call Stack (most recent call first):
>   build/VTK/VTKConfig.cmake:92 (find_package)
>   CMake/ParaViewModuleTop.cmake:89 (include)
>   CMakeLists.txt:676 (include)
> This warning is for project developers.  Use -Wno-dev to suppress it.

Bye
Christoph

-- 
Unfortunately, plots are notoriously hard to get right. Partly, the
default settings of programs like gnuplot or Excel are to blame for
this since these programs make it very convenient to create bad plots.
-- Till Tantau, "The TikZ and PGF Packages"
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] CMake error from VTKConfig.cmake

Re: [Paraview] CMake error from VTKConfig.cmake

Re: [Paraview] CMake error from VTKConfig.cmake

Re: [Paraview] CMake error from VTKConfig.cmake

Re: [Paraview] CMake error from VTKConfig.cmake

Re: [Paraview] CMake error from VTKConfig.cmake

Re: [Paraview] CMake error from VTKConfig.cmake

Re: [Paraview] CMake error from VTKConfig.cmake

Re: [Paraview] CMake error from VTKConfig.cmake

Re: [Paraview] CMake error from VTKConfig.cmake

Re: [Paraview] CMake error from VTKConfig.cmake

[Paraview] CMake error from VTKConfig.cmake

12 matches

Site Navigation

Mail list logo

Footer information