Thank you for the suggestion. Making the change did allow it to get past that point, but then it ran into a whole mess of errors later. Is it likely that I did something wrong at some point during the installation (before I started editing files), or will the
3.2.0 release really not compile as-is?<br><br>Is the ITK available as a package from anywhere?<br><br>Thanks again for any help!<br> - Dan<br><br>A sample:<br>[ 15%] Built target itkjpeg16<br>[ 17%] Built target itkgdcm<br>
[ 17%] Built target ITKznz<br>[ 17%] Built target ITKniftiio<br>[ 17%] Built target itkvcl<br>Linking CXX executable vcl_test_all<br>CMakeFiles/vcl_test_all.dir/test_driver.o: In function `__static_initialization_and_destruction_0(int, int)':
<br>test_driver.cxx:(.text+0x23): undefined reference to `std::ios_base::Init::Init()'<br>CMakeFiles/vcl_test_all.dir/test_driver.o: In function `__tcf_0':<br>test_driver.cxx:(.text+0x6c): undefined reference to `std::ios_base::Init::~Init()'
<br>CMakeFiles/vcl_test_all.dir/test_driver.o: In function `testresult(int)':<br>test_driver.cxx:(.text+0x96): undefined reference to `std::cout'<br>test_driver.cxx:(.text+0x9b): undefined reference to `std::basic_ostream<char, std::char_traits<char> >& std::operator$
<br>test_driver.cxx:(.text+0xa3): undefined reference to `std::basic_ostream<char, std::char_traits<char> >& std::endl<cha$<br>test_driver.cxx:(.text+0xab): undefined reference to `std::basic_ostream<char, std::char_traits<char> >::operator<<(st$
<br>test_driver.cxx:(.text+0xc9): undefined reference to `std::cout'<br><br><br><div><span class="gmail_quote">On 5/23/07, <b class="gmail_sendername">R Holbrey</b> <<a href="mailto:richardh@comp.leeds.ac.uk">richardh@comp.leeds.ac.uk
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Wed, 23 May 2007, Dan Homerick wrote:<br><br>> Building the ITK with gcc (ver
4.1.2) and cmake (ver 2.4-patch 6) in Ubuntu<br>> (ver 7.04), I received the following error:<br>><br>> [ 1%] Built target mkg3states<br>> [ 3%] Built target itkjpeg8<br>> [ 4%] Built target itktiff<br>> [ 5%] Built target itkopenjpeg
<br>> [ 6%] Built target itksys<br>> [ 7%] Built target ITKMetaIO<br>> [ 9%] Built target ITKNrrdIO<br>> [ 9%] Built target ITKEXPAT<br>> [ 9%] Building CXX object<br>> Utilities/DICOMParser/CMakeFiles/ITKDICOMParser.dir/DICOMFile.o
<br>> /usr/local/InsightToolkit-3.2.0/Utilities/DICOMParser/DICOMFile.h:51: error:<br>> expected unqualified-id before '&' token<br>> /usr/local/InsightToolkit-3.2.0/Utilities/DICOMParser/DICOMFile.h:51: error:
<br>> expected ',' or '...' before '&' token<br><br>as a first test, I'd try commenting out the #ifdefs in DICOMConfig.h:42<br><br>#ifdef DICOM_NO_STD_NAMESPACE<br> #define dicom_stl<br>
#else<br> #define dicom_stl std<br>#endif<br><br>to just "#define dicom_stl std".<br><br>I've no idea what the alternative relates to.<br><br><br>richard<br><br>> /usr/local/InsightToolkit-3.2.0/Utilities/DICOMParser/DICOMFile.h:51: error:
<br>> ISO C++ forbids declaration of 'parameter' with no type<br>> /usr/local/InsightToolkit-3.2.0/Utilities/DICOMParser/DICOMFile.cxx:61:<br>> error: expected unqualified-id before '&' token<br>
> /usr/local/InsightToolkit-3.2.0/Utilities/DICOMParser/DICOMFile.cxx:61:<br>> error: expected ',' or '...' before '&' token<br>> /usr/local/InsightToolkit-3.2.0/Utilities/DICOMParser/DICOMFile.cxx:61:
<br>> error: ISO C++ forbids declaration of 'parameter' with no type<br>> /usr/local/InsightToolkit-3.2.0/Utilities/DICOMParser/DICOMFile.cxx: In<br>> member function 'bool itkdicomparser::DICOMFile::Open(int)':
<br>> /usr/local/InsightToolkit-3.2.0/Utilities/DICOMParser/DICOMFile.cxx:66:<br>> error: 'filename' was not declared in this scope<br>> make[2]: ***<br>> [Utilities/DICOMParser/CMakeFiles/ITKDICOMParser.dir/DICOMFile.o] Error 1
<br>> make[1]: *** [Utilities/DICOMParser/CMakeFiles/ITKDICOMParser.dir/all] Error<br>> 2<br>> make: *** [all] Error 2<br>><br>> This was the latest release version of the ITK from Sourceforge. Any<br>> suggestions?
<br>><br>> Thanks for any help,<br>> - Dan<br>><br></blockquote></div><br>