Re: editors/openoffice-1.1: random g++ "internal compiler error"

From: Craig Rodrigues <rodrigc_at_crodrigues.org>
Date: Sat, 29 Nov 2003 21:03:44 -0500
On Sun, Nov 30, 2003 at 04:19:27AM +0600, Mikhail Manuilov wrote:
> vcl/settings.hxx:1165: internal compiler error: Segmentation   fault
> Please submit a full bug report, with preprocessed source if appropriate.
> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> dmake:  Error code 1, while making '../../unxfbsd.pro/slo/
> actiontriggerhelper.obj'
> ---* TG_SLO.MK *---

> 
> It appears to be randomly, but does it will help to cvsup and buildworld?
> I really hate that script =):
> 
> #!/bin/sh
> make build;
> while [ $? -ne 0 ];
> do
>         make build;
> done;
> 
> # c++ -v
> Using built-in specs.
> Configured with: FreeBSD/i386 system compiler
> Thread model: posix
> gcc version 3.3.3 [FreeBSD] 20031106
> 
> Bit of uname output:
> FreeBSD 5.1-CURRENT #0: Mon Nov 17 23:29:49 OMST 2003
> I've built with that ( not exactly - but 14-15 Nov build world - there was 
> panic with ntfs copy ) system XFree86+kde3.14 from sources


Hi,

I managed to successfully build the OpenOffice 1.1 port
(it took a LONG time, and a lot of disk space).

FreeBSD 5.1-CURRENT FreeBSD 5.1-CURRENT #21: Sat Nov 15 23:40:30 EST 2003

Using built-in specs.
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 3.3.3 [FreeBSD] 20031106

Sometimes when gcc crashes unpredictably, this is an
indication of some hardware problems: i.e. faulty memory,
faulty disk, CPU may not be cooled properly, etc.

I recommend that you just use your script to "make build"
in a loop, so that the build will resume in case of a failure.

-- 
Craig Rodrigues        
http://crodrigues.org
rodrigc_at_crodrigues.org
Received on Sat Nov 29 2003 - 17:01:38 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:31 UTC