[mythtv-users] problem with toolchain build for mediamvp

[Rusty McEacharn]

avoid cross-compiling mvpmc if possible.  use the binary releases. 
your geek status will not be as high, but it is a lot easier.  the
following is a section from my binary howto:

5         MVPMC
5.1      Obtaining an original dongle.bin
dongle.bin is the name of the Linux kernel and ramdisk that Hauppauge
supplies for the MediaMVP. The mvpmc project creates a new version of
this file, replacing Hauppauge's frontend software with mvpmc.

You will need to place a copy of the Hauppauge-supplied dongle.bin
file into /tftpboot. The mvpmc build procedure will be looking for the
software in that location.

Download the Hauppauge Windows server software from
http://hauppauge.lightpath.net/software/mediamvp/mediamvpsetup_22_22146.exe
and extract the dongle.bin file:

$ cd ~
$ wget http://hauppauge.lightpath.net/software/mediamvp/mediamvpsetup_22_22146.exe
$ unzip -Ln mediamvpsetup_22_22146.exe dongle.bin
# cp dongle.bin /tftpboot
#exit

5.2      Creating the dongle.bin.mvpmc file
Download a binary release of the mvpmc software to your home directory
from http://prdownloads.sourceforge.net/mvpmc/mvpmc-0.1.2-bin.tar.gz?download.
 You will have to select your mirror.
$ cd ~
$ wget http://internap.dl.sourceforge.net/sourceforge/mvpmc/mvpmc-0.1.2-bin.tar.gz
Extract the mvpmc software from the tar.gz file.  Then, build a new
dongle file called dongle.bin.mvpmc.
$ tar –xvzf mvpmc-0.1.2-bin.tar.gz
$ cd mvpmc-0.1.2-bin
$ ./dongle_build.sh -d /tftpboot/dongle.bin -o dongle.bin.mvpmc
# cp dongle.bin.mvpmc /tftpboot
# exit

5.3      Creating the dongle.bin.mvpmc.config file
When the MediaMVP is booting, it will try to download this file from
the tftp server. If you would like your MediaMVP to automatically
start the mvpmc application, you should make your config file look
something like to use NFS for recording playback. In this case,
192.168.0.2 is the IP address of the master backend server. We are
creating a mount point called /myth/tv and then mounting the directory
using NFS. The -r parameter instructs mvpmc to look for the recordings
in /myth/tv.  Since mvpmc can play mp3 files, I mounted /myth/music as
well.

--------------------------------------------------------------------------------------------------------------------
mkdir /myth
mkdir /myth/tv
mkdir /myth/music
/etc/nfsmount.sh 192.168.0.2:/myth/tv /myth/tv
/etc/nfsmount.sh 192.168.0.2:/myth/music /myth/music
/bin/mvpmc -f /etc/helvR10.fnt -s 192.168.0.2 -o svideo -a 4:3 -m ntsc
-r /myth/tv &
--------------------------------------------------------------------------------------------------------------------

In the example above, mvpmc would get the MythTV program guide info
via the MythTV protocol, but it would play the recordings via NFS. 
The mvpmc software can also use the Myth protocol for recording
playback rather than using NFS. If you would like to use the Myth
protocol, the last line in dongle.bin.mvpmc.config would look like
this.

/bin/mvpmc -f /etc/helvR10.fnt -s 192.168.0.2 -o svideo -a 4:3 -m ntsc –r &

Copy dongle.bin.mvpmc.config to /tftpboot.
# cp dongle.bin.mvpmc.config /tftpboot

# exit