From owner-freebsd-ports@FreeBSD.ORG Tue Dec 25 13:43: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 9F913FAD for ; Tue, 25 Dec 2012 13:43:53 +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 4BC818FC18 for ; Tue, 25 Dec 2012 13:43:52 +0000 (UTC) X-Originating-IP: 217.70.178.148 Received: from mfilter20-d.gandi.net (mfilter20-d.gandi.net [217.70.178.148]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id C01ECA8070 for ; Tue, 25 Dec 2012 14:43:35 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mfilter20-d.gandi.net Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by mfilter20-d.gandi.net (mfilter20-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id 9J-pIhFHX++w for ; Tue, 25 Dec 2012 14:43:34 +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 17ABDA8079 for ; Tue, 25 Dec 2012 14:43:34 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1085) Subject: Re: multimedia/x264 workaround is broken From: Matthew Rezny In-Reply-To: <50D92254.9060700@gmail.com> Date: Tue, 25 Dec 2012 14:43:32 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <73EA428D-4614-4938-893F-DCD5A3EE8007@hexaneinc.com> References: <50D92254.9060700@gmail.com> To: freebsd-ports@freebsd.org X-Mailer: Apple Mail (2.1085) 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 13:43:53 -0000 On 25 Dec, 2012, at 4:49, Kubilay Kocak wrote: > 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. I did notice the links in the PR to redports, so perhaps you were = suggesting I look at those for previous build error with Clang. = Unfortunately, those links are useless, neither is a build log but = instead a redirect to twitter. These are the second set of build logs = that could be useful but aren't. I had first attempted to look at the = log on the Ports and Clang wiki, but that file was on a host that is = still down. The first build log being unavailable due to a downed host is annoying. = The second set of build logs being unavailable only had to be an = annoyance, but it was turned into an offense with the Twitter redirect. = That is almost as offensive as seeing mention in the announcements that = some things will be posted on Facebook. WTF! Did someone miss their = scheduled beating with the cluebat? The spying with Google analytics was = bad enough, but at least that can be disabled by the client browser. = Stuff posted on Facebook is essentially thrown away effort; not only is = it locked away in a non-public location, but ownership of the material = is relinquished.