Hi.
Here's how I built mplayer from source.
I ran the script in the debian subdir of the mplay source instead of
just running ./configure. This script told me the packages needed to be
installed when it couldn't find things.
In case it doesn't, install the apt-file package. You will need to
run
apt-file update
before it will be useful.
After that, when the configure process doesn't find something, use
apt-file search filename
to find the package containing the file. I like using the script
instead of getting someone's pre-built package because I ended up with a
mplayer Debian package built specific to my system. For example, it is
built for my AMD cpu instead of auto detecting the cpu each time it starts.
Hope this helps.
Kenny
On Sun, Apr 17, 2005 at 07:40:55PM -0400, Charles Hallenbeck wrote:
> Lorenzo,
> Your suggestion did not work for me. The package seems to depend on
> other things from "unstable" and apt-get is reluctant to install the
> dependencies.
>
> I compiled the 1.0pre7 source on this Debian system, but lots of things
> failed to be discovered automatically in ./configure. Someone on the
> mplayer-users list suggested I may not have installed all -dev-packages.
> How would one do that? Is there a "wholesale" method, or must it be done
> one by one, and if so, where to begin?
>
> Thanks.
>
> Chuck
>
>
>
> --
> The Moon is Waxing Gibbous (63% of Full)
> "Things are in the saddle, and they ride mankind." Ralph Waldo Emerson
> Visit my download site at http://www.mhcable.com/~chuckh
>
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
