Hi KiBi,
On Mon, Mar 10, 2014 at 09:06:51PM +0100, Cyril Brulebois wrote:
> Source: seqan
> Version: 1.4.1-3
> Severity: serious
> Justification: FTBFS
>
> it seems your package is eating too much RAM for breakfast:
> | cd /«PKGBUILDDIR»/obj-arm-linux-gnueabihf/core/apps/pair_align &&
> /usr/bin/c++ -DSEQAN_ENABLE_TESTING=0 -DSEQAN_HAS_EXECINFO=1
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -g -O2 --param=ssp-buffer-size=4
> -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -W -Wall -Wno-long-long
> -fstrict-aliasing -Wstrict-aliasing -pedantic -Wno-variadic-macros
> -I/«PKGBUILDDIR»/core/include -o
> CMakeFiles/pair_align.dir/pair_align.cpp.o -c
> /«PKGBUILDDIR»/core/apps/pair_align/pair_align.cpp
> | virtual memory exhausted: Cannot allocate memory
> | make[4]: ***
> [core/apps/pair_align/CMakeFiles/pair_align.dir/pair_align.cpp.o] Error 1
>
> Only amd64, powerpc, and s390x builds are in the archive by now:
> https://buildd.debian.org/status/package.php?p=seqan&suite=sid
This is a known fact admitted by upstream. I even failed to build on
not so powerfully RAM equiped amd64 machines. The only solution I see
is to exclude all other architectures than the one you are mentioning
above.
It seems reducing optimisation in d/rules
DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
DEB_BUILD_ARCH_BITS := $(shell dpkg-architecture -qDEB_BUILD_ARCH_BITS)
ifeq ($(DEB_BUILD_ARCH_BITS),32)
CFLAGS=$(shell dpkg-buildflags --get CFLAGS | sed 's/-O[2-9]/-O1/')
CXXFLAGS=$(shell dpkg-buildflags --get CXXFLAGS | sed 's/-O[2-9]/-O1/')
endif
did not really help (perhaps even droping -O1 could be tried but I
doubt this).
Kind regards
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
