From owner-freebsd-current@FreeBSD.ORG Mon Sep 19 19:30:14 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8204A16A41F for ; Mon, 19 Sep 2005 19:30:14 +0000 (GMT) (envelope-from minimarmot@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id F237143D48 for ; Mon, 19 Sep 2005 19:30:13 +0000 (GMT) (envelope-from minimarmot@gmail.com) Received: by xproxy.gmail.com with SMTP id i27so124064wxd for ; Mon, 19 Sep 2005 12:30:13 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=mGNzWTA/qh6e/kc5o5PBFzXWTKRN2CFw2HfYMKclkq+Xnzbz102Gsr7jEvkETtrDSNOIiRvy5Fpfl55zvtfRT2QgxaRBbbS+idmtKdgrKxTNPXN4EjwMwG44yze1+XLLE/2kNRLQCZhCWnIXew3qlVOgdbFUl7TLXel+GF4ATCo= Received: by 10.70.16.17 with SMTP id 17mr1509604wxp; Mon, 19 Sep 2005 12:30:13 -0700 (PDT) Received: by 10.70.9.2 with HTTP; Mon, 19 Sep 2005 12:30:13 -0700 (PDT) Message-ID: <47d0403c0509191230394d1473@mail.gmail.com> Date: Mon, 19 Sep 2005 19:30:13 +0000 From: Ben Kaduk To: bob self In-Reply-To: <432EC9DB.2040808@charter.net> Mime-Version: 1.0 References: <432EC9DB.2040808@charter.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: make buildworld causes "internal compiler error" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: minimarmot@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2005 19:30:14 -0000 On 9/19/05, bob self wrote: >=20 >=20 > Why might this be happening???? I updated all the ports from source > yesterday. That worked fine. Now I'm trying to go to beta 5 but after a > long time > compiling I get this message. I'm now running 6.0 beta 4 and as far as I > know there are no problems except this. >=20 > Bob >=20 >=20 >=20 >=20 > c++ -O2 -fno-strict-aliasing -pipe -DIN_GLIBCPP_V3 -DHAVE_CONFIG_H > -I/usr/src/gnu/lib/libstdc++ -I/usr/src/gnu/lib/libstdc++/../ > ../../contrib/libstdc++/libsupc++ > -I/usr/src/gnu/lib/libstdc++/../../../contrib/gcc > -I/usr/src/gnu/lib/libstdc++/../../../contri > b/libstdc++/include -frandom-seed=3DRepeatabilityConsideredGood > -fno-implicit-templates -ffunction-sections -fdata-sections -Wno- > deprecated -c > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/io-inst.cc > In file included from /usr/obj/usr/src/tmp/usr/include/c++/3.4/string:57, > from >=20 > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include/bits/locale= _classes.h:47, > from >=20 > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include/bits/ios_ba= se.h:47, > from /usr/obj/usr/src/tmp/usr/include/c++/3.4/ios:49, > from > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/io-inst.cc:35: >=20 > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include/bits/basic_= string.tcc:236: > internal compiler error: Segmentation f > ault: 11 > Please submit a full bug report, > with preprocessed source if appropriate. > See for instructions. > *** Error code 1 >=20 > Stop in /usr/src/gnu/lib/libstdc++. > *** Error code 1 >=20 > Stop in /usr/src/gnu/lib. > *** Error code 1 >=20 > Stop in /usr/src. > *** Error code 1 >=20 > Stop in /usr/src. > *** Error code 1 >=20 > Stop in /usr/src. > *** Error code 1 >=20 > Stop in /usr/src. >=20 >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " I have heard many times on this list that such "internal compiler errors"= =20 are usually caused by bad hardware -- have you checked your memory? Ben Kaduk