From owner-freebsd-ports@FreeBSD.ORG Mon Mar 3 17:26:15 2014 Return-Path: Delivered-To: freebsd-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 97347B5D for ; Mon, 3 Mar 2014 17:26:15 +0000 (UTC) Received: from wilberforce.math.missouri.edu (wilberforce.math.missouri.edu [128.206.184.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5E9951BD for ; Mon, 3 Mar 2014 17:26:14 +0000 (UTC) Received: from [128.206.184.213] (wilberforce.math.missouri.edu [128.206.184.213]) by wilberforce.math.missouri.edu (8.14.7/8.14.7) with ESMTP id s23HQ8dx042485 for ; Mon, 3 Mar 2014 11:26:08 -0600 (CST) (envelope-from stephen@missouri.edu) Message-ID: <5314BB30.7050801@missouri.edu> Date: Mon, 03 Mar 2014 11:26:08 -0600 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: sage-6.1.1 build errors out while building conway_polynomials References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Mar 2014 17:26:15 -0000 On 03/03/14 11:33, Saifi Khan wrote: > Hi: > > on attempting to build sage-6.1.1 from the '/usr/ports/math/sage' port, > the build errors out while building a subpackage 'conway_polynomials'. Most people have reported errors in scipy and matplotlib with FreeBSD-10. I think the build of conway-polynomials comes earlier. So if we had a work around for this, you would still be stuck later on with the build of scipy or matplotlib. I am somewhat convinced that the error is due to some kind of incompatibility between clang and gcc46 and the linking process. I have no idea how to fix these problems. I'm kind of hoping that it will get magically fixed one day.