public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Jeremy R Schmidt" <jschmidt@cs.und.edu>
To: <speakup@braille.uwo.ca>
Subject: Re: errors when installing speakup.
Date: Wed, 12 Jun 2002 20:06:28 -0500	[thread overview]
Message-ID: <000001c2132f$8a0e0340$18b7fea9@jeremy1> (raw)
In-Reply-To: <Pine.LNX.4.44.0206082322390.3315-100000@babel.hpcc.noaa.gov>

Hi, I don't believe there is a kernel directory in the
/pub/speakup/disks/redhat/7.2/kernel directory. There is either a kernel or
kernels directory in the 7.3 directory.
Also, I think there may have been kernels in the 7.2 directory, but what if
I have 2.4.7-10, do I just need the kernel rpm, or do I need to upgrade
other kernel rpms as well? Also, one more question, what kernel do I need as
far as the 386, etc. I have a pIII 1.2GHZ.
Thanks,

Jeremy
----- Original Message -----
From: <jwantz@hpcc2.hpcc.noaa.gov>
To: <speakup@braille.uwo.ca>
Sent: Saturday, June 08, 2002 10:35 PM
Subject: Re: errors when installing speakup.


> Hi Jeremy,
> I am not sure where Toby gets his ideas about Redhat being so
> drastically different from his favorite distribution, but it seems you
> did not have the source code for your kernel installed.  If you had, you
> most assuredly would have seen a linux directory when you were in
> /usr/src.  Unless you have a specific reason for building your kernel
> though you can ftp to bumpy.braille.uwo.ca and go to the directory
> /pub/speakup/disks/redhat/7.2/kernel and download the binary rpm.  Or as
> somebody suggested you could try the 7.3 rpms.  Make sure though that if
> you try the 7.3 kernel and you want to try alsasound, you use the 7.3
> alsasound.  Alsa is kernel dependent!
>
>      Jim Wantz WB0TFK
> On Sat, 8 Jun 2002, Jeremy R Schmidt
> wrote:
>
> > Hello everyone, I downloaded and untared speakup 1.0.
> > When I ran ./install under redhat 7.2, I got the following.
> > I had to retype it out, so I hope I didn't miss anything.
> > Can anyone let me know if I need to fix anything, or if I should keep
going?
> > P.S. I checked, and I don't have a linux directory in /usr/src, so I
created
> > a simlink with the following command
> > ln -s linux-2.4.7-10 linux
> > no should I just run ./install again?
> >
> > Thanks,
> >
> > Jeremy
> > Jeremy
> > head: /usr/src/linux/Makefile: No such file or directory
> >
> > Patching version V
> >
> > cp: cannot stat `speakup': NO such file or directory
> >
> > Creating .orig files [cat:
/usr/src/linux/drivers/char/speakup/patchlist-v:
> > No such file or directory
> >
> > ] done.
> >
> > Patching files [ppatch: checkclean: extra operand
> >
> > patch: Try `patch --help' for more information
> >
> > ] done.
> >
> > Copying files [ccp: copying multiple files, but last `todo' is not a
> > directory
> >
> > Try ` cp --help' for more information.
> >
> > ] done.
> >
> >
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>





      parent reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Jeremy R Schmidt
 ` Toby Fisher
 ` Aaron Howell
 ` jwantz
   ` Janina Sajka
   ` Jeremy R Schmidt
     ` jwantz
   ` Jeremy R Schmidt [this message]

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='000001c2132f$8a0e0340$18b7fea9@jeremy1' \
    --to=jschmidt@cs.und.edu \
    --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).