[mythtv-users] Blue tinge / preview size

[mythtv.users]

> On 03/13/2008 03:18 PM, mythtv.users wrote:
>>> On 03/13/2008 05:55 AM, mythtv.users wrote:
>>>
>>>> I've just upgraded to 0.21 and noticed that the video preview window
>>>> isn't
>>>> right, all the people are blue!
>>>>
>>>> Does anyone else see this, is it just some strange combination of
>>>> factors that only I have?
>>>>
>>> Your MythTV was built without MMX.  If you compiled yourself,
>>>
>> Nope, been there, bought the T-shirt, now I just use packages.

Of course sometimes I make my own packages... ;-)

>>> If you're using a packaged version of Myth, you need to tell your
>>> packager more details of the setup you're using because he needs to
>>> adjust the configuration so it will work on lots of different machines,
>>> but so it also has MMX.
>>>
>> It's a P4 so I'd hope fairly common... I've emailed the packager anyway.
>>
> The thing is that packagers have to mess with things like --cpu, --tune,
> and --arch to get packages that work on lots of different machines, so
> just like self-compiling and using those switches can break things, ...

Well the problem is that when the package is built it runs  ./configure
--compile-type=release --cpu=i586 --tune=i686 --enable-mmx --prefix=/usr
--libdir=/usr/lib --with-bindings=perl,python --enable-joystick-menu
--enable-lirc --enable-ivtv --enable-firewire --enable-dvb
--dvb-path=/usr/include --enable-audio-oss --enable-audio-alsa
--enable-audio-arts --enable-dts --enable-audio-jack --enable-x11
--enable-xrandr --enable-xv --enable-xvmc --enable-xvmc --enable-xvmc-vld
--enable-xvmc-pro --enable-opengl-vsync --disable-directfb

Which creates a correct config file (and would build), unfortunatly it
then runs.
perl -pi -e"s|^OPTFLAGS=.*|OPTFLAGS=%{optflags}|" config.mak
perl -pi -e's|^ARCHFLAGS=.*|ARCHFLAGS=|' config.mak

Which blows the OPTFLAGS and ARCHFLAGS from config.mak which then means it
fails to build. I've no experience with packaging for anyone else[2] so I
have no idea what those lines are actually for[1] but for me I downloaded
the source rpm, hashed out the two perl lines above (lines 340 and 341
IIRC) from the SPEC file and rebuilt my packages. Tada, no more blue. I
personally left the version number the same so that any updates (hopefully
with mmx) will update rather than conflict.

Druid

[1] I presume to make it build generic enough to run on a number of
architectures but I don't understand why this wouldn't just be done in the
configure.
[2] I had a play with creating suse rpms based on the fedora spec file but
although I did it I gave up playing when I found someone else with more
experience doing the same!