Bug#726009: Insufficient RAM on build-machines (was Bug#726009: yade: FTBFS on i386 (and others))

[Anton Gladky]

Thanks all, guys, for recommendations and explanations. I will try to
split some large cpp-files as Dmitrijs mentioned (there are a couple of
them, which are failing reliably on weak archs), remove some
optimization options as Mathieu advised and we will see, whether it helps.

I would also try to build Yade with clang on failing archs, if upper
mentioned actions will not help to solve the problem. Though
openmp-parallelisation will be disabled in this case, ant it is not very
convenient.

Thanks again,

Anton

On 10/12/2013 02:34 PM, Mathieu Malaterre wrote:
> Anton,
> 
> On Fri, Oct 11, 2013 at 9:00 PM, Anton Gladky <gladk at debian.org> wrote:
> [...]
>>> /usr/bin/c++   -Dyade_EXPORTS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2  -DYADE_PTR_CAST=static_pointer_cast -DYADE_CAST=static_cast -fPIC -DYADE_VTK -DYADE_OPENMP -fopenmp -DYADE_GTS  -DQGLVIEWER_FOUND -DYADE_OPENGL -frounding-math -DYADE_CGAL -DFLOW_ENGINE -frounding-math -DLINSOLV -DFLOW_ENGINE -DYADE_GL2PS -O3 -DNDEBUG -fPIC -
> 
> You are using cmake in Release mode, which is bad IMHO. So having -O2
> and -O3 (in that order) compiles code in -O3, which is way too much
> AFAIK.
> 
> Ref:
> http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html
> ...
> If you use multiple -O options, with or without level numbers, the
> last such option is the one that is effective.
> ...
> 
> See also here why CMAKE_BUILD_TYPE should be required to be set to "" on debian:
> http://bugs.debian.org/701231#12
> 
> 2cts


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20131012/cc1f4f62/attachment.sig>