public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
* Trouble Compiling modules/kernel
@  Joe Kamphaus
   ` Zachary Kline
  0 siblings, 1 reply; 11+ messages in thread
From: Joe Kamphaus @  UTC (permalink / raw)
  To: speakup

What am I doing wrong?

I am trying to compile a kernel and keep getting this error:

CC [M]  drivers/char/speakup/speakup.o
drivers/char/speakup/speakup.c:2677:39: error: macro "DECLARE_WORK" requires 3 arguments, but only 2 given
drivers/char/speakup/speakup.c:2677: warning: type defaults to ‘int’ in declaration of ‘DECLARE_WORK’
drivers/char/speakup/speakup.c: In function ‘speakup_help’:
drivers/char/speakup/speakup.c:2686: error: ‘ld_help’ undeclared (first use in this function)
drivers/char/speakup/speakup.c:2686: error: (Each undeclared identifier is reported only once
drivers/char/speakup/speakup.c:2686: error: for each function it appears in.)
make[3]: *** [drivers/char/speakup/speakup.o] Error 1
make[2]: *** [drivers/char/speakup] Error 2
make[1]: *** [drivers/char] Error 2
make: *** [drivers] Error 2

I have tried to compile as module or included in kernel.  I have tried several kernel versions. I am using cvs with the following script to patch the source.

#!/bin/bash

ROOTDIR=/usr/src/linux
if [ "$1" != "" ]; then
	ROOTDIR="$1"
else
    if [ -d kernel -a -d Documentation ]; then
	ROOTDIR=`pwd`
    fi
fi

VERSION=v`head -2 $ROOTDIR/Makefile | \
	awk '{ printf "%s",$3 }'`

DIR=$ROOTDIR/drivers/char/speakup

echo "Patching version $VERSION"

if [ ! -d ${DIR}/CVS ] && [ "$CVSROOT" == "" ]; then
	echo 'CVSROOT not set.  Enter it below.  Hit enter for anonymous.'
	read -p 'CVSROOT> ' CVSROOT
	[ "$CVSROOT" == "" ] &&
	  CVSROOT=':pserver:anonymous@linux-speakup.org:/usr/src/CVS'
	export CVSROOT
	cvs login || exit
fi

if [ "$1" != "-p" ]; then
	#  get new version
	mkdir -p ${DIR%/speakup}
	cd ${DIR%/speakup}
	if [ -d speakup ] && [ -d ${DIR}/CVS ]; then
		cd speakup
		cvs update -d -P || exit
	else
	rm -fr ${DIR}
		cvs co -P speakup || exit
		cd speakup
	fi
fi

#  make .orig files
echo -n 'Creating .orig files ['
for i in `cat ${DIR}/patchlist-${VERSION}`; do
	patch=`echo $i | cut -f 1 -d ,`
	filebase=`echo $i | cut -f 2 -d ,`

	mkdir -p `dirname $ROOTDIR/$filebase`
	if [ "$patch" == "1" ]; then
		if [ ! -e $ROOTDIR/$filebase.orig ]; then
			echo -n .
			cp $ROOTDIR/$filebase $ROOTDIR/$filebase.orig
		fi
	fi
done
echo '] done.'

#  apply patches
echo -n 'Patching files ['
for i in ${DIR}/diff-${VERSION}/*.patch; do
	# skip dirs
	[ -d $i ] && continue
	echo -n p
	writeloc=${i##$DIR\/diff-${VERSION}\/}
	writeloc=${writeloc%.patch}
	writeloc=${writeloc//^/\/} 
	patch --silent -f -p0 -o $ROOTDIR/$writeloc $ROOTDIR/$writeloc.orig $i
done
echo '] done.'

#  copy files
echo -n 'Copying files ['
for i in ${DIR}/diff-${VERSION}/*.copy; do
	# skip dirs
	[ -d $i ] && continue
	echo -n c
	writeloc=${i##$DIR\/diff-${VERSION}\/}
	writeloc=${writeloc%.copy}
	writeloc=${writeloc//^/\/} 
	cp $i $ROOTDIR/$writeloc
done
echo '] done.'

http://www.joekamphaus.net



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Trouble Compiling modules/kernel
   Trouble Compiling modules/kernel Joe Kamphaus
@  ` Zachary Kline
     ` Samuel Thibault
  0 siblings, 1 reply; 11+ messages in thread
From: Zachary Kline @  UTC (permalink / raw)
  To: Speakup is a screen review system for Linux.

Hi,
    You need to switch from CVS to Git.  There are many detailed sets of 
instructions in the list archives on how to do this.
    What distribution are you compiling for, and which kernel versions are 
you dealing with?
Best,
Zack.

----- Original Message ----- 
From: "Joe Kamphaus" <joe@joekamphaus.net>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, January 07, 2009 12:30 PM
Subject: Trouble Compiling modules/kernel


> What am I doing wrong?
>
> I am trying to compile a kernel and keep getting this error:
>
> CC [M]  drivers/char/speakup/speakup.o
> drivers/char/speakup/speakup.c:2677:39: error: macro "DECLARE_WORK" 
> requires 3 arguments, but only 2 given
> drivers/char/speakup/speakup.c:2677: warning: type defaults to ‘int’ in 
> declaration of ‘DECLARE_WORK’
> drivers/char/speakup/speakup.c: In function ‘speakup_help’:
> drivers/char/speakup/speakup.c:2686: error: ‘ld_help’ undeclared (first 
> use in this function)
> drivers/char/speakup/speakup.c:2686: error: (Each undeclared identifier is 
> reported only once
> drivers/char/speakup/speakup.c:2686: error: for each function it appears 
> in.)
> make[3]: *** [drivers/char/speakup/speakup.o] Error 1
> make[2]: *** [drivers/char/speakup] Error 2
> make[1]: *** [drivers/char] Error 2
> make: *** [drivers] Error 2
>
> I have tried to compile as module or included in kernel.  I have tried 
> several kernel versions. I am using cvs with the following script to patch 
> the source.
>
> #!/bin/bash
>
> ROOTDIR=/usr/src/linux
> if [ "$1" != "" ]; then
> ROOTDIR="$1"
> else
>    if [ -d kernel -a -d Documentation ]; then
> ROOTDIR=`pwd`
>    fi
> fi
>
> VERSION=v`head -2 $ROOTDIR/Makefile | \
> awk '{ printf "%s",$3 }'`
>
> DIR=$ROOTDIR/drivers/char/speakup
>
> echo "Patching version $VERSION"
>
> if [ ! -d ${DIR}/CVS ] && [ "$CVSROOT" == "" ]; then
> echo 'CVSROOT not set.  Enter it below.  Hit enter for anonymous.'
> read -p 'CVSROOT> ' CVSROOT
> [ "$CVSROOT" == "" ] &&
>   CVSROOT=':pserver:anonymous@linux-speakup.org:/usr/src/CVS'
> export CVSROOT
> cvs login || exit
> fi
>
> if [ "$1" != "-p" ]; then
> #  get new version
> mkdir -p ${DIR%/speakup}
> cd ${DIR%/speakup}
> if [ -d speakup ] && [ -d ${DIR}/CVS ]; then
> cd speakup
> cvs update -d -P || exit
> else
> rm -fr ${DIR}
> cvs co -P speakup || exit
> cd speakup
> fi
> fi
>
> #  make .orig files
> echo -n 'Creating .orig files ['
> for i in `cat ${DIR}/patchlist-${VERSION}`; do
> patch=`echo $i | cut -f 1 -d ,`
> filebase=`echo $i | cut -f 2 -d ,`
>
> mkdir -p `dirname $ROOTDIR/$filebase`
> if [ "$patch" == "1" ]; then
> if [ ! -e $ROOTDIR/$filebase.orig ]; then
> echo -n .
> cp $ROOTDIR/$filebase $ROOTDIR/$filebase.orig
> fi
> fi
> done
> echo '] done.'
>
> #  apply patches
> echo -n 'Patching files ['
> for i in ${DIR}/diff-${VERSION}/*.patch; do
> # skip dirs
> [ -d $i ] && continue
> echo -n p
> writeloc=${i##$DIR\/diff-${VERSION}\/}
> writeloc=${writeloc%.patch}
> writeloc=${writeloc//^/\/}
> patch --silent -f -p0 -o $ROOTDIR/$writeloc $ROOTDIR/$writeloc.orig $i
> done
> echo '] done.'
>
> #  copy files
> echo -n 'Copying files ['
> for i in ${DIR}/diff-${VERSION}/*.copy; do
> # skip dirs
> [ -d $i ] && continue
> echo -n c
> writeloc=${i##$DIR\/diff-${VERSION}\/}
> writeloc=${writeloc%.copy}
> writeloc=${writeloc//^/\/}
> cp $i $ROOTDIR/$writeloc
> done
> echo '] done.'
>
> http://www.joekamphaus.net
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Trouble Compiling modules/kernel
   ` Zachary Kline
