From: "John Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: how to patch a 2.6.22 kernel with speakup
Date: Wed, 19 Sep 2007 16:56:55 -0500 [thread overview]
Message-ID: <023801c7fb07$fe787b00$4ba65c90@vv507j> (raw)
In-Reply-To: <20070919205721.GA10303@cq.ftml.net>
Oh, sorry, that touch command was just to fool make. I probably should have
removed that line from my transcript.
I guess i could try compiling to see if it worked.
----- Original Message -----
From: "Chuck Hallenbeck" <chuckh@ftml.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, September 19, 2007 3:57 PM
Subject: Re: how to patch a 2.6.22 kernel with speakup
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> John,
>
> Not long ago I patched a 2.6.22 kernel successfully from the cvs
> archive using the checkout script. Your patching seems to have been
> successful, but the file you were unable to touch is one that does
> exist on my system. Not sure what that means. Do you have a permissions
> problem of some sort? Did you check out the various path elements on
> the way to BUGS?
>
> Chuck
>
>
> On Wed, Sep 19, 2007 at 03:47:27PM -0500, John Heim wrote:
>> Does the checkout script still work? The reason I ask is that i have a
>> Makefile that makes it easier for me to download and compile a kernel. In
>> the past, all I had to do was change the kernel version mumber (2.6.21 to
>> 2.6.22 for example) and it would download the kernel code tar ball,
>> uncompress it, create a symlink to it, and run the checkout script. I ran
>> it
>> today, I expected it tto fail when it ran the checkout script. I've
>> pasted
>> the output below. I don't hear anything that seems like an error message.
>>
>>
>> # make
>> wget http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.22.tar.bz2 -O
>> /usr/src/download
>> s/linux-2.6.22.tar.bz2
>> --13:15:22--
>> http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.22.tar.bz2
>> => `/usr/src/downloads/linux-2.6.22.tar.bz2'
>> Resolving kernel.org... 204.152.191.5, 204.152.191.37
>> Connecting to kernel.org|204.152.191.5|:80... connected.
>> HTTP request sent, awaiting response... 200 OK
>> Length: 45,119,878 (43M) [application/x-bzip2]
>>
>> 100%[========================================>] 45,119,878 39.00K/s
>> ETA 00:00
>>
>> 13:33:49 (39.94 KB/s) - `/usr/src/downloads/linux-2.6.22.tar.bz2' saved
>> [45119878/4511
>> 9878]
>>
>> tar -jxf /usr/src/downloads/linux-2.6.22.tar.bz2
>> //usr/src/bin/checkout
>> Patching version v26
>> ? .built-in.o.cmd
>> ? .speakup.o.cmd
>> ? .speakup_acntpc.o.cmd
>> ? .speakup_acntsa.o.cmd
>> ? .speakup_apollo.o.cmd
>> ? .speakup_audptr.o.cmd
>> ? .speakup_bns.o.cmd
>> ? .speakup_decext.o.cmd
>> ? .speakup_dectlk.o.cmd
>> ? .speakup_drvcommon.o.cmd
>> ? .speakup_dtlk.o.cmd
>> ? .speakup_keyhelp.ko.cmd
>> ? .speakup_keyhelp.mod.o.cmd
>> ? .speakup_keyhelp.o.cmd
>> ? .speakup_keypc.o.cmd
>> ? .speakup_ltlk.o.cmd
>> ? .speakup_sftsyn.o.cmd
>> ? .speakup_spkout.o.cmd
>> ? .speakup_txprt.o.cmd
>> ? .speakupmain.o.cmd
>> ? speakup_keyhelp.ko
>> ? speakup_keyhelp.mod.c
>> cvs update: Updating .
>> P speakup.c
>> cvs update: Updating diff-v22
>> cvs update: Updating diff-v22/save
>> cvs update: Updating diff-v23
>> cvs update: Updating diff-v24
>> cvs update: Updating diff-v25
>> cvs update: Updating diff-v26
>> Creating .orig files [] done.
>> Patching files [pppppppppp] done.
>> Copying files [cccccc] done.
>> touch /usr/src/linux-2.6.22/drivers/char/speakup/BUGS
>> touch: cannot touch `/usr/src/linux-2.6.22/drivers/char/speakup/BUGS': No
>> such file or
>> directory
>> make: *** [/usr/src/linux-2.6.22/drivers/char/speakup/BUGS] Error 1
>> nitschke:/usr/src#
>> nitschke:/usr/src#
>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> - --
> The Moon is Waxing Gibbous (52% of Full)
>
> My web site location is at: http://hallenbeck.ftml.net
> I doubt, therefore I might be.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFG8Y0x0maTgpPXM9cRAlcZAJ9c1ZiYqxC07np1k/L9A5X+x89jvACdFGlK
> BxrBmX935Y2yEHXsOGIW1Zo=
> =zj6Y
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Chuck Hallenbeck
` Kirk Reiser
` Chuck Hallenbeck
` John Heim
` Kenny Hitt
` Chuck Hallenbeck
` Nick Gawronski
` Chuck Hallenbeck
` John Heim [this message]
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='023801c7fb07$fe787b00$4ba65c90@vv507j' \
--to=jheim@math.wisc.edu \
--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).