From owner-freebsd-ports@FreeBSD.ORG Fri Sep 12 12:42:33 2014 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5CDE8F36; Fri, 12 Sep 2014 12:42:33 +0000 (UTC) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 37D1EB57; Fri, 12 Sep 2014 12:42:33 +0000 (UTC) Received: from [192.168.0.132] (vie-188-118-244-060.dsl.sil.at [188.118.244.60]) by ainaz.pair.com (Postfix) with ESMTPSA id 848903F478; Fri, 12 Sep 2014 08:42:31 -0400 (EDT) Date: Fri, 12 Sep 2014 14:42:29 +0200 (CEST) From: Gerald Pfeifer To: Andrey Chernov Subject: Re: Can't build lang/gcc port on i386: segmentation fault In-Reply-To: <5412E64E.7050701@freebsd.org> Message-ID: References: <5412D743.70005@freebsd.org> <5412E4A1.7040101@freebsd.org> <5412E64E.7050701@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: ports@FreeBSD.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2014 12:42:33 -0000 On Fri, 12 Sep 2014, Andrey Chernov wrote: >> As I just found, it builds with BOOTSTRAP nice, so apparently clang >> makes some damage. You can see CFLAGS in the log. Swap is 4GB I think it >> is large enough. Nothing special otherwise. > BTW, previous 4.7* as lang/gcc build fine even without BOOTSTRAP. I am curious, what happens when you try lang/gcc48? My expectation would be both lang/gcc and lang/gcc48 to behave the same, since it's a very similar codebase, gcc48 just a bit newer on the same branch. We could make BOOTSTRAP the default for lang/gcc, though not doing that and thus building a lot faster has been one of the features of lang/gcc. -- Since it does not reproduce for me, do others see the same failure? Gerald