@    ` Samuel Thibault
       ` Nick Gawronski
  0 siblings, 1 reply; 11+ messages in thread
From: Samuel Thibault @  UTC (permalink / raw)
  To: Speakup is a screen review system for Linux.

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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Trouble Compiling modules/kernel
     ` Samuel Thibault
@      ` Nick Gawronski
       [not found]       ` <0A98E1637487415A909D77F28CEBB13A@bouncy>
  0 siblings, 1 reply; 11+ messages in thread
From: Nick Gawronski @  UTC (permalink / raw)
  To: Speakup is a screen review system for Linux.

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


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Trouble Compiling modules/kernel
       [not found]         ` <44E48C85D8FD47EAA0C4A4D7C36CA1B8@chihuahuad1>
@            ` Kerry Hoath
               ` Nick Gawronski
  0 siblings, 1 reply; 11+ messages in thread
From: Kerry Hoath @  UTC (permalink / raw)
  To: Speakup is a screen review system for Linux.

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
>



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Trouble Compiling modules/kernel
             ` Kerry Hoath
@              ` Nick Gawronski
                 ` Gregory Nowak
                 ` Kerry Hoath
  0 siblings, 2 replies; 11+ messages in thread
From: Nick Gawronski @  UTC (permalink / raw)
  To: Speakup is a screen review system for Linux.

