From owner-freebsd-multimedia@FreeBSD.ORG Wed May 6 05:16:44 2015 Return-Path: Delivered-To: multimedia@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 60585D7A; Wed, 6 May 2015 05:16:44 +0000 (UTC) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1E17A1FAE; Wed, 6 May 2015 05:16:44 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1YprhK-0002ff-Cf; Wed, 06 May 2015 07:16:42 +0200 Date: Wed, 6 May 2015 07:16:42 +0200 From: Kurt Jaeger To: Kevin Oberman Cc: adamw@freebsd.org, multimedia@freebsd.org Subject: Re: Problem with recent multimedia/handbrake and multimedia/x265 updates Message-ID: <20150506051642.GS2157@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2015 05:16:44 -0000 Hi! > Then Kurt added a build conflict with multimedia/x265. > > Why? In https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199126 you find more details about it. > It does not use of depend on the x265 port, but it IS a problem. The > build is pulling in /usr/local/include/x265.h which is significantly > different in the new version of x265, especially in the definition of the > x265_param structure, and that breaks the build. It should be using the > version if x265.h in > work/HandBrake-0.10.1/build/contrib/x265/x265-9329-0d30d2641875-1.5/source/ > but it looks like the appropriate '-I' is not used when building. I looked > around for where this might be set, but did not find it. I really don't > understand cmake. We had someone reporting a problem (in that PR) and a solution, which is not perfect. So I choose to at least document that solution with the patch suggested by Keith White. If there's a better fix, someone has to provide it, given the time and skill constrains we all have. > ATM, this is just a bit pain in the ass as it is not hard to work around, > but it would be nice to have it fixed as the proper procedure may not be > obvious to some: > pkg delete -f x265 > build and install handbrake > re-install x265 > This should probably have been added to UPDATING. This is the generic fix for build conflicts, and because it's the generic fix, it was not added to UPDATING. This should not say this went all fine, but it went so-lala given the contrains we work under. I'm sorry that it caused trouble 8-( -- pi@opsec.eu +49 171 3101372 5 years to go !