public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Willem van der Walt <wvdwalt@csir.co.za>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: build speakup as modules with standard 2.6.26 kernel docs?
Date: Fri, 19 Sep 2008 12:32:55 +0200 (SAST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0809191229260.27627@localhost.localdomain> (raw)
In-Reply-To: <20080916210134.GG4809@implementation>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1528 bytes --]

Should I downgrade the kernel?
This is from intrepid:
uname -r gives:
2.6.27-3-generic
The relevant part of module assistant install speakup gives:
  CC [M]  /usr/src/modules/speakup/main.o
/usr/src/modules/speakup/main.c: In function 
speakup_paste_selection':
/usr/src/modules/speakup/main.c:492: error: 
struct tty_ldisc' has no member named 
receive_buf'
make[4]: *** [/usr/src/modules/speakup/main.o] 

apt-get install speakup-source
says it is the latest version.
Any ideas?
TIA, Willem

On Tue, 16 Sep 2008, Samuel Thibault wrote:

> Willem van der Walt, le Tue 16 Sep 2008 12:26:36 +0200, a écrit :
> > Where are documentation describing how to build speakup as modules for use 
> > with a standard kernel?
> 
> install speakup-source, then see
> /usr/share/doc/speakup-source/README.Debian
> 
> > The way I understood it, one should be able to do that from kernels 2.6.26 
> > and up
> 
> That's right.
> 
> Samuel
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
-- 
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.


  parent reply	other threads:[~ UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Speakup on Ubuntu 8.04 Hardy Alastair Irving
 ` Samuel Thibault
   ` Accessible Ubuntu Installer luke
     ` Samuel Thibault
       ` luke
         ` luke
           ` Samuel Thibault
             ` luke
         ` Samuel Thibault
           ` luke
             ` Samuel Thibault
               ` luke
           ` Mike Reiser
             ` Chuck Hallenbeck
               ` build speakup as modules with standard 2.6.26 kernel docs? Willem van der Walt
                 ` Gregory Nowak
                 ` Samuel Thibault
                   ` Willem van der Walt
                   ` Willem van der Walt [this message]
                     ` Samuel Thibault
                       ` 2.6.27 intrepid speakup patch? Willem van der Walt
                         ` Samuel Thibault
                           ` Willem van der Walt
               ` Accessible Ubuntu Installer Mike Reiser
                 ` Accessible Debian Installer Kitty Litter
                   ` Terry D. Cudney
             ` Accessible Ubuntu Installer Samuel Thibault
 ` Speakup on Ubuntu 8.04 Hardy Alex Snow

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.64.0809191229260.27627@localhost.localdomain \
    --to=wvdwalt@csir.co.za \
    --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).