From: "Tim Burgess" <tim.burgess@blazie.co.uk>
To: <speakup@braille.uwo.ca>
Subject: RE: kernel compile gone wrong.
Date: Sun, 23 Sep 2001 13:36:27 +0100 [thread overview]
Message-ID: <000401c1442c$c7d8d290$f9b4e5d4@tim02> (raw)
In-Reply-To: <Pine.LNX.4.21.0109230702110.1418-100000@c1422183-a.ross1.pa.home.com>
Hi,
I tried compiling the 2.4.9 kernel without the patch, so you might have
answered my question as well. However, I'm confused about the "CVS"
reference for SpeakUp. I've been out of the SpeakUp loop for a while (I'm
running 0.09 under kernel 2.2.16 at the moment). The only SpeakUp code I
can find on the web/FTP site is a tar.gz. The installation documentation
that I have seems to indicate that all I need to do is unpack the file into
/usr/src, change to the SpeakUp directory and execute ./install. It did
occur to me that I might (or might not) need to do the patch as per the 0.09
version.
Dazed and confused - can you advise?
P.S. Just to show that I'm still a complete newbie, how do I delete a
directory containing files and sub-dirs in one go?
Cheers.
Tim
-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Frank Carmickle
Sent: 23 September 2001 12:18
To: speakup@braille.uwo.ca
Subject: Re: kernel compile gone wrong.
Shaun
Your errors are with incompatible versions of speakup and a kernel I do
believe. Looks like you tried building current cvs against 2.4.4. I
don't see any reason why you would want to build 2.4.4 at this point. I
suggest that you build 2.4.9ac10. This can be accomplished by getting the
2.4.9 source tarball and the ac10 patch which can be found at
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/linux-2.4/2.4.9/patch-2.4.
9-ac10.gz
To patch the ac patch make sure the the 2.4.9 source is in /usr/src/linux
then make a link to this called linux.ac This can be done by 'ln -s linux
linux.ac' from with in the /usr/src dir. Then from /usr/src do 'patch -p0
<patch-2.4.9-ac10' Of course this assumes that you already gunziped
it. Then use the checkout script to apply cvs of speakup.
On Sun, 23 Sep 2001, Shaun Oliver wrote:
> ok I'm man enough to admit it. I've got a major problem I think.
> or at least a minor one I can't sort out for some reason.
> I don't know exactly why, but I seem to have a problem with my kernel
> compile. I'm trying to compile kernel 2.4.4 for slackware 7.1 and I run
> into some trouble when it gets to the vt.o part.
> I've attached a copy of my image.log compressed of course to see if anyone
> else either has had this problem or knows of a way to figure it out.
--
Frank Carmickle
phone: 412 761-9568
email: frankiec@dryrose.com
_______________________________________________
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: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
Shaun Oliver
` Frank Carmickle
` Shaun Oliver
` Tim Burgess [this message]
` Shaun Oliver
` Steve Holmes
` Tim Burgess
` Janina Sajka
` Tim Burgess
` Janina Sajka
` Gregory Nowak
` Gregory Nowak
` Janina Sajka
` Janina Sajka
` Tim Burgess
` Gregory Nowak
` Tim Burgess
` William F. Acker WB2FLW +1-303-777-8123
` Tim Burgess
` Gregory Nowak
` Tim Burgess
` Shaun Oliver
` Tim Burgess
` Tim Burgess
` Charles Hallenbeck
` Tim Burgess
` Shaun Oliver
` Gregory Nowak
` Gregory Nowak
` Gregory Nowak
` Tim Burgess
Holmes, Steve
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='000401c1442c$c7d8d290$f9b4e5d4@tim02' \
--to=tim.burgess@blazie.co.uk \
--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).