From: Deedra Waters <dmwaters@gentoo.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: 2.6.0 kernel won't compile
Date: Sat, 3 Jan 2004 17:05:24 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.58.0401031704010.3667@simba> (raw)
In-Reply-To: <20040103153047.GA12426@gmx.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alex, do not use genkernel. As I stated before, it does not work with speakup as of yet. You will need to do the standard compile yourself, like you would a normal kernel.
The reason genkernel does not work yet, is that some changes need to be made to it to handle speakup stuff.
On Sat, 3 Jan 2004, Alex Snow wrote:
> I'm trying to compile a 2.6.0 kernelas part of my gentoo install. I
> tried both the latest gentoo-dev-sources with speakup already patched in
> and patching it into the gentoo sources without speakup pre patched in.
> I get the following errors when genkernel runs make bzImage (taken from
> genkernel.log)
> drivers/built-in.o(.init.text+0x3fb1): In function `speakup_open':
> : undefined reference to `k_handler'
> drivers/built-in.o(.init.text+0x3fb6): In function `speakup_open':
> : undefined reference to `k_handler'
> drivers/built-in.o(.init.text+0x3fc5): In function `speakup_open':
> : undefined reference to `k_handler'
> drivers/built-in.o(.init.text+0x3fca): In function `speakup_open':
> : undefined reference to `k_handler'
> drivers/built-in.o(.init.text+0x3fd9): more undefined references to
> `k_handler'
> follow
> make: *** [vmlinux] Error 1
> c
>
- --
Gentoo Linux: Gentoo infrastructure, dmwaters@gentoo.org,
http://www.gentoo.org
Freenode staff member: dmwaters@freenode.net , http://www.freenode.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/90q5U5AGPOTGNc8RAsKOAJ4nzpN39SwRCy/2F4wzeRG4dqUxNgCeOIB2
cFCnDzjR781zRhlSiz/zKHQ=
=UqY9
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Alex Snow
` Deedra Waters [this message]
` Alex Snow
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=Pine.LNX.4.58.0401031704010.3667@simba \
--to=dmwaters@gentoo.org \
--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).