public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: William Hubbs <w.d.hubbs@gmail.com>
To: speakup@braille.uwo.ca
Subject: Re: Compilation Error (soft synth related?)
Date: Fri, 13 Jun 2008 08:27:39 -0500	[thread overview]
Message-ID: <20080613132739.GA15072@linux1> (raw)
In-Reply-To: <Pine.LNX.4.64.0806130052220.21849@gube.gnpgvphfpbzzhavpngvbaf.arg>

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

Hi Luke,

please update your speakup tree and try this again.  It should be fixed,
but if it isn't, let me know.

Thanks,

William

On Fri, Jun 13, 2008 at 12:55:25AM -0400, luke wrote:
> While compiling kernel version 2.6.24.7, from a speakup tree acquired on 
> Thursday morning from the git mirror, I get this a while after the make 
> bzImage.  Interestingly, I didn't get this when compiling a 2.6.18 kernel 
> with the same speakup tree, and different kernel options.
> 
>   CC      drivers/char/speakup/speakup_soft.o
>   CC      drivers/char/speakup/buffers.o
>   CC      drivers/char/speakup/devsynth.o
> drivers/char/speakup/devsynth.c: In function ?
> speakup_file_write?
> :
> drivers/char/speakup/devsynth.c:27: error: implicit declaration of 
> function ?
> copy_from_user?
> 
> make[3]: *** [drivers/char/speakup/devsynth.o] Error 1
> make[2]: *** [drivers/char/speakup] Error 2
> make[1]: *** [drivers/char] Error 2
> make: *** [drivers] Error 2
> 
> Any thoughts?
> 
> Regards,
> 
> Luke
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkhSdcsACgkQblQW9DDEZTihbgCggNiiPflL1BrZW4STIxt5DQwq
EBMAn2u/5TSNbVyITafmnhqwanlHJnof
=tCxj
-----END PGP SIGNATURE-----

      reply	other threads:[~ UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 luke
 ` William Hubbs [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=20080613132739.GA15072@linux1 \
    --to=w.d.hubbs@gmail.com \
    --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).