From owner-freebsd-python@FreeBSD.ORG Thu Oct 24 00:09:13 2013 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 ESMTP id 10DBE5E5; Thu, 24 Oct 2013 00:09:13 +0000 (UTC) (envelope-from mike.jakubik@intertainservices.com) Received: from mail.intertainservices.com (mail.intertainservices.com [69.77.177.114]) by mx1.freebsd.org (Postfix) with ESMTP id D914F2A57; Thu, 24 Oct 2013 00:09:12 +0000 (UTC) Received: from freebsd.local (unknown [172.16.10.114]) by mail.intertainservices.com (Postfix) with ESMTPSA id BFA7A5643C; Wed, 23 Oct 2013 20:09:06 -0400 (EDT) Message-ID: <52686522.5080706@intertainservices.com> Date: Wed, 23 Oct 2013 20:09:06 -0400 From: Mike Jakubik User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: koobs@FreeBSD.org, Koop Mast , gnome@FreeBSD.org, python@FreeBSD.org Subject: Re: FreeBSD Port: graphics/py-cairo References: <526803B9.3010102@intertainservices.com> <52685214.5080503@rainbow-runner.nl> <526859F5.1060608@FreeBSD.org> In-Reply-To: <526859F5.1060608@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-intertainservices-MailScanner-Information: Please contact the ISP for more information X-intertainservices-MailScanner-ID: BFA7A5643C.A0E25 X-intertainservices-MailScanner: Found to be clean X-intertainservices-MailScanner-From: mike.jakubik@intertainservices.com X-Spam-Status: No X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Oct 2013 00:09:13 -0000 Hi, I found the problem. This port does not seem to respect the CC environment variables and was trying to compile with gcc, instead of clang. The problem is that my CFLAGS dont work in gcc (no -mavx in old gcc, etc) and it seemed to pull these flags from python, because changing them in /etc/make.conf did not help. After I recompiled python without these flags, I was able to compile this. Still though, it would be nice if it used clang, as defined in my make.conf. Sorry for the noise. Thanks. On 10/23/13 19:21, Kubilay Kocak wrote: > On 24/10/2013 9:47 AM, Koop Mast wrote: >> >> On 10/23/13 19:13, Mike Jakubik wrote: >>> Hello, >>> >>> I am unable to compile this on 9.2-STABLE. >> Mike I see you got both 2.7 and 3.3 installed. When I build py-cairo it >> worked fine, so I don't really know what happening with waf. So I cc'd >> python@ since they might have a beter idea what waf is doing. >> >> -Koop >> > The output of the following might help to isolate: > > - /usr/local/bin/python2.7-config --cflags > - /usr/local/bin/python2.7-config --libs > - /usr/local/bin/python2.7-config --includes > - /usr/local/bin/python2.7-config --ldflags > > Also possibly related: > > https://code.google.com/p/waf/issues/detail?id=1118 > > Can you also have a look at config.log and pull out any relevant failures. > > Thanks, > > Koobs >