From owner-freebsd-ports@FreeBSD.ORG Tue Dec 25 15:03:53 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F33B5CFC for ; Tue, 25 Dec 2012 15:03:52 +0000 (UTC) (envelope-from mrezny@hexaneinc.com) Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) by mx1.freebsd.org (Postfix) with ESMTP id 9E2598FC0A for ; Tue, 25 Dec 2012 15:03:52 +0000 (UTC) X-Originating-IP: 217.70.178.145 Received: from mfilter17-d.gandi.net (mfilter17-d.gandi.net [217.70.178.145]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id 57D87A807A; Tue, 25 Dec 2012 16:03:41 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mfilter17-d.gandi.net Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by mfilter17-d.gandi.net (mfilter17-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id xie-YRlqcqwv; Tue, 25 Dec 2012 16:03:39 +0100 (CET) X-Originating-IP: 81.90.254.28 Received: from [192.168.1.197] (unknown [81.90.254.28]) (Authenticated sender: mrezny@hexaneinc.com) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 8D181A808B; Tue, 25 Dec 2012 16:03:39 +0100 (CET) Subject: Re: multimedia/x264 workaround is broken Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Matthew Rezny In-Reply-To: <50D9B0C6.1080009@gmail.com> Date: Tue, 25 Dec 2012 16:03:38 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <50D92254.9060700@gmail.com> <73EA428D-4614-4938-893F-DCD5A3EE8007@hexaneinc.com> <50D9B0C6.1080009@gmail.com> To: Kubilay Kocak X-Mailer: Apple Mail (2.1085) Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Dec 2012 15:03:53 -0000 On 25 Dec, 2012, at 14:57, Kubilay Kocak wrote: > On 26/12/2012 12:43 AM, Matthew Rezny wrote: >> On 25 Dec, 2012, at 4:49, Kubilay Kocak wrote: >>=20 >>> On 25/12/2012 1:55 PM, Matthew Rezny wrote: >>>=20 >>>> The immediate question is, what was the original error that >>>> mandated the workaround and does that error still occur with >>>> current version of Clang? If the latter is no, can we get rid >>>> of the temporary workaround? >>>=20 >>> This may help provide some answers: >>>=20 >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/171542 >>>=20 >> Thank you for the suggestion. However, the topic of that PR is >> disabling PGO to build with Clang. I had already turned off the PGO >> option before the first build attempt, and the problem I faced was >> the insistence upon calling the non-existent GCC regardless of >> chosen port options. >=20 > I referenced the PR as an additional information source, as I wasn't > entirely sure what issue you were facing without logs to reference. I > should have been more explicit than 'may help' and will do my best > next time. >=20 > Ta, >=20 > Koobs >=20 The log was not included because it was nothing but a single useful line = of information, the attempt to invoke gcc, following two screens worth = of boilerplate. In case I was unclear before, the problem I found is that the workaround = makes it always call the assumed-present base gcc. There are two = failures, never triggering a build of gcc from ports even when setting = the option that should require it (GCC4.4+), and still attempting to = call base gcc rather than the ports version had any gcc port been = installed. Both those errors stem from a workaround that does not even seem = necessary. The port appears to build fine with Clang.