From owner-freebsd-ports@FreeBSD.ORG Tue Dec 25 02:55:44 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 19ABDDF for ; Tue, 25 Dec 2012 02:55:44 +0000 (UTC) (envelope-from mrezny@hexaneinc.com) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) by mx1.freebsd.org (Postfix) with ESMTP id BA56B8FC0C for ; Tue, 25 Dec 2012 02:55:43 +0000 (UTC) X-Originating-IP: 217.70.178.148 Received: from mfilter20-d.gandi.net (mfilter20-d.gandi.net [217.70.178.148]) by relay4-d.mail.gandi.net (Postfix) with ESMTP id 629A217207E for ; Tue, 25 Dec 2012 03:55:26 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mfilter20-d.gandi.net Received: from relay4-d.mail.gandi.net ([217.70.183.196]) by mfilter20-d.gandi.net (mfilter20-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id cFcPwqtllJIh for ; Tue, 25 Dec 2012 03:55:25 +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 relay4-d.mail.gandi.net (Postfix) with ESMTPSA id C05C0172085 for ; Tue, 25 Dec 2012 03:55:24 +0100 (CET) From: Matthew Rezny Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: multimedia/x264 workaround is broken Date: Tue, 25 Dec 2012 03:55:23 +0100 Message-Id: To: freebsd-ports@freebsd.org Mime-Version: 1.0 (Apple Message framework v1085) 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 02:55:44 -0000 The Ports and Clang wiki page has x264 listed as a port with build = problems, but has Y for the USE_GCC=3Dany workaround. The last commit on = the port, over 3 months ago, has a contradictory message, noting the = workaround is insufficient and thus is only a temporary fix. I am running 9.1-RELEASE/amd64 built WITH_CLANG_IS_CC and WITHOUT_GCC. I = hit the deficiency in the workaround today while building ports. I took the default port options, except to disable PGO as I expected = that would be GCC specific. First attempt, configure fails with no = working C compiler, config.log shows it tries to call "gcc" which does = not exist because the port did not trigger any gcc from ports. Second attempt, turn on GCC4.4+ option, clean and make again. Same = failure, config.log is identical. Huh, why didn't it even try to build = some GCC from ports? Looking at the Makefile I notice the blanket = USE_GCC=3Dany and later the conditional USE_GCC?=3D4.4+. So the = workaround appears to smash the port's GCC4.4+ option and thus it could = never actually use any GCC from ports with this workaround in place. The = workaround is now the culprit in the brokenness when WITHOUT_GCC is = used. Third attempt, remove the offending USE_GCC=3Dany line from the = Makefile, turn off the GCC4.4+ option in the port, clean and make again. = Success! The port builds clean with Clang, no errors or warnings except = an ignored GCC specific option. I have not tested use of the port, that = has to wait for others to finish building so I have some way to do so. 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? Happy Festivus (Air your grievances)