From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-1.7 required=5.0 tests=DMARC_MISSING, MAILING_LIST_MULTI,NICE_REPLY_A,RDNS_DYNAMIC autolearn=unavailable autolearn_force=no version=4.0.0 Received: from mail.broadpark.no (217-13-4-9.dd.nextgentel.com [217.13.4.9]) by chiba.3jane.net (Postfix) with ESMTP id D5804ABB60 for ; Thu, 26 Sep 2002 06:03:20 -0500 (CDT) Received: from gonzales (98.80-202-111.nextgentel.com [80.202.111.98]) by mail.broadpark.no (Postfix) with ESMTP id B214980E4 for ; Thu, 26 Sep 2002 13:02:56 +0200 (MEST) Content-Type: text/plain; charset="iso-8859-1" From: Dag Viggo =?iso-8859-1?q?Lok=F8en?= Organization: friByte To: gentoo-dev@gentoo.org Subject: Re: Fw: Re: [gentoo-dev] 1.4_rc1 bootstrap problem Date: Thu, 26 Sep 2002 13:02:56 +0200 User-Agent: KMail/1.4.3 References: <20020926081210.4845f477.mikko.moilanen@ty.mikkeliamk.fi> In-Reply-To: <20020926081210.4845f477.mikko.moilanen@ty.mikkeliamk.fi> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200209261302.56159.dag.viggo@lokoen.org> Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 2f7d4c35-865e-4ca7-8b77-3594cea9dc49 X-Archives-Hash: a3daa6d3fc75fb95a4bdd4359bf75efa On Thursday 26 September 2002 07:12, Mikko Moilanen wrote: > Begin forwarded message: > > Date: Thu, 26 Sep 2002 08:10:54 +0300 > From: Mikko Moilanen > To: fred > Subject: Re: [gentoo-dev] 1.4_rc1 bootstrap problem > > > On Wed, 25 Sep 2002 11:55:35 -0700 > > fred wrote: > > >On Wed, 25 Sep 2002 15:25:16 +0200 > > > > > >Dag Viggo Lok=F8en wrote: > > >> Somewhere during the execution og the scripts/bootstrap.sh script,= ld > > >> segfaults. > > > > Is it really a segfualt (ie memory access error) or is it some other > > error sych as invalid opcode? If its an invalid opcode then the > > problem would probibly be an incorrently configured make.conf file. > > Yes it is. I have tried also with default use flags and standard -O2 > optimizations. > This latest error i had, was not an segfault but a terminated with signal= 15,=20 core dumped. If i remember correctly, the segfault cam when i tried with = some=20 heavier optimizations (-march=3Dk6 -O3 -pipe -fomit-frame-pointer -fforce= -addr=20 -frerun-cse-after-loop -frerun-loop-opt) --=20 Mvh. Dag Viggo Lok=F8en