From owner-freebsd-python@FreeBSD.ORG Mon Feb 24 11:16:25 2014 Return-Path: Delivered-To: python@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 B27127F8 for ; Mon, 24 Feb 2014 11:16:25 +0000 (UTC) Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2DA6D1858 for ; Mon, 24 Feb 2014 11:16:24 +0000 (UTC) Received: by mail-la0-f49.google.com with SMTP id mc6so1980204lab.36 for ; Mon, 24 Feb 2014 03:16:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+LbCa6JT3KqBelZ88DTQ4dE4f0A4t3kN3frzZE4mBMY=; b=Lpx3nhSZ5f8aTJS9GYFCdZ1TnF/awPPc5NlRFnRQtUtMN7on4Qs2p9h+DSViw2PHls IUkuYfeIHIz8UBtVaq3/pa46/elIR3r77T/wq8rirNNKE1NW39S1ch2dI0cQG4lB9L5v spr1NPPdx37g8ioOsfoA57pdQPcZiqlqAq/DQGfXOlbxPz6hpskzIfcKMZAZQ2y+DCNX Gg6MOk561QB5lEtBYmjKAHcdVDS1oX3yt4CZ9W+xVGzjQjBbeiR/QyfmCcaDVYnT0H3U cFNRiYhnzmi8PTo6QSfgP+5VyDanstzN4ZCzSCXPOaJlhidF+m2aJoHyLTXznzWkrh2b dOXg== X-Received: by 10.112.142.40 with SMTP id rt8mr11258058lbb.52.1393240583269; Mon, 24 Feb 2014 03:16:23 -0800 (PST) Received: from 95.108.174.208-red.dhcp.yndx.net (95.108.174.208-red.dhcp.yndx.net. [95.108.174.208]) by mx.google.com with ESMTPSA id zf7sm10860093lab.7.2014.02.24.03.16.21 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Feb 2014 03:16:21 -0800 (PST) Sender: Dmitry Sivachenko Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: python packages struggling with GCC 4.7 From: Dmitry Sivachenko In-Reply-To: Date: Mon, 24 Feb 2014 15:16:19 +0400 Content-Transfer-Encoding: quoted-printable Message-Id: <89EE25AC-F3B6-4994-9A04-DE5BB438D755@FreeBSD.org> References: <201311060508.rA658XmR012155@svn.freebsd.org> <20131106063906.GA1385@medusa.sysfault.org> <20131106070255.GE60770@FreeBSD.org> To: Gerald Pfeifer X-Mailer: Apple Mail (2.1827) Cc: William Grzybowski , python@freebsd.org X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Feb 2014 11:16:25 -0000 On 23 =D1=84=D0=B5=D0=B2=D1=80. 2014 =D0=B3., at 9:48, Gerald Pfeifer = wrote: > On Thu, 5 Dec 2013, Gerald Pfeifer wrote: >> On Wed, 4 Dec 2013, William Grzybowski wrote: >>> It looks like the build is not respecting FFLAGS, so no -Wl,rpath=3D = for=20 >>> gfortran. As far as it working for gcc46, it looks like it fails to=20= >>> detect gfortran46 as a compiler and uses gcc46, which respects = CFLAGS. >>=20 >> That is, hmm, interesting. =3D:-) Nice analysis. >>=20 >>> Can you try http://people.freebsd.org/~wg/py-numpy.patch ? >>=20 >> Thanks for the patch! =20 >>=20 >> Is there any chance that someone on python@ can give it a try? That=20= >> would be great since I am traveling right now and hardly can test. >=20 > No takers? :-) With some unplanned offline-ness on my side, this > has now taken far longer than I had hoped for, but I managed to test > this patch now (reproducing both the original failure and then a build > without) -- and this patch, once I got it to apply, works! >=20 > Thanks a lot. >=20 > Shall I go ahead and commit it, or would you prefer to? I just committed the patch, thanks for all involved. Looking forward for final transition to gcc-4.7 in USE_GCC. :)=