Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


On Sun, Jul 15, 2012 at 3:45 PM, Albert Thuswaldner
<albert.thuswaldner@gmail.com> wrote:
On Fri, Jul 13, 2012 at 1:41 AM, Rafael Dominguez <venccsralph@gmail.com> wrote:
After the update to libmspub-0.0.1 a day ago, my gcc terminates with
the error "running out of virtual memory" when compiling the
PolygonUtils.cpp file (i got 4GB ram),
im using gcc 4.4.5 in Gentoo Linux. My build parameters are

--enable-python=system --disable-epm --with-system-boost
--enable-crashdump --with-system-zlib --with-system-stdlibs
--with-system-openssl --with-system-db --with-system-curl
--with-system-cppunit --without-ppds --with-system-cairo
--with-junit=/home/ralph/Proyectos/junit-4.10.jar --enable-symbols
--enable-werror


Could it be possible because the file is too big???

Hmm, After upgrading master for the first time in a while, my build
fails at the same spot.

log for /home/thuswa/work/libo2/libmspub
Compiling: libmspub/unxlngi6.pro/misc/build/libmspub-0.0.1/src/lib/PolygonUtils.cpp
g++: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See <http://bugs.opensuse.org/> for instructions.
dmake:  Error code 1, while making
'../../../../../../unxlngi6.pro/slo/PolygonUtils.obj'
dmake:  Error code 255, while making './unxlngi6.pro/misc/build/so_built_mspub'

Does anyone know what's going on here?

Thanks!
/Albert

Its fixed now, pull latest master

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.