public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kenny Hitt <kenny@hittsjunk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: audio players
Date: Mon, 18 Apr 2005 00:27:53 -0500	[thread overview]
Message-ID: <20050418052753.GA16013@blackbox> (raw)
In-Reply-To: <Pine.LNX.4.62.0504171937270.2737@hhs48.com>

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@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


  parent reply	other threads:[~ UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Eric Kosten
 ` Lorenzo Taylor
   ` Charles Hallenbeck
     ` Lorenzo Taylor
       ` Charles Hallenbeck
         ` Sean McMahon
       ` Charles Hallenbeck
         ` Lorenzo Taylor
           ` Charles Hallenbeck
             ` Lorenzo Taylor
               ` Charles Hallenbeck
           ` Charles Hallenbeck
             ` Kenny Hitt
       ` Charles Hallenbeck
         ` Lorenzo Taylor
     ` Kenny Hitt [this message]
       ` Charles Hallenbeck
         ` Kenny Hitt
           ` Charles Hallenbeck
             ` Kenny Hitt
               ` Kenny Hitt
                 ` Charles Hallenbeck
               ` jim grimsby
                 ` Charles Hallenbeck
                 ` Kenny Hitt
                   ` jim grimsby
             ` jim grimsby
             ` Sean McMahon
               ` Charles Hallenbeck
                 ` Kenny Hitt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050418052753.GA16013@blackbox \
    --to=kenny@hittsjunk.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).