ports/120510: multimedia/handbrake doesn't build on amd64

Wes Morgan morganw at chemikals.org
Wed Feb 13 00:50:02 UTC 2008


The following reply was made to PR ports/120510; it has been noted by GNATS.

From: Wes Morgan <morganw at chemikals.org>
To: Jona Joachim <jaj at hcl-club.lu>
Cc: edwin at freebsd.org, bug-followup at freebsd.org, rafan at freebsd.org
Subject: Re: ports/120510: multimedia/handbrake doesn't build on amd64
Date: Tue, 12 Feb 2008 18:23:10 -0600 (CST)

 On Tue, 12 Feb 2008, Jona Joachim wrote:
 
 > Hi!
 > Thanks for your patch! Sorry for replying so late, I've been very busy
 > lately...
 > Does handbrake really compile and work for you on amd64 with this patch
 > applied? Unfortunately I can't test it myself as I currently don't have
 > an amd64 system running FreeBSD.
 > I submitted a patch with a little different approach which should fix
 > the build on amd64: ports/119908. It works on RELENG_7 but it doesn't
 > seem to work on RELENG_6. However your patch is much more elegant.
 > Could you perhaps test if it works on RELENG_6, too?
 
 
 Yep, it works fine:
 
 [morganw at volatile:/usr/home/media/dvd$]: handbrake -i A_NEW_HOPE -o 
 star_wars.avi
 HandBrake 0.9.1 (2007100800) - http://handbrake.m0k.org/
 2 CPUs detected
 Opening A_NEW_HOPE...
 Scanning title 1...
 Scanning title 1...
 Scanning title 1...
 Scanning title 1...
 Scanning title 1...
 Scanning title 1...
 Scanning title 1...
 Scanning title 1...
 
 <snip>
 
 [mpeg4 @ 0x886a20]removing common factors from framerate
 No accelerated IMDCT transform found
 Encoding: task 1 of 1, 2.84 % (184.08 fps, avg 191.80 fps, ETA 00h15m09s)
 
 [morganw at volatile:/usr/home/media/dvd$]: uname -a
 FreeBSD volatile 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #4: Sun Jan 13 
 11:48:41 CST 2008     morganw at volatile:/usr/src/sys/amd64/compile/VOLATILE 
 amd64
 
 It works the same as handbrake on my i386 laptop (Scanning for "forced 
 subs" is broken on both). Unfortunately I don't have a RELENG_6 machine to 
 test it on at the moment. The assembler error messages referenced in your 
 PR look like they are 32-bit specific code that isn't being avoided on 
 amd64.



More information about the freebsd-ports-bugs mailing list