Hi, As I am building my own kernel and have read the installation file is it 
still possible to just compile speakup and dectalk express driver in the 
kernel if I don't plan on giving away the kernel?  It says in Installation 
that this can be done but I wonder how updated that file is.  This way I 
could get rid of the kernels that debian produces and manage them on my own.
----- Original Message ----- 
From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, January 07, 2009 6:43 PM
Subject: Re: Trouble Compiling modules/kernel


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
>


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


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Trouble Compiling modules/kernel
               ` Nick Gawronski
@                ` Gregory Nowak
                 ` Kerry Hoath
  1 sibling, 0 replies; 11+ messages in thread
From: Gregory Nowak @  UTC (permalink / raw)
  To: speakup

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

On Wed, Jan 07, 2009 at 08:26:53PM -0600, Nick Gawronski wrote:
> Hi, As I am building my own kernel and have read the installation file is 
> it still possible to just compile speakup and dectalk express driver in 
> the kernel if I don't plan on giving away the kernel?

Yes.

Greg


- -- 
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.9 (GNU/Linux)

iEYEARECAAYFAkllcHoACgkQ7s9z/XlyUyDuQACfVxarBe8ph3/mkaBUkkBQ3rIF
BI8AoIB62T7y4ldAUuD4VdV4pbZZ7oxh
=uuA0
-----END PGP SIGNATURE-----

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Trouble Compiling modules/kernel
               ` Nick Gawronski
                 ` Gregory Nowak
@                ` Kerry Hoath
                   ` Gregory Nowak
  1 sibling, 1 reply; 11+ messages in thread
From: Kerry Hoath @  UTC (permalink / raw)
  To: Speakup is a screen review system for Linux.

Sure this is possible; but I won't be the one providing you support on how 
to do it <smile>
Note the following points:

Some of the documentation inside the speakup repository seems slightly out 
of date, I need to look at this more closely before I make this acersion 
with confidence.

If you are managing your kernels yourself and not building them with 
kernel-package then you'll have to look after your boot loader, kernel 
image, modules tree and initrd image if you use it.
If you use kernel-package and module-assistant then you can let the system 
manage the boot loader configuration (easy with grub, doable to a point with 
lilo it tracks vmlinuz and vmlinuz.old)
and it'll handle the initrd image.

If you are compiling a kernel that is not debian blessed, you'll have to 
insure that the compiler is using the right set of headers, i.e. the ones 
for your compiled kernel and speakup must link against these also.

This will happen automatically if you compile from source if you succeed in 
patching speakup into the source tree, however after you reboot you need to 
insure that
/lib/modules/kernelversion/build points to the include path of your kernel 
source tree. This usually involves keeping your kernel source around until 
you have compiled any and all out of tree kernel module packages.
These would include a newer alsa if you want one, and other out of tree 
modules.

I must say i'm mystified as to why most people seem to want to "get rid of" 
the distribution kernel; fearing that it is bloated and overloaded.
Usually the initrd takes care of only loading modules you need for your 
hardware.
Of course if you are compiling your own and you know what you are doing; 
then all this talk of include paths, configuration of boot loaders and 
similar should all be known ground.
If it isn't; then perhaps a user should start by compiling out of tree 
kernel modules and work up from there.

The following is directed at no particular person:

If everyone documented what they did as they did it and submitted it to the 
site then we wouldn't have these problems to anywhere this degree.
That said, often people are alergic to documentation, i've noticed this from 
my years of teaching.
We have what we call the silver service brigade that seem to want every step 
and procedure handed to them on a silver platter.
I conceed however there has to be a happy medium between no documentation 
and insert slot a into tab b documentation for every distribution of Linux.

Personally; i'm part of the problem; as I allready have my speakup working 
the way I want, and with 15 years Linux experience this is not a problem for 
me.

I've built my out of tree modules; and they work well enough for my 
purposes.
If people want speakup included in distributions then they're going to have 
to work on it themselves or find someone to do the work for them (possibly 
greasing the wheels with financial contributions).
Samuel does Debian and so do other people, Bill and Janina do an excellent 
job on Fedora,
and apologies to others who did not make it onto this list.

Bundling speakup in the default kernel is certainly potentially disruptive 
and causes more maintainance for the distribution maintainers.
Just my 2 cents worth.
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 11:26 AM
Subject: Re: Trouble Compiling modules/kernel


Hi, As I am building my own kernel and have read the installation file is it
still possible to just compile speakup and dectalk express driver in the
kernel if I don't plan on giving away the kernel?  It says in Installation
that this can be done but I wonder how updated that file is.  This way I
could get rid of the kernels that debian produces and manage them on my own.
----- Original Message ----- 
From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, January 07, 2009 6:43 PM
Subject: Re: Trouble Compiling modules/kernel


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
>


_______________________________________________
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


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Trouble Compiling modules/kernel
                 ` Kerry Hoath
