<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello Robbins,<div><br></div><div>That is extremely helpful that you are submitting a nightly dashboard with the configuration you are using!</div><div><br></div><div>I see you have the following:</div><div><br></div><div><span class="Apple-style-span" style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px; "><pre> set( dashboard_cache "
CMAKE_VERBOSE_MAKEFILE:BOOL=ON
BUILD_EXAMPLES:BOOL=ON
BUILD_SHARED_LIBS:BOOL=ON
BUILD_TESTING:BOOL=ON
BUILD_DOXYGEN:BOOL=OFF
CMAKE_SKIP_RPATH:BOOL=OFF
ITK_USE_SYSTEM_GDCM:BOOL=ON
ITK_USE_SYSTEM_JPEG:BOOL=ON
ITK_USE_SYSTEM_PNG:BOOL=ON
ITK_USE_SYSTEM_TIFF:BOOL=OFF
ITK_USE_SYSTEM_ZLIB:BOOL=ON
ITK_USE_SYSTEM_VXL:BOOL=OFF
USE_FFTWD:BOOL=ON
USE_FFTWF:BOOL=ON
ITK_USE_CONCEPT_CHECKING:BOOL=ON
ITK_USE_STRICT_CONCEPT_CHECKING:BOOL=ON
"
)</pre></span><div>Looking at the dash board we have other system which are using gcc 4.7. But most of our nightly builds use ITK libraries in stead of system ones. So I am suspicion of ITK's compatibilities with your systems libraries. </div></div><div><br></div><div>When you don't use any system libraries are there may test failures? My first suspicion would be a ZLIB library incompatibility then TIFF... but we should see how the build on your system is with out any system libraries is first.</div><div><br></div><div>Brad</div><div><br></div><div><br></div><div><br><div><div>On Jun 5, 2012, at 10:28 PM, Steve M. Robbins wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi,<br><br>Thanks all. Yes, I downloaded using git (I thought that was the<br>only option at this point).<br><br><br>On Tue, Jun 05, 2012 at 09:15:40AM -0400, Bradley Lowekamp wrote:<br><br><br><blockquote type="cite">There are many configuration options available. I will assume that you are just trying to build ITK with the default options, if you are trying to build WrapITK let us know as the advice will change a little.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">In the default configuration testing and examples are enabled. This adds a dependency to download data. So this should be disabled if network access needs to be avoided. While I don't think it has been done yet, it should be possible to create a second tar ball of the data, and that will either need to be extracted into a specific location in the source code, or an environment variable will need to be specified to it's path.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Turning on FFTW ( off by default ), will automatically download the source code and compile if that option is turned on, and a system library is not specified.<br></blockquote><blockquote type="cite"><br></blockquote><br>I have enabled testing and examples and FFTW, so that is what I saw<br>downloading. Since Matt says the release tarballs will contain the data,<br>that won't be a problem. <br><br>I'd like to use the system FFTW, but last time I tried there were<br>segfaults [1]. That was with 4.1.0; I should try again. If it turns<br>out we need to use embedded FFTW, it would be convenient if I could<br>run "make download-all", then regenerate a tar ball with everything<br>included.<br><br>[1] <a href="http://lists.debian.org/debian-med/2012/04/msg00064.html">http://lists.debian.org/debian-med/2012/04/msg00064.html</a><br><br><br>Incidentally, while the library builds, many of the tests fail<br>or segfault. This has been the case ever since Debian switched<br>to gcc 4.7 [2]. Anyone have success with this compiler?<br><br><br>[2] <a href="http://open.cdash.org/buildSummary.php?buildid=2260572">http://open.cdash.org/buildSummary.php?buildid=2260572</a><br><br><br>Thanks,<br>-Steve<br><br></div></blockquote></div><br></div></body></html>