From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Trouble Compiling modules/kernel
Date: Thu, 8 Jan 2009 09:43:52 +0900 [thread overview]
Message-ID: <BF689DB2FE4A443488FF1846EB1251EF@bouncy> (raw)
In-Reply-To: <44E48C85D8FD47EAA0C4A4D7C36CA1B8@chihuahuad1>
You'd have to build your modules with module-assistant and your kernel with
kernel-package.
This will build a .deb for your kernel and a headers package you can
install.
Alternatively you are managing the symbolic links for the include
directories yourself and this gets tricky.
I run the pre-compiled distribution kernels with the bundled initrds as I
see no problem with the prebuilt kernels and modules outside the kernel tree
cause me no problem.
Someone else will have to sit down and document how to use an out of
distribution kernel.
I posted a guide to what I did to build the modules in late december, this
will be in the list archives.
The url for the list archives is in every message posted to this list in the
headers. go take a look.
the article you seak will be posted in late december from Kerry Hoath
or use google.
Regards, Kerry.
----- Original Message -----
From: "Nick Gawronski" <nick@nickgawronski.com>
To: "Kerry Hoath" <kerry@gotss.net>
Sent: Thursday, January 08, 2009 9:16 AM
Subject: Re: Trouble Compiling modules/kernel
Hi, well the best way to do this would just be to remove all old information
that is no longer usable and update it with the new git information and get
rid of the cvs stuff. If I have a kernel source tar archive from kernel.org
and want to use it with debian where can I put the sources where the speakup
git modules will see them?
----- Original Message -----
From: "Kerry Hoath" <kerry@gotss.net>
To: "Nick Gawronski" <nick@nickgawronski.com>; "Speakup is a screen review
system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, January 07, 2009 5:57 PM
Subject: Re: Trouble Compiling modules/kernel
> cd /a/path/to/store/the/source
> git clone http://linux-speakup.org/speakup.git
>
> cd speakup/src
> make modules
> make modules_install
>
> you'll need kernel and kernel-headers for your current running kernel
> installed for this to work.
>
> Perhaps if someone was to mark up the instructions in html and submit them
> to Kirk the website would get updated?
> Regards, Kerry.
>
> ----- Original Message -----
> From: "Nick Gawronski" <nick@nickgawronski.com>
> To: "Speakup is a screen review system for Linux."
> <speakup@braille.uwo.ca>
> Sent: Thursday, January 08, 2009 8:28 AM
> Subject: Re: Trouble Compiling modules/kernel
>
>
> Hi, I totally agree. No wonder lots of distributions don't have speakup
> if
> the information on the linux speakup site was updated then probably
> speakup
> could be back in versions of linux that it was in before and even more
> versions that never had it. Can you quickly give me instructions on
> getting
> the git version I have debian and have already done apt-get install
> git-core
> so have git installed on my system. Why is the cvs version even still on
> the site if it is no longer being maintained?
> ----- Original Message -----
> From: "Samuel Thibault" <samuel.thibault@ens-lyon.org>
> To: "Speakup is a screen review system for Linux."
> <speakup@braille.uwo.ca>
> Sent: Wednesday, January 07, 2009 5:23 PM
> Subject: Re: Trouble Compiling modules/kernel
>
>
> Zachary Kline, le Wed 07 Jan 2009 12:35:01 -0800, a écrit :
>> There are many detailed sets of instructions in the list archives on
>> how to do this.
>
> Could these find their way to http://linux-speakup.org ? It's a problem
> that information there is mostly outdated.
>
> Samuel
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> 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: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
Joe Kamphaus
` Zachary Kline
` Samuel Thibault
` Nick Gawronski
[not found] ` <0A98E1637487415A909D77F28CEBB13A@bouncy>
[not found] ` <44E48C85D8FD47EAA0C4A4D7C36CA1B8@chihuahuad1>
` Kerry Hoath [this message]
` Nick Gawronski
` Gregory Nowak
` Kerry Hoath
` Gregory Nowak
` Nick Gawronski
[not found] <mailman.1.1231434002.20588.speakup@braille.uwo.ca>
` Joe Kamphaus
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=BF689DB2FE4A443488FF1846EB1251EF@bouncy \
--to=kerry@gotss.net \
--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).