public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Georgina Joyce" <gena-j@bulldoghome.com>
To: "'Speakup is a screen review system for Linux.'"
	<speakup@braille.uwo.ca>
Subject: RE: Anyone found problems with 2.6.21.5 kernel speakup and mrproper?
Date: Thu, 21 Jun 2007 15:14:21 +0100	[thread overview]
Message-ID: <004d01c7b40e$79098f80$0302a8c0@forestfern> (raw)
In-Reply-To: <20070620232134.GA12146@localhost.localdomain>

Hi

Interesting, well if anyone is serious about having speakup in the main kernel source such issues like this should be resolved.  It's not as clear cut as you state.  I didn't think my 2.6.21.3 source came up with that error. 
We'll never know now because after building a kernel, the error goes away.  Let's call it the virgin bug.  <smiles>

Regards

Gena

Amateur Call: M 0 E B P

VOIP / IM: gena1959uk



-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca] On Behalf Of Gregory Nowak
Sent: Thursday, June 21, 2007 12:22 AM
To: speakup@braille.uwo.ca
Subject: Re: Anyone found problems with 2.6.21.5 kernel speakup and mrproper?


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

I remember seeing this at least since 2.6.19, and probably earlier, it's
been like that for a good while. I always assumed it was a problem
with the kernel source itself, rather than the speakup patch, since I
never bothered running mrproper on a clean source, as I mentioned in
another thread here earlier. 

Since everything compiles and works fine anyway, I just ignored it,
and didn't worry about it, or bother mentioning it.

Greg


On Wed, Jun 20, 2007 at 11:32:16PM +0100, Georgina Joyce wrote:
> Hi
> 
> Here's a strange thing, after patching a fresh source of the 2.6.21.5 tar ball I get the error shown below.  I've tried as a standard user and as root.  I don't understand why that the patching of speakup is causing this error when issuing the mrproper command.  Because the file named in the error isn't part of the tar ball in the first place.  The mrproper command doesn't produce this error until the kernel has been patched with speakup.  I've downloaded and checked out with fresh tar balls and the results are the same.
> 
> I proceeded with the build which was successful, without errors and the kernel came up talking.
> 
> Kirk are you aware of this?  I've built speakup into the kernel, oh thinking about it, the only speakup module is the software synth.  Which I haven't attempted to run.  It's occurred on a debian etch and also on a nearly complete lfs installation.
> 
> make mrproper
> awk: cmd. line:1: fatal: cannot open file `/usr/src/linux-2.6.21.5/include/linux/version.h' for reading (No such file or directory)
> 
> Regards
> 
> Gena
> 
> Amateur Call: M 0 E B P
> 
> VOIP / IM: gena1959uk
> 
> 
> 
> _______________________________________________
> 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.6 (GNU/Linux)

iD8DBQFGebZ+7s9z/XlyUyARAnZwAKCYQCf6xZhdZnwNzcVKxn+xdLIsgwCglCKE
mUgSfekWh7vn1/ovdLV8SO4=
=C8om
-----END PGP SIGNATURE-----

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup

__________ NOD32 2342 (20070621) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com




  reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Georgina Joyce
 ` Gregory Nowak
   ` Georgina Joyce [this message]
 ` randy turner
   ` Georgina Joyce

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='004d01c7b40e$79098f80$0302a8c0@forestfern' \
    --to=gena-j@bulldoghome.com \
    --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).