From owner-freebsd-current@FreeBSD.ORG Mon Apr 30 11:44:19 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DC5441065672 for ; Mon, 30 Apr 2012 11:44:19 +0000 (UTC) (envelope-from jean-sebastien.pedron@dumbbell.fr) Received: from mail.made4.biz (unknown [IPv6:2001:41d0:1:7018::1:3]) by mx1.freebsd.org (Postfix) with ESMTP id 9772F8FC12 for ; Mon, 30 Apr 2012 11:44:19 +0000 (UTC) Received: from [2a01:e35:8b50:830:290:f5ff:fe9d:b78c] (helo=magellan.dumbbell.fr) by mail.made4.biz with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1SOp1d-000Kx2-SD for freebsd-current@freebsd.org; Mon, 30 Apr 2012 13:44:18 +0200 Message-ID: <4F9E7B11.3060901@dumbbell.fr> Date: Mon, 30 Apr 2012 13:44:17 +0200 From: =?ISO-8859-15?Q?Jean-S=E9bastien_P=E9dron?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120426 Thunderbird/12.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4F9D1DF8.20001@zedat.fu-berlin.de> <4F9D317D.40609@FreeBSD.org> <4F9E2D20.4010300@zedat.fu-berlin.de> In-Reply-To: <4F9E2D20.4010300@zedat.fu-berlin.de> X-Enigmail-Version: 1.4 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Subject: Re: lang/gcc46: error when compiling with CLANG X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2012 11:44:19 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 30.04.2012 08:11, O. Hartmann wrote: > Repeating the build ends up at the same "stage" as it stopped when > building on regular basis - for my understanding. You say you have two boxes running 10-CURRENT: do they run the same SVN revision? A recent change (r234585, 2012-04-22) in libc causes several softwares to segfault if the libc is built with clang. I just committed to HEAD (r234836) a patch that fixes this. Maybe it's related to your problem, you may want to try it. - -- Jean-Sébastien Pédron -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+eexEACgkQa+xGJsFYOlNvQgCgmOVXZiH5zv5T+RdVL25rdome +zAAoLR/deC5HhWwZgNi/8yK8wcYJ0AS =RUSU -----END PGP SIGNATURE-----