public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Applying speakup 2.0 patch on debian kernel 2.6.16 failed
Date: Fri, 7 Jul 2006 11:51:18 -0700	[thread overview]
Message-ID: <20060707185118.GB30873@localhost.localdomain> (raw)
In-Reply-To: <87k66pmqpg.fsf@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It seems like you're applying speakup 2.0 from the tarball, and that
won't work. You need to either use the latest cvs version, or go back
to a kernel that the tarball will still patch against. I don't
remember what kernel version that would be, maybe someone else knows,
or you'll just have to search the list archives, in the hope of
finding that info. Hth.

Greg


On Fri, Jul 07, 2006 at 05:31:39PM +0300, Dart Vader wrote:
> 
> Hi.
> 
> Can't apply speakup patch on a debian kernal. I do:
> 
> $ cd /usr/src/linux
> $ make mrproper
> $ cd /usr/src/speakup-2.0/
> $ ./install 
> Patching version v26
> Creating .orig files [...............] done.
> Patching files [pp1 out of 1 hunk FAILED -- saving rejects to file arch/mips/Kconfig.rej
> p1 out of 1 hunk FAILED -- saving rejects to file arch/sparc64/Kconfig.rej
> p1 out of 1 hunk FAILED -- saving rejects to file arch/sparc/Kconfig.rej
> pppp9 out of 13 hunks FAILED -- saving rejects to file drivers/char/vt.c.rej
> pp1 out of 3 hunks FAILED -- saving rejects to file drivers/Makefile.rej
> ppppp] done.
> Copying files [ccccc] done.
> $ 
> 
> I use the following debian kernal:
> Linux version 2.6.16-2-k7 (Debian 2.6.16-15) (waldi@debian.org) (gcc version 4.0.4 20060507 (prerelease) (Debian 4.0.3-3)) #1 Wed Jun 21 18:43:32 UTC 2006
> 
> I use a downloaded from speakup website tarball of speakup source:
> speakup-2.0.tar.gz
> 
> What I did wrong? Where can I get docs to solve my problem?
> Tell me if I should provide to you more information about my system.
> 
> 
> ---
> Roman
> out
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFErq0m7s9z/XlyUyARAuluAJwMr241dNR3OhWA1M9IWaDbJeZYhACeP5BT
aSL91w8PRTquLV5rQYqm0tg=
=Ci5C
-----END PGP SIGNATURE-----


  reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Dart Vader
 ` Gregory Nowak [this message]
   ` Gregory Nowak
     ` Lorenzo Taylor
       ` Dart Vader
         ` Gregory Nowak
           ` Steve Holmes
             ` Applying speakup 2.0 patch on debian kernel 2.6.16 failed [solved] Dart Vader
   ` Applying speakup 2.0 patch on debian kernel 2.6.16 failed Lorenzo Taylor

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=20060707185118.GB30873@localhost.localdomain \
    --to=greg@romuald.net.eu.org \
    --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).