Bug#739697: src:dolfin: FTBFS on armhf and mips: virtual memory exhausted: Cannot allocate memory
On Mon, Feb 24, 2014 at 12:35 AM, peter green plugw...@p10link.net wrote: peter green wrote: I've been doing some tests on this interestingly it failed for me much earlier than on the buildd, maybe different systems give slightly different ammounts of usable address space or something. Anyway reducing optimisation levels etc doesn't seem to help, switching to 4.7 is looking more promising. 4.7 also ran into memory exhaustion problems (though later in the build than 4.8 did), 4.6 was able to build it successfully on armhf. Still need to test it on mips. Thanks for testing. I think the simplest solution would be to disable CGAL on armhf and mips. CGAL support in DOLFIN is planned to be removed anyway. I was going to do an upload now, but ran into this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739904 Hopefully, this will be fixed soon. Johannes -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739697: src:dolfin: FTBFS on armhf and mips: virtual memory exhausted: Cannot allocate memory
peter green wrote: I've been doing some tests on this interestingly it failed for me much earlier than on the buildd, maybe different systems give slightly different ammounts of usable address space or something. Anyway reducing optimisation levels etc doesn't seem to help, switching to 4.7 is looking more promising. 4.7 also ran into memory exhaustion problems (though later in the build than 4.8 did), 4.6 was able to build it successfully on armhf. Still need to test it on mips. I also ran into an issue with boost which I had to add a workarround for. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739697: src:dolfin: FTBFS on armhf and mips: virtual memory exhausted: Cannot allocate memory
I've been doing some tests on this interestingly it failed for me much earlier than on the buildd, maybe different systems give slightly different ammounts of usable address space or something. Anyway reducing optimisation levels etc doesn't seem to help, switching to 4.7 is looking more promising. I'll follow up when i've done further tests. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739697: src:dolfin: FTBFS on armhf and mips: virtual memory exhausted: Cannot allocate memory
Package: src:dolfin Version: 1.3.0+dfsg-1 Severity: serious Dear Maintainer, dolfin currently FTBFS on armhf and mips: [ 70%] Building CXX object dolfin/CMakeFiles/dolfin.dir/generation/PolyhedralMeshGenerator.cpp.o cd /«BUILDDIR»/dolfin-1.3.0+dfsg/debian/build-python2.7/dolfin /usr/bin/c++ -DBOOST_UBLAS_NDEBUG -DDOLFIN_GIT_COMMIT_HASH=\unknown\ -DDOLFIN_VERSION=\1.3.0\ -DHAS_CGAL -DHAS_CHOLMOD -DHAS_HDF5 -DHAS_MPI -DHAS_OPENMP -DHAS_PETSC -DHAS_QT4 -DHAS_QVTK -DHAS_SCOTCH -DHAS_SLEPC -DHAS_UMFPACK -DHAS_VTK -DHAS_ZLIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -D_BSD_SOURCE -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2 -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -Ddolfin_EXPORTS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wno-deprecated -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -frounding-math -fopenmp -O2 -g -DNDEBUG -fPIC -isystem /usr/include/qt4 -isystem /usr/include/qt4/QtGui -isystem /usr/include/qt4/QtCore -isystem /usr/include/vtk-5.8 -I/«BUILDDIR»/dolfin-1.3.0+dfsg -I/usr/include/libxml2 -I/usr/lib/slepcdir/3.4.2 -I/usr/lib/slepcdir/3.4.2/linux-gnueabihf-c-opt/include -I/usr/lib/slepcdir/3.4.2/include -isystem /usr/include/suitesparse -isystem /usr/include/scotch -isystem /usr/lib/openmpi/include -isystem /usr/lib/openmpi/include/openmpi -isystem /usr/include/eigen3 -isystem /usr/lib/petscdir/3.4.2/include -isystem /usr/lib/petscdir/3.4.2/linux-gnueabihf-c-opt/include-o CMakeFiles/dolfin.dir/generation/PolyhedralMeshGenerator.cpp.o -c /«BUILDDIR»/dolfin-1.3.0+dfsg/dolfin/generation/PolyhedralMeshGenerator.cpp virtual memory exhausted: Cannot allocate memory Apparently the C++ compiler cannot deal with that source file within reasonable memory bounds. There are various possible solutions among which: simplifying the source file, deactivating the corresponding functionality on those archs, trying another compiler or compiler version, removing dolfin from those archs… Cheers, -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http://www.dynare.org/sebastien `- GPG Key: 4096R/381A7594 signature.asc Description: Digital signature