@                  ` Gregory Nowak
                     ` Nick Gawronski
  0 siblings, 1 reply; 11+ messages in thread
From: Gregory Nowak @  UTC (permalink / raw)
  To: Speakup is a screen review system for Linux.

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

On Thu, Jan 08, 2009 at 12:48:54PM +0900, Kerry Hoath wrote:
> I must say i'm mystified as to why most people seem to want to "get rid 
> of" the distribution kernel; fearing that it is bloated and overloaded.

Well, here are my own reasons for it:

1. I'm currently running 2.6.27.8, while debian still seems to be
   providing 2.6.26. I'll grant that this isn't a big deal for me, but
   it relates to my second reason for still building my own kernel.

2. When I started building the 2.6.x.x series on this hardware,
   speakup still had to be built into the kernel in those days. This
   meant that I had to build my own kernel if I wanted something
   fairly recent (both linux, and speakup), and if I was going to do
   that, I might as well customize it to my hardware, and only include
   the support I know I need.

Once we move into the 2.7.x series, or the 3.x series, (whatever is
coming next), where previous experience dictates that you can't use
your current .config file fairly painlessly, I plan to go with the
distro-provided kernels than. To summarize, as long as I don't need to
extensively modify my .config file to build a newer kernel, and as
long as I can get a newer kernel than what the distro provides if I
want to do that, I see no reason not to do it, that's my personal choice.

