From: Garry Turkington <garry.turkington@acm.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speakup & 2.6.12 kernels
Date: Wed, 17 Aug 2005 21:55:33 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0508172151590.13372@localhost.localdomain> (raw)
In-Reply-To: <20050818014118.GA27220@taylor.homelinux.net>
Hi,
I've built Speakup from CVS into every sub-release of the vanilla
2.6.12 kernel as well as the Fedora mangled version.
So I'd suggest the errors are due to Debian-specific kernel changes.
Simply ignoring the rejected patches is not likely a wise course of
action, try applying the rejected patches by hand - they'll be in the .rej
files in the apposite directories.
Regards,
Garry
--
Garry Turkington
garry.turkington@gmail.com
On Wed, 17 Aug 2005, Lorenzo Taylor wrote:
> I am trying to patch a 2.6.12 kernel from Debian with Speakup 2.0, which says
> that it will work with any 2.6.10 or later kernel.. However, I am getting the
> following when I run ./install from the speakup directory:
>
> Patching version v26
> Creating .orig files [...............] done.
> Patching files [ppppppp1 out of 3 hunks FAILED -- saving rejects to file drivers/Makefile.rej
> pppp9 out of 13 hunks FAILED -- saving rejects to file drivers/char/vt.c.rej
> pppp] done.
> Copying files [ccccc] done.
>
> I tried using Speakup from CVS with slightly different but very similar results.
>
> Is it safe to go ahead and try compiling the kernel? Does Speakup just not work
> with 2.6.12 kernels? Or is it a Debian thing since I am using the Debian kernel
> sources?
>
> All help appreciated,
> Lorenzo
> --
> Living your life is a task so difficult, it has never been attempted before.
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Lorenzo Taylor
` Garry Turkington [this message]
` John covici
` Kenny Hitt
` 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=Pine.LNX.4.63.0508172151590.13372@localhost.localdomain \
--to=garry.turkington@acm.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).