Hi Andreas, Sorry, it seems your email got lost in my inbox.
On 15:33 08/09, Andreas Tille wrote: > Hi, > > I do also have access to some larger Jessie machine but here the build > failed quite quickly: > > ... > -- Configuring tests/cuda > CMake Error at util/cmake/SeqAnBuildSystem.cmake:395 (cmake_parse_arguments): > Unknown CMake command "cmake_parse_arguments". > Call Stack (most recent call first): > tests/cuda/CMakeLists.txt:26 (seqan_setup_cuda_vars) > > > -- Configuring incomplete, errors occurred! > See also > "/tmp/buildd/seqan-2.0.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log". > dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None returned exit code 1 > debian/rules:19: recipe for target 'build' failed > ... > > > As far as I understand > > manual/source/BuildManual/UsingFindSeqAnCMakeModule.rst > > and > > util/cmake/SeqAnBuildSystem.cmake > > SEQAN_HAS_CUDA should be autodetected. > > Any idea? > I'm re-building this in pbuilder, and will keep you posted. On a separate note, what do you think of the idea of having a different binary package for each of the seqan applications, as opposed to one big seqan-apps. Cheers, K --- Kevin Murray GPG pubkey: http://www.kdmurray.id.au/static/A4B4EE6A.asc FPR: 656C 0632 1EAB 2C3F 3837 9767 17C2 8EB1 A4B4 EE6A