> If everyone documented what they did as they did it and submitted it to 
> the site then we wouldn't have these problems to anywhere this degree.

The problem here is that the information is scattered through the list
archives, since there are a good number of us who post instructions on
how to do this or that, a lot of times, more than once. This info is
however not on the site, because Kirk has much better things to do
than maintain the web pages, and nobody from the community, it seems,
wants to take on the job, which I frankly can't altogether
fault. maintaining a web site is a big job to do for one person,
especially if it's done as a volunteer, and not as a paid
employee. When you throw 2 or more people into the mix, say assigning
person 1 to this section of the site, and person 2 to another section,
this is a big responsibility for each of those people also, and has
the potential to lead to a conflict, since person 1 may not like the
way person 2 wants to do things.

My own suggestion therefore would be to turn linux-speakup.org into a
wiki, where those who want to help can do so, without having to take
on the responsibility for the entire site, or a section, if they don't
want to. I personally would have no problem expanding the wiki here,
and there whenever I had the chance to do so, but I couldn't commit to
be responsible for an entire site, or even a certain section of it, if
I had to be the single person who made sure that it stays up to date
all the time. Of course, it would be best if those who wanted to
contribute got a login account, as opposed to a free-for-all, and
ideally, there should be a team who would monitor the contents once a
while for quality control, and accuracy. So Kirk, and others, how
about something like apt-get install phpwiki (since I believe Kirk is
running debian on linux-speakup.org), any thoughts?

Greg


- -- 
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.9 (GNU/Linux)

iEYEARECAAYFAklloKoACgkQ7s9z/XlyUyCBuwCgutT4mgQX+SGj/+d/nouDRsHX
GdQAn1SRAYG3GiJMRMaLHH105hVzBXPj
=GdfM
-----END PGP SIGNATURE-----

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Trouble Compiling modules/kernel
                   ` Gregory Nowak
@                    ` Nick Gawronski
  0 siblings, 0 replies; 11+ messages in thread
From: Nick Gawronski @  UTC (permalink / raw)
  To: Speakup is a screen review system for Linux.

