Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Jun 2000 14:10:58 -0700
From:      Kent Stewart <kstewart@3-cities.com>
To:        Lars <Lars@lawnet.xs4all.nl>
Cc:        "'freebsd-stable@Freebsd.org'" <freebsd-stable@Freebsd.org>
Subject:   Re: Desperate : make buildworld NEVER works!!!!!
Message-ID:  <394D3AE2.D3896F73@3-cities.com>
References:  <C1A84F04B2ACD211B7A152544C0072CD2601@lawwnt01.lawnet.xs4all.nl>

next in thread | previous in thread | raw e-mail | index | archive | help


Lars wrote:
> 
> Hello all,
> 
> for over a month or so, I've been trying to upgrade a machine from 3.3-R to
> 3-Stable.
> On the same machine I've also tried to upgrade from 4-R to 4-Stable.
> The problem I have is that 'make buildworld' NEVER ends succesfully. It
> ALWAYs stops
> with a an '*** ERROR 1'.
> 
> The procedure I follow is like this :
> - Install fresh copy of 3.3-R (or 4-R) on machine from cd.
> - I always install a minimal installation with man pages, ports collection
> and ALL the sources
> - upgrade source with cvsup. The cvsup file I use looks like (here for 3.3-R
> -> 3-Stable):
>   *default host=cvsup.internat.freebsd.org
>   *default base=/usr
>   *default prefix=/usr
>   *default release=cvs
>   *default delete use-rel-suffix
>   src-all tag=RELENG_3
> - drop to single usermode with 'shutdown now'
> - # fsck -p
> - # mount -u /
> - # mount -a -t ufs
> - # swapon -a
> - # cd /usr/obj
> - # chflags -R noschg *
> - # rm -rf *
> - # cd /usr/src
> - # script /var/tmp/bw000618a.out
> - # make buildworld
> 
> I follow the guidelines from the Handbook, as you can see.
> 
> Here are two outputs (the last part) of the 'make buildworld' command from
> this morning trying upgrading 4-R to 4-Stable .
> The cvsup server I used was cvsup.internat.freebsd.org
> 
> 1)
> 
<snip>
> cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/libopcodes
> -I/usr/src/gnu/usr.bin/binutils/libopcodes/../libbfd/i386
> -I/usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/incl
> ude -DARCH_i386
> -I/usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/opco
> des
> -I/usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/bfd
> -I/usr/obj/usr/src/i386/usr/include -c
> /usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/opcode
> s/i386-dis.c -o i386-dis.o
> {standard input}: cc: Assembler messages:
> Internal compiler error: program cc1 got fatal signal 11{standard
> input}:2930:

This is the real error message, i.e., a signal 11 exit.

Signal 11's during a build are almost always hardware related and
typically bad memory.

I cvsup'ed 4.0-Stable at 1145 PDT (1845 GMT) and I have a build
running right now. I still think it is hardware on your end. I'll let
the list know if it fails. It will take about an hour.

Kent

> Warning: *** Error code 1
> end of file not at end of a line; newline inserted
> 
<snip>
-- 
Kent Stewart
Richland, WA

mailto:kstewart@3-cities.com
http://www.3-cities.com/~kstewart/index.html
http://daily.daemonnews.org/

SETI (Search for Extraterrestrial Intelligence) @ Home
http://setiathome.ssl.berkeley.edu/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?394D3AE2.D3896F73>