[Paraview] QT_HELP_GENERATOR-NOTFOUND
Dear All, I am trying to run compile ParaView on 64 bit openSUSE 11.2 with KDE 4.3.1. I was using this website as a reference http://www.cmake.org/Wiki/ParaView:Build_And_Install. Unfortunately after configuring the installation with ccmake I get QT_HELP_GENERATOR-NOTFOUND in QT_HELP_GENERATOR variable. Executing make ends up with an error: [ 99%] Built target H5PartReader [ 99%] Compiling Qt help project paraview.qhp /bin/sh: QT_HELP_GENERATOR-NOTFOUND: command not found make[2]: *** [Documentation/CMakeFiles/ParaViewOnlineHelp] Error 127 make[1]: *** [Documentation/CMakeFiles/ParaViewOnlineHelp.dir/all] Error 2 Could you let me know if you had any hints as to solve this problem? I would be very much obliged for any assistance. Kind regards, Robert ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Problem linking Cocoa pqWidgets
Berk -- out of curiosity, then, is your Qt 4.6 built for both i386 and x86_64 architectures, and using Cocoa? It doesn't necessarily make sense, but since I don't get the grayed out filters on my laptop which was using an older version of CMake (2.9.20091007) -- so it linked a bunch of PV libraries with additional OS X frameworks -- is it possible that with more recent CMake there are some other dependencies which are not being linked in, don't get caught at compile time, but are missing at run time? Anyway, as long as someone can put in that extra Cocoa line for pqWidgets, at least that will build with CVS CMake. Thanks, -Eric On Jan 6, 2010, at 10:14 PM, Berk Geveci wrote: Also, the progress bar issue is known - we will try to fix it before 2.8 but no guarantees. I never ran into the grayed out filters issue. I have been using Qt 4.6 btw. -berk On Wed, Jan 6, 2010 at 4:50 PM, Clinton Stimpson clin...@elemtech.com wrote: On Wednesday 06 January 2010 02:43:54 pm Eric E. Monson wrote: Hey Clint, Yes, I'm using CVS CMake (2.9.20100105). Qt is not static (unless that's the default, but I don't think it is). The default is shared/dynamic. So older versions of CMake added in other framework dependencies (like Carbon, ApplicationServices or AppKit) automatically based on what Qt was built with? Correct. So, your suggestion to fix Qt/Widgets/CMakeLists.txt needs to happen. Clint Thanks, -Eric On Jan 6, 2010, at 4:36 PM, Clinton Stimpson wrote: Did you use the CVS version of CMake? FindQt4/UseQt don't put the extra dependencies in there anymore unless Qt is static. So if pqWidgets uses Cocoa, it needs to link against the Cocoa framework. Clint On Wednesday 06 January 2010 01:35:39 pm Eric E. Monson wrote: Hello, On one of my machines I just switched over to Snow Leopard, so I did a fresh CVS grab of ParaView. I have Qt 4.5.3 built from source for Cocoa (x86 and x86_64 architectures), and I have been trying to build ParaView (i386;x86_64), but keep getting a linking error on the pqWidgets library: [ 90%] Built target QtTesting Linking CXX shared library ../../bin/libpqWidgets.dylib Undefined symbols: _objc_msgSend, referenced from: pqProgressBarHelper::setProgress(int)in pqProgressBarHelper.mm.o pqProgressBarHelper::setProgress(int)in pqProgressBarHelper.mm.o pqProgressBarHelper::setProgress(int)in pqProgressBarHelper.mm.o ld: symbol(s) not found collect2: ld returned 1 exit status Undefined symbols: _objc_msgSend, referenced from: pqProgressBarHelper::setProgress(int)in pqProgressBarHelper.mm.o pqProgressBarHelper::setProgress(int)in pqProgressBarHelper.mm.o pqProgressBarHelper::setProgress(int)in pqProgressBarHelper.mm.o ld: symbol(s) not found I found I can get past this if I add a -framework Cocoa to the linker line manually, so I think in ParaView3/Qt/Widgets/CMakeLists.txt maybe there should be another check added, something like (line 198): if(VTK_USE_COCOA) TARGET_LINK_LIBRARIES(pqWidgets -framework Cocoa) endif(VTK_USE_COCOA) The progress bar doesn't really work and I'm running into the grayed out filters that some others have mentioned (filters show up right after launching PV, I can generate or load a source, and I can apply one filter, but then they disappear after that and won't come back), but at least PV compiled... :) Not sure if it's relevant, but in case it's helpful: On another machine with a very similar setup (Snow Leopard and x86,x86_64 Cocoa Qt 4.5.2 from source), but just CVS update and rebuild on an old checkout rather than a fresh one, I noticed that the pqWidgets_LIB_DEPENDS (and a bunch of other things) include ;general;-framework Carbon;general;-framework AppKit;general;-framework ApplicationServices; The progress bar doesn't work on that version, either, but I don't get the grayed out filters problem. Thanks, -Eric -- Eric E Monson Duke Visualization Technology Group ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at
Re: [Paraview] Problem linking Cocoa pqWidgets
Berk -- out of curiosity, then, is your Qt 4.6 built for both i386 and x86_64 architectures, and using Cocoa? I used i386 (Carbon and Cocoa) initially but I am now using 64 bit Cocoa exclusively. -berk On Thu, Jan 7, 2010 at 9:27 AM, Eric E. Monson emon...@cs.duke.edu wrote: Berk -- out of curiosity, then, is your Qt 4.6 built for both i386 and x86_64 architectures, and using Cocoa? It doesn't necessarily make sense, but since I don't get the grayed out filters on my laptop which was using an older version of CMake (2.9.20091007) -- so it linked a bunch of PV libraries with additional OS X frameworks -- is it possible that with more recent CMake there are some other dependencies which are not being linked in, don't get caught at compile time, but are missing at run time? Anyway, as long as someone can put in that extra Cocoa line for pqWidgets, at least that will build with CVS CMake. Thanks, -Eric On Jan 6, 2010, at 10:14 PM, Berk Geveci wrote: Also, the progress bar issue is known - we will try to fix it before 2.8 but no guarantees. I never ran into the grayed out filters issue. I have been using Qt 4.6 btw. -berk On Wed, Jan 6, 2010 at 4:50 PM, Clinton Stimpson clin...@elemtech.com wrote: On Wednesday 06 January 2010 02:43:54 pm Eric E. Monson wrote: Hey Clint, Yes, I'm using CVS CMake (2.9.20100105). Qt is not static (unless that's the default, but I don't think it is). The default is shared/dynamic. So older versions of CMake added in other framework dependencies (like Carbon, ApplicationServices or AppKit) automatically based on what Qt was built with? Correct. So, your suggestion to fix Qt/Widgets/CMakeLists.txt needs to happen. Clint Thanks, -Eric On Jan 6, 2010, at 4:36 PM, Clinton Stimpson wrote: Did you use the CVS version of CMake? FindQt4/UseQt don't put the extra dependencies in there anymore unless Qt is static. So if pqWidgets uses Cocoa, it needs to link against the Cocoa framework. Clint On Wednesday 06 January 2010 01:35:39 pm Eric E. Monson wrote: Hello, On one of my machines I just switched over to Snow Leopard, so I did a fresh CVS grab of ParaView. I have Qt 4.5.3 built from source for Cocoa (x86 and x86_64 architectures), and I have been trying to build ParaView (i386;x86_64), but keep getting a linking error on the pqWidgets library: [ 90%] Built target QtTesting Linking CXX shared library ../../bin/libpqWidgets.dylib Undefined symbols: _objc_msgSend, referenced from: pqProgressBarHelper::setProgress(int) in pqProgressBarHelper.mm.o pqProgressBarHelper::setProgress(int) in pqProgressBarHelper.mm.o pqProgressBarHelper::setProgress(int) in pqProgressBarHelper.mm.o ld: symbol(s) not found collect2: ld returned 1 exit status Undefined symbols: _objc_msgSend, referenced from: pqProgressBarHelper::setProgress(int) in pqProgressBarHelper.mm.o pqProgressBarHelper::setProgress(int) in pqProgressBarHelper.mm.o pqProgressBarHelper::setProgress(int) in pqProgressBarHelper.mm.o ld: symbol(s) not found I found I can get past this if I add a -framework Cocoa to the linker line manually, so I think in ParaView3/Qt/Widgets/CMakeLists.txt maybe there should be another check added, something like (line 198): if(VTK_USE_COCOA) TARGET_LINK_LIBRARIES(pqWidgets -framework Cocoa) endif(VTK_USE_COCOA) The progress bar doesn't really work and I'm running into the grayed out filters that some others have mentioned (filters show up right after launching PV, I can generate or load a source, and I can apply one filter, but then they disappear after that and won't come back), but at least PV compiled... :) Not sure if it's relevant, but in case it's helpful: On another machine with a very similar setup (Snow Leopard and x86,x86_64 Cocoa Qt 4.5.2 from source), but just CVS update and rebuild on an old checkout rather than a fresh one, I noticed that the pqWidgets_LIB_DEPENDS (and a bunch of other things) include ;general;-framework Carbon;general;-framework AppKit;general;-framework ApplicationServices; The progress bar doesn't work on that version, either, but I don't get the grayed out filters problem. Thanks, -Eric -- Eric E Monson Duke Visualization Technology Group ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/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:
Re: [Paraview] QT_HELP_GENERATOR-NOTFOUND
Ensure that QT_HELP_GENERATOR is set to the qhelpgenerator executable. Where can I find this one? Apparently ccmake cannot find autumatically. Maybe it is not supplied with openSUSE Qt package. Is there any way to do it manually? It's probably located at the same location as qmake. You might want to look at openSUSE Qt package details to see if they even provide the generator or if it's in a different package or something. 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] QT_HELP_GENERATOR-NOTFOUND
Thanks for your reply. What version of Qt are you using? My Qt version is 4.5.3. Ensure that QT_HELP_GENERATOR is set to the qhelpgenerator executable. Where can I find this one? Apparently ccmake cannot find autumatically. Maybe it is not supplied with openSUSE Qt package. Is there any way to do it manually? Best wishes, Robert ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] QT_HELP_GENERATOR-NOTFOUND
Thanks again for the hints. It was indeed in a different package. Can't say exactly which one since I simply added all the qt4 packages that borne the signature of Trolltech. make and make install work just fine now. Thank you! Robert ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Latest CVS - Mac compiling problem
Gents, I'mhaving this error when compiling today's cvs : [ 48%] Built target vtkWrapClientServer Linking CXX shared library ../../../bin/libvtkCommonCS.dylib Undefined symbols: vtkDataSet_Init(vtkClientServerInterpreter*), referenced from: vtkPlane_Init(vtkClientServerInterpreter*) in vtkPlaneClientServer.cxx.o ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: *** [bin/libvtkCommonCS.dylib] Error 1 make[1]: *** [Utilities/VTKClientServer/Common/CMakeFiles/vtkCommonCS.dir/all] Error 2 make: *** [all] Error 2 Does not happen under Linux, only under Mac. Any idea ? Regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Latest CVS - Mac compiling problem
Update your CVS and try again. This looks like it is from a problematic
checkin to VTK that has been reverted this morning.
-Ken
On 1/7/10 10:48 AM, Pierre-Olivier Dallaire
pierre-olivier.dalla...@videotron.ca wrote:
Gents,
I'mhaving this error when compiling today's cvs :
[ 48%] Built target vtkWrapClientServer
Linking CXX shared library ../../../bin/libvtkCommonCS.dylib
Undefined symbols:
vtkDataSet_Init(vtkClientServerInterpreter*), referenced from:
vtkPlane_Init(vtkClientServerInterpreter*) in
vtkPlaneClientServer.cxx.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[2]: *** [bin/libvtkCommonCS.dylib] Error 1
make[1]: *** [Utilities/VTKClientServer/Common/CMakeFiles/vtkCommonCS.dir/all]
Error 2
make: *** [all] Error 2
Does not happen under Linux, only under Mac. Any idea ?
Regards,
PO
___
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
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
Kenneth Moreland
*** Sandia National Laboratories
***
*** *** *** email: kmo...@sandia.gov
** *** ** phone: (505) 844-8919
*** web: http://www.cs.unm.edu/~kmorel
___
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
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Latest CVS - Mac compiling problem
Works / thank you ! On 2010-01-07, at 1:37 PM, Moreland, Kenneth wrote: Update your CVS and try again. This looks like it is from a problematic checkin to VTK that has been reverted this morning. -Ken On 1/7/10 10:48 AM, Pierre-Olivier Dallaire pierre-olivier.dalla...@videotron.ca wrote: Gents, I'mhaving this error when compiling today's cvs : [ 48%] Built target vtkWrapClientServer Linking CXX shared library ../../../bin/libvtkCommonCS.dylib Undefined symbols: vtkDataSet_Init(vtkClientServerInterpreter*), referenced from: vtkPlane_Init(vtkClientServerInterpreter*) in vtkPlaneClientServer.cxx.o ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: *** [bin/libvtkCommonCS.dylib] Error 1 make[1]: *** [Utilities/VTKClientServer/Common/CMakeFiles/vtkCommonCS.dir/all] Error 2 make: *** [all] Error 2 Does not happen under Linux, only under Mac. Any idea ? Regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview Kenneth Moreland *** Sandia National Laboratories *** *** *** *** email: kmo...@sandia.gov ** *** ** phone: (505) 844-8919 *** web: http://www.cs.unm.edu/~kmorel ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Problem linking Cocoa pqWidgets
In case anyone is interested, I'm not seeing the grayed out filters after doing a fresh build of Qt 4.6.0 from source, configured with: ./configure -release -plugin-sql-sqlite -arch x86_64 -cocoa (the sqlite is for another project), and building yesterday's CVS ParaView (with the change to ParaView3/Qt/Widgets/CMakeLists.txt that I mentioned in my original post) for x86_64 architecture under OS X 10.6.2 using CMake 2.9.20100105. Thanks, -Eric On Jan 7, 2010, at 9:30 AM, Berk Geveci wrote: Berk -- out of curiosity, then, is your Qt 4.6 built for both i386 and x86_64 architectures, and using Cocoa? I used i386 (Carbon and Cocoa) initially but I am now using 64 bit Cocoa exclusively. -berk On Thu, Jan 7, 2010 at 9:27 AM, Eric E. Monson emon...@cs.duke.edu wrote: Berk -- out of curiosity, then, is your Qt 4.6 built for both i386 and x86_64 architectures, and using Cocoa? It doesn't necessarily make sense, but since I don't get the grayed out filters on my laptop which was using an older version of CMake (2.9.20091007) -- so it linked a bunch of PV libraries with additional OS X frameworks -- is it possible that with more recent CMake there are some other dependencies which are not being linked in, don't get caught at compile time, but are missing at run time? Anyway, as long as someone can put in that extra Cocoa line for pqWidgets, at least that will build with CVS CMake. Thanks, -Eric On Jan 6, 2010, at 10:14 PM, Berk Geveci wrote: Also, the progress bar issue is known - we will try to fix it before 2.8 but no guarantees. I never ran into the grayed out filters issue. I have been using Qt 4.6 btw. -berk On Wed, Jan 6, 2010 at 4:50 PM, Clinton Stimpson clin...@elemtech.com wrote: On Wednesday 06 January 2010 02:43:54 pm Eric E. Monson wrote: Hey Clint, Yes, I'm using CVS CMake (2.9.20100105). Qt is not static (unless that's the default, but I don't think it is). The default is shared/dynamic. So older versions of CMake added in other framework dependencies (like Carbon, ApplicationServices or AppKit) automatically based on what Qt was built with? Correct. So, your suggestion to fix Qt/Widgets/CMakeLists.txt needs to happen. Clint Thanks, -Eric On Jan 6, 2010, at 4:36 PM, Clinton Stimpson wrote: Did you use the CVS version of CMake? FindQt4/UseQt don't put the extra dependencies in there anymore unless Qt is static. So if pqWidgets uses Cocoa, it needs to link against the Cocoa framework. Clint On Wednesday 06 January 2010 01:35:39 pm Eric E. Monson wrote: Hello, On one of my machines I just switched over to Snow Leopard, so I did a fresh CVS grab of ParaView. I have Qt 4.5.3 built from source for Cocoa (x86 and x86_64 architectures), and I have been trying to build ParaView (i386;x86_64), but keep getting a linking error on the pqWidgets library: [ 90%] Built target QtTesting Linking CXX shared library ../../bin/libpqWidgets.dylib Undefined symbols: _objc_msgSend, referenced from: pqProgressBarHelper::setProgress(int)in pqProgressBarHelper.mm.o pqProgressBarHelper::setProgress(int)in pqProgressBarHelper.mm.o pqProgressBarHelper::setProgress(int)in pqProgressBarHelper.mm.o ld: symbol(s) not found collect2: ld returned 1 exit status Undefined symbols: _objc_msgSend, referenced from: pqProgressBarHelper::setProgress(int)in pqProgressBarHelper.mm.o pqProgressBarHelper::setProgress(int)in pqProgressBarHelper.mm.o pqProgressBarHelper::setProgress(int)in pqProgressBarHelper.mm.o ld: symbol(s) not found I found I can get past this if I add a -framework Cocoa to the linker line manually, so I think in ParaView3/Qt/Widgets/CMakeLists.txt maybe there should be another check added, something like (line 198): if(VTK_USE_COCOA) TARGET_LINK_LIBRARIES(pqWidgets -framework Cocoa) endif(VTK_USE_COCOA) The progress bar doesn't really work and I'm running into the grayed out filters that some others have mentioned (filters show up right after launching PV, I can generate or load a source, and I can apply one filter, but then they disappear after that and won't come back), but at least PV compiled... :) Not sure if it's relevant, but in case it's helpful: On another machine with a very similar setup (Snow Leopard and x86,x86_64 Cocoa Qt 4.5.2 from source), but just CVS update and rebuild on an old checkout rather than a fresh one, I noticed that the pqWidgets_LIB_DEPENDS (and a bunch of other things) include ;general;-framework Carbon;general;-framework AppKit;general;-framework ApplicationServices; The progress bar doesn't work on that version, either, but I don't get the grayed out filters problem. Thanks, -Eric -- Eric E Monson Duke Visualization Technology Group ___ Powered by www.kitware.com Visit other
[Paraview] ParaView 3.6.2 Release and hdf5-1.8
I have tried compiling pv3.6.2 with my system's hdf5 and have run into the following issue: regardless of what api-version I use to configure compile hdf5 (v16 or v18), I cannot compile pv because of the following error: /apps-vis/ParaView3-6-2/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx:174: error: braces around scalar initializer for type ‘herr_t (*)(H5FD_t*, unsigned char*, unsigned int, hbool_t)’ Badly placed (. /apps-vis/ParaView3-6-2/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx:174: error: invalid conversion from ‘haddr_t (*)(H5FD_t*)’ to ‘herr_t (*)(H5FD_t*, H5FD_mem_t, hid_t, haddr_t, hsize_t)’ Badly placed (. etc. here is my last config for hdf5: ./configure --enable-parallel --enable-linux-lfs --enable-shared --with-default-api-version=v18 The good news: I was able to make the compilation finish after copying XdmfH5Driver.cxx from the CVS version of ParaView. And so far in execution trials, nothing has broken. Has anyone else seen this? I had initially configured hdf5 with the default (i.e without specifying the last option --with-default-api-version=v??). I then tried with v16, and v18, and in both cases, I could not compile, until I overwrote the source with the cvs copy. - Jean M. Favre Scientific Computing Research Swiss National Supercomputing Center CH-6828 Manno Switzerland ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParaView 3.6.2 Release and hdf5-1.8
On Fri, 08 Jan 2010 10:21:22 Favre Jean wrote:
I have tried compiling pv3.6.2 with my system's hdf5 and have run into the
following issue:
regardless of what api-version I use to configure compile hdf5 (v16 or
v18), I cannot compile pv because of the following error:
/apps-vis/ParaView3-6-2/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx:174: error:
braces around scalar initializer for type ‘herr_t (*)(H5FD_t*, unsigned
char*, unsigned int, hbool_t)’ Badly placed (.
/apps-vis/ParaView3-6-2/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx:174: error:
invalid conversion from ‘haddr_t (*)(H5FD_t*)’ to ‘herr_t (*)(H5FD_t*,
H5FD_mem_t, hid_t, haddr_t, hsize_t)’ Badly placed (.
etc.
here is my last config for hdf5:
./configure --enable-parallel --enable-linux-lfs --enable-shared
--with-default-api-version=v18
The good news:
I was able to make the compilation finish after copying XdmfH5Driver.cxx
from the CVS version of ParaView. And so far in execution trials, nothing
has broken.
Has anyone else seen this? I had initially configured hdf5 with the default
(i.e without specifying the last option --with-default-api-version=v??).
I then tried with v16, and v18, and in both cases, I could not compile,
until I overwrote the source with the cvs copy.
In Gentoo we have a patch for XdmfH5Driver.cxx - It was introduced for
paraview 3.6.1 but it may still be current.
I am attaching for reference. One thing to note conditional compilation is
introduced for HDF5 v1.6 and 1.8. From the look of the patch the code
that is left alone is geared to HDF5 v1.8 but paraview ship with version 1.6
so paraview version may have been patched to include some v1.8 bits.
Most interesting are these 2 bits that are not conditional:
@@ -159,6 +165,7 @@
H5FD_dsm_close, /*close */
H5FD_dsm_cmp, /*cmp */
NULL, /*query */
+NULL, /*type map */
NULL, /*alloc */
NULL, /*free */
H5FD_dsm_get_eoa, /*get_eoa */
@@ -168,6 +175,7 @@
H5FD_dsm_read, /*read */
H5FD_dsm_write, /*write */
NULL, /*flush */
+NULL, /*truncate */
NULL, /*lock */
NULL, /*unlock*/
H5FD_FLMAP_SINGLE /*fl_map*/
this is in the definition of H5FD_class_t H5FD_dsm_g, that would fit with your
error message ie line 174 the definition supplied is too short and misses some
fields.
diff -Naur ParaView3/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx ParaView3.new/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx
--- ParaView3/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx 2009-07-20 15:39:10.0 -0400
+++ ParaView3.new/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx 2009-07-22 16:05:22.0 -0400
@@ -132,9 +132,15 @@
static herr_t H5FD_dsm_flush(H5FD_t *_file);
#endif
static int H5FD_dsm_cmp(const H5FD_t *_f1, const H5FD_t *_f2);
+#ifdef H5_USE_16_API
+static haddr_t H5FD_dsm_get_eoa(const H5FD_t *_file, H5FD_mem_t);
+static herr_t H5FD_dsm_set_eoa(H5FD_t *_file, H5FD_mem_t, haddr_t addr);
+static haddr_t H5FD_dsm_get_eof(const H5FD_t *_file);
+#else
static haddr_t H5FD_dsm_get_eoa(H5FD_t *_file);
static herr_t H5FD_dsm_set_eoa(H5FD_t *_file, haddr_t addr);
static haddr_t H5FD_dsm_get_eof(H5FD_t *_file);
+#endif
static herr_t H5FD_dsm_read(H5FD_t *_file, H5FD_mem_t type, hid_t fapl_id, haddr_t addr,
DSM_HSIZE_T size, void *buf);
static herr_t H5FD_dsm_write(H5FD_t *_file, H5FD_mem_t type, hid_t fapl_id, haddr_t addr,
@@ -159,6 +165,7 @@
H5FD_dsm_close, /*close */
H5FD_dsm_cmp, /*cmp */
NULL, /*query */
+NULL, /*type map */
NULL, /*alloc */
NULL, /*free */
H5FD_dsm_get_eoa, /*get_eoa */
@@ -168,6 +175,7 @@
H5FD_dsm_read, /*read */
H5FD_dsm_write, /*write */
NULL, /*flush */
+NULL, /*truncate */
NULL, /*lock */
NULL, /*unlock*/
H5FD_FLMAP_SINGLE /*fl_map*/
@@ -594,7 +602,11 @@
*-
*/
static haddr_t
+#ifdef H5_USE_16_API
+H5FD_dsm_get_eoa(const H5FD_t *_file, H5FD_mem_t)
+#else
H5FD_dsm_get_eoa(H5FD_t *_file)
+#endif
{
H5FD_dsm_t *file = (H5FD_dsm_t*)_file;
@@ -622,7 +634,11 @@
*-
*/
static herr_t
+#ifdef H5_USE_16_API
+H5FD_dsm_set_eoa(H5FD_t *_file, H5FD_mem_t,
