Hi, On Wed, 5 Feb 2014 14:03:00 +0100, Andreas Tille <andreas@an3as.eu> wrote: > > One solution is to build with no optimisations (-O0 instead of -O2, > > perhaps using noopt); that allows seqan to build on my i386 buildd. I > > didn't try with -O1. > > Any volunteer to test > > $ svn diff > Index: rules > =================================================================== > --- rules (Revision 15979) > +++ rules (Arbeitskopie) > @@ -7,6 +7,11 @@ > export CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS | sed > 's/-fstack-protector *//') > 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 > > %: > dh $@ > > > I do not have any properly sized i386 at hand and I would like to avoid > hammering the porter machines hard with this build which takes >2h on my > amd64 where I made sure no other process will consume some memory. With -O1 the build requires 2.5GB of memory on i386. It builds fine but obviously might take a (very) long time on buildds with less RAM. -O0 only needs 1GB. If you can target the change more specifically, only pair_align.cpp needs the work-around - everything else builds with far less memory. Regards, Stephen
Attachment:
signature.asc
Description: PGP signature