[mythtv] [mythtv-commits] Ticket #6685: Compiling SVN head (20786) fails on GetNumberXineramaScreens

[Michael T. Dean]

On 07/03/2009 07:03 AM, MythTV wrote:
> #6685: Compiling SVN head (20786) fails on GetNumberXineramaScreens
>
>  When I try to compile SVN head, it fails, because it can not find the
>  GetNumberXineramaScreen in videooutbase.cpp.
>   
...
>  My config command:
>  {{{
>  ./configure --disable-audio-oss --compile-type=release --enable-proc-opt
>  --disable-joystick-menu --enable-ivtv --disable-lirc --disable-xvmc
>  --enable-xv --disable-xrandr --disable-distcc --disable-dbox2 --disable-
>  audio-jack --disable-xvmc-vld --disable-hdhomerun --disable-firewire
>  --disable-iptv --disable-iwmmxt --disable-altivec --enable-dvb --disable-
>  hdpvr --disable-mheg --disable-opengl-video --disable-opengl-vsync
>  --disable-vdpau --disable-xv --disable-x11
>  }}}
>   
...
>  Did I do something wrong?

Yes, you used configure options that create a broken MythTV build.

Sure, you can now compile your broken build as Mark fixed the bug, but I 
just thought I'd send you a message saying that it /will/ be broken so 
that you don't waste your time or the list's time sending questions 
about why Myth doesn't work (or, worse, waste developer time by 
reporting bugs).

Your configure line is /definitely/ breaking mythtranscode--using 
--disable-audio-oss on GNU/Linux systems breaks parts of Myth.  See: 
http://www.gossamer-threads.com/lists/mythtv/users/184639#184639 and 
http://www.gossamer-threads.com/lists/mythtv/users/185108#185108 and 
http://www.gossamer-threads.com/lists/mythtv/users/184868#184868 .

IIRC, using --disable-x11 on GNU/Linux will break other parts of Myth 
(preview pixmap generation?).

If you want a broken build, go for it.  If you're just trying to get a 
lean/mean build, you should really read up on what --disable-oss (and 
all other disable flags you're specifying) is doing for you (i.e. read 
the MythTV code and read up on what exactly OSS is) and you'll see that 
you're going about it the wrong way.

Chances are that a majority of those other disables are also bad ideas.

I have a feeling that you think you're getting the functionality of the 
disabled --disable-frontend by selectively disabling things you /think/ 
are frontend-only things (but aren't).  Instead, you're creating a 
broken build.

Mike