Hi, yes having linux-speakup.org as a wiki would really be nice.  I also 
agree that there would need to be some form of control or a maintainer for 
the wiki.  This way people could post documentation in the form of wiki 
pages and could change or remove their own pages if they chose.  The list 
archives are nice but there are a lot of them and if someone wants to look 
for something it is not the easiest thing to search threw years of archives 
to find one answer.  A frequently asked questions on the linux-speakup.org 
with common answers would also be nice for those of us who like reading 
them.  When I find a new program or service on the internet I usually start 
by reading the frequently asked questions first as my question is probably 
answered in there or a close answer is in it if not the exact answer.
----- Original Message ----- 
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Thursday, January 08, 2009 12:43 AM
Subject: Re: Trouble Compiling modules/kernel


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thu, Jan 08, 2009 at 12:48:54PM +0900, Kerry Hoath wrote:
>> I must say i'm mystified as to why most people seem to want to "get rid
>> of" the distribution kernel; fearing that it is bloated and overloaded.
>
> Well, here are my own reasons for it:
>
> 1. I'm currently running 2.6.27.8, while debian still seems to be
>   providing 2.6.26. I'll grant that this isn't a big deal for me, but
>   it relates to my second reason for still building my own kernel.
>
> 2. When I started building the 2.6.x.x series on this hardware,
>   speakup still had to be built into the kernel in those days. This
>   meant that I had to build my own kernel if I wanted something
>   fairly recent (both linux, and speakup), and if I was going to do
>   that, I might as well customize it to my hardware, and only include
>   the support I know I need.
>
> Once we move into the 2.7.x series, or the 3.x series, (whatever is
> coming next), where previous experience dictates that you can't use
> your current .config file fairly painlessly, I plan to go with the
> distro-provided kernels than. To summarize, as long as I don't need to
> extensively modify my .config file to build a newer kernel, and as
> long as I can get a newer kernel than what the distro provides if I
> want to do that, I see no reason not to do it, that's my personal choice.
>
>> If everyone documented what they did as they did it and submitted it to
>> the site then we wouldn't have these problems to anywhere this degree.
>
> The problem here is that the information is scattered through the list
> archives, since there are a good number of us who post instructions on
> how to do this or that, a lot of times, more than once. This info is
> however not on the site, because Kirk has much better things to do
> than maintain the web pages, and nobody from the community, it seems,
> wants to take on the job, which I frankly can't altogether
> fault. maintaining a web site is a big job to do for one person,
> especially if it's done as a volunteer, and not as a paid
> employee. When you throw 2 or more people into the mix, say assigning
> person 1 to this section of the site, and person 2 to another section,
> this is a big responsibility for each of those people also, and has
> the potential to lead to a conflict, since person 1 may not like the
> way person 2 wants to do things.
>
> My own suggestion therefore would be to turn linux-speakup.org into a
> wiki, where those who want to help can do so, without having to take
> on the responsibility for the entire site, or a section, if they don't
> want to. I personally would have no problem expanding the wiki here,
> and there whenever I had the chance to do so, but I couldn't commit to
> be responsible for an entire site, or even a certain section of it, if
> I had to be the single person who made sure that it stays up to date
> all the time. Of course, it would be best if those who wanted to
> contribute got a login account, as opposed to a free-for-all, and
> ideally, there should be a team who would monitor the contents once a
> while for quality control, and accuracy. So Kirk, and others, how
> about something like apt-get install phpwiki (since I believe Kirk is
> running debian on linux-speakup.org), any thoughts?
>
> Greg
>
>
> - -- 
> 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.9 (GNU/Linux)
>
> iEYEARECAAYFAklloKoACgkQ7s9z/XlyUyCBuwCgutT4mgQX+SGj/+d/nouDRsHX
> GdQAn1SRAYG3GiJMRMaLHH105hVzBXPj
> =GdfM
> -----END PGP SIGNATURE-----
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Trouble Compiling modules/kernel
       [not found] <mailman.1.1231434002.20588.speakup@braille.uwo.ca>
@  ` Joe Kamphaus
  0 siblings, 0 replies; 11+ messages in thread
From: Joe Kamphaus @  UTC (permalink / raw)
  To: speakup

Thanks everyone.  I got it.

Never did get modules to compile but what I did was:

I upgraded my debian system to lenny and my kernel to 
linux-image-2.6.26-1-686 then I could install the modules
as they are a package in lenny: speakup-modules-2.6.26-1-686.deb

This has been working well for me.  It is nice to know that the
next stable release of debian will have speakup-modules as
a package.

Joe


^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~ UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 Trouble Compiling modules/kernel Joe Kamphaus
 ` Zachary Kline
   ` Samuel Thibault
     ` Nick Gawronski
     [not found]       ` <0A98E1637487415A909D77F28CEBB13A@bouncy>
     [not found]         ` <44E48C85D8FD47EAA0C4A4D7C36CA1B8@chihuahuad1>
           ` Kerry Hoath
             ` Nick Gawronski
               ` Gregory Nowak
               ` Kerry Hoath
                 ` Gregory Nowak
                   ` Nick Gawronski
     [not found] <mailman.1.1231434002.20588.speakup@braille.uwo.ca>
 ` Joe Kamphaus

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).