On Mon, Oct 27, 2014 at 10:02:43PM +0100, Dr.-Ing. Edgar Alwers wrote:
> First of all, this system asks for a very nice volume of RAM on the PC:
> my first compiling try ended with the error:
> quote
> -----------------
> ......
> [build CXX] sc/source/ui/docshell/docsh2.cxx
> g++: interner Compiler-Fehler: Getötet (Programm cc1plus)
> Bitte senden Sie einen vollständigen Fehlerbericht auf Englisch ein;
> bearbeiten Sie die Quellen zunächst mit einem Präprozessor, wenn es
> dienlich ist.
> Siehe <http://gcc.gnu.org/bugs.html> für nähere Anweisungen.
> /sources_BLFS/libreoffice-4.3.2.2/solenv/gbuild/LinkTarget.mk:183: recipe for 
> target 
> '/sources_BLFS/libreoffice-4.3.2.2/workdir/CxxObject/sc/source/ui/docshell/docfunc.o'
>  
> failed
> make[1]: *** 
> [/sources_BLFS/libreoffice-4.3.2.2/workdir/CxxObject/sc/source/ui/docshell/docfunc.o]
>  
> Error 4
> make[1]: *** Deleting file 
> '/sources_BLFS/libreoffice-4.3.2.2/workdir/CxxObject/sc/source/ui/docshell/docfunc.o'
> make[1]: *** Warte auf noch nicht beendete Prozesse...
> Makefile:224: recipe for target 'build' failed
> make: *** [build] Error 2
> ----------------
> unquote
> 
> Translation: internal compiler error: killed ( program cc1plus )
> Google said, this is due to a lack of RAM ( my box has 2 GB )
> 

 An ICE can also happen for other reasons.  Lack of memory is not the
only possible cause.  One of my machines (with 7.5GB) gets ICEs from
time to time.

> I got this error message after 4 hours of make !
> 

 With 4.3.1.2 on my netbook (1GB memory, 4GB swap) the first failure
came after 42 hours.  Thread started at
http://lists.linuxfromscratch.org/pipermail/blfs-dev/2014-October/028716.html
and on the second attempt it completed the build and install in a
little less than 42 hours.

 LO is well known as slow-to-build, and problems usually only show
up when you are a long way into the build.
> I fixed (?) this problem by adding 2 GB of swap partition, not building 
> anymore with -j2 ( I have two processors ) and using only a black console to 
> avoid unnecessary RAM load, I did not start KDE.
> 
> The result, after 6 hours of compilation ( !! )  was:
> quote
> -------------------
> ld LOC] libreoffice
> [build CUT] vcl_app_test
> DynamicLibraryManagerException: "Failed to load dynamic library: 
> /sources_BLFS/libreoffice-4.3.2.2/workdir/LinkTarget/CppunitTest/libtest_vcl_app_test.so
> libgraphite2.so.3: cannot open shared object file: No such file or directory"
> Path is 
> '.:/sources_BLFS/libreoffice-4.3.2.2/solenv/bin:/bin:/usr/local/bin:/bin:/usr/bin:/opt/kde/bin:/opt/qt4/bin:/usr/bin:/sbin:/usr/local/bin:/opt/bin:/usr/local/sbin:/usr/bin:/lib:/opt/qt/bin:/opt/qt4/bin:/opt/kde:/opt/kde/bin:/opt/jdk-7u3:/opt/jdk-7u3/bin'
> which: no gdb in 
> (.:/sources_BLFS/libreoffice-4.3.2.2/solenv/bin:/bin:/usr/local/bin:/bin:/usr/bin:/opt/kde/bin:/opt/qt4/bin:/usr/bin:/sbin:/usr/local/bin:/opt/bin:/usr/local/sbin:/usr/bin:/lib:/opt/qt/bin:/opt/qt4/bin:/opt/kde:/opt/kde/bin:/opt/jdk-7u3:/opt/jdk-7u3/bin)
> You need gdb in your path to show backtraces
> 
> Error: a unit test failed, please do one of:
> 
> export DEBUGCPPUNIT=TRUE            # for exception catching
> export CPPUNITTRACE="gdb --args"    # for interactive debugging on Linux
> export CPPUNITTRACE="\"[full path to devenv.exe]\" /debugexe" # for 
> interactive debugging in Visual Studio
> export VALGRIND=memcheck            # for memory checking
> 
> and retry using: make CppunitTest_vcl_app_test
> 
> /sources_BLFS/libreoffice-4.3.2.2/solenv/gbuild/CppunitTest.mk:70: recipe for 
> target 
> '/sources_BLFS/libreoffice-4.3.2.2/workdir/CppunitTest/vcl_app_test.test' 
> failed
> make[1]: *** 
> [/sources_BLFS/libreoffice-4.3.2.2/workdir/CppunitTest/vcl_app_test.test] 
> Error 1
> make[1]: *** Warte auf noch nicht beendete Prozesse...
> Makefile:224: recipe for target 'build' failed
> make: *** [build] Error 2
> -------------------
> unquote
> 

 I would suggest that you give it some MORE swap, and do not be
afraid to use -j2.  Using -j2 will certainly not halve the time, but
it will help a little.  Also, you might want to run 'top' in
whatever sort of term you are using (xterm or equivalent), to see what
is going on during the build.

ĸen
-- 
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to