On Tue, Apr 30, 2002 at 11:28:48AM +0200, Jose M. Alcaide wrote:
> cpp0: cc: output pipe has been closedInternal compiler error: program cc1 got fatal
>signal 10
>
> This cc1 SIGBUS is triggered by different source files at different times.
> But it happens while building XFree86-Server sooner o
> From: "Jose M. Alcaide" <[EMAIL PROTECTED]>
> Date: Tue, 30 Apr 2002 11:28:48 +0200
> To: [EMAIL PROTECTED]
> Subject: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
>
> I am getting this error while building XFree86-Server-4.2.0_2 on a
> recently updated -CURRENT (Mon Apr 29 1
I've experienced this same problem today; but only after installing
5.0-current on the system in question. It compiled fine with FreeBSD_4.5.
This is a 1.2ghz Pentium with 1gb of RAM. No problems with other things
(large compile projects with 4.5 before).
_F
> From: "Jose M. Alcaide"
Found that cc1 also has a problem with this on a buildworld for
FreeBSD-5.0-CURRENT. FYI.
I can reinstall 4.5 and attempt the same, but I recall no problems with 4.5.
_F
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To follow up on my previous post: I did reinstall FreeBSD-4.5 (updated
with cvsup), did a buildworld etc., then build XFree86-4 with no troubles
at all.
So looks like the problem may be with FreeBSD-5.0-CURRENT.
_F
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
On Tue, Apr 30, 2002 at 06:24:14PM -0400, Forrest Aldrich wrote:
> I've experienced this same problem today; but only after installing
> 5.0-current on the system in question. It compiled fine with FreeBSD_4.5.
>
> This is a 1.2ghz Pentium with 1gb of RAM. No problems with other things
> (la
< said:
> I have been building XFree86 without problems,
I just rebuilt both -current (Friday or Saturday timeframe) and all of
X (last night) without a problem. (Well, other than all of the old
binaries I need to recompile now...)
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
wi
On Tue, 2002-04-30 at 10:35, Ian wrote:
>
> > cpp0: cc: output pipe has been closedInternal compiler error: program cc1 got
> > fatal signal 10
> >
>
> I have seen cc1 die like this many many times, and have only ever seen 2
> root causes for the death:
>
> 1) bad ram
> 2) you overclocked th
Fluid <[EMAIL PROTECTED]> wrote:
> How about signal 4? I was rebuilding my -current the other day and I
> kept getting mostly signal 4 errors (in different places) with a couple
> of signal 10's and 11's. I tried finding a run-down of what the various
> errors meant, but I couldn't find a thing
