public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Erik Heil" <eheil@patmedia.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: recompilation crashed
Date: Thu, 13 Nov 2003 07:05:01 -0500	[thread overview]
Message-ID: <002d01c3a9de$5f065430$0201a8c0@eheil> (raw)
In-Reply-To: <003401c3a9d5$8342d7f0$b40710ac@dkit.ie>

Hello there.  Wouldn't it be just easier to not use rpm and just build the
kernel from scratch, then apply Speakups from the 1.5 tarball or from CVS
using the checkout script?  I'm not that familiar with RH or Fedora and I'm
more of a Debian person, but this approach seemed to make more sense to me.
----- Original Message ----- 
From: "Darragh" <lists@digitaldarragh.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Thursday, November 13, 2003 6:01 AM
Subject: recompilation crashed


> well, I'm at the line
> version 2.85 reloading .nptlspk2 }
> but its been there for hours.  Any ideas?
>
> I'll just go back over what's happened so far.
> I installed fedora core 1.
> booted into x so I changed to run level 3 and rebooted.
> I then had to install the kernel from the speakup modified version.  It
told
> me that it was already there so I used the --force arguement.
> speakup didn't speek so I assumed it was my apollo, after some messing
> around I found that the _synth module was gone and the apollo spoke during
> shut.
> down when I loded the accsent module.
> I found the apollo.c file and noticed that it was checked to compile in
the
> kurnel.  I tried recompiling the kernel and I've got as far as here.
>
> Thanks
>
> Darragh
> Note the person reading it out to me is nearly blind him self so although
> the line is definitly at the bottom of the screen there may be a mistake
or
> so.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup



  reply	other threads:[~ UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Linux-and-Virus Programs? Hart Larry
 ` Sina Bahram
 ` Janina Sajka
   ` Sina Bahram
     ` Gregory Nowak
       ` Sina Bahram
     ` Erik Heil
     ` Janina Sajka
       ` Sina Bahram
   ` Keith Watson
     ` Sina Bahram
     ` Alex Snow
       ` Shaun Oliver
       ` Dj Statik
         ` Alex Snow
 ` Toby Fisher
 ` Shaun Oliver
   ` recompilation crashed Darragh
     ` Erik Heil [this message]
       ` Darragh
 ` Linux-and-Virus Programs? 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='002d01c3a9de$5f065430$0201a8c0@eheil' \
    --to=eheil@patmedia.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).