public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Ryan Mann <rmann@rmisp.net>
To: speakup@braille.uwo.ca
Subject: Re: sblive: alsa compile problem
Date: Wed, 27 Mar 2002 19:38:56 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0203271936280.25360-100000@rmnet> (raw)
In-Reply-To: <002b01c1d5ce$1ad48880$01213e18@mycomputer>

0.9.0beta12 compiled for me, so I think he is just missing a library.  
MMaybe if you posted some of the undefined references or other error 
messages, one of the C experts on this list could tell what you need.
On 
Wed, 27 Mar 2002, Igor Gueths wrote:

> I compiled the driver utils and libs. I also used alsa 0.90 beta 9. You may want to try that version possibly.
> ----- Original Message ----- 
> From: Cheryl Homiak <chomiak@chartermi.net>
> To: speakup <speakup@braille.uwo.ca>
> Sent: Wednesday, March 27, 2002 2:51 PM
> Subject: sblive: alsa compile problem
> 
> 
> > Ok, I decided to try using alsa.
> > The drivers and libs compiled okay, but when I got to the utils I got a lot of
> > undefined references; can send in more detail if needed.
> > I am using the 0.9.0beta12 packages and have linux kernel 2.4.17.
> > Gcc 2.99.5.
> > I know I must just be missing a package, but can't figure out what.
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



  reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Cheryl Homiak
 ` Igor Gueths
   ` Ryan Mann [this message]
     ` Igor Gueths
 ` Kerry Hoath
   ` Cheryl Homiak
     ` Kerry Hoath

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=Pine.LNX.4.44.0203271936280.25360-100000@rmnet \
    --to=rmann@rmisp.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).