From: rmann@rmisp.net
To: speakup@braille.uwo.ca
Subject: Re: festival module for Speakup
Date: Mon, 31 Mar 2003 08:12:14 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0303310811470.11495-100000@rmnet> (raw)
In-Reply-To: <3E880966.6000900@deis.unibo.it>
What is the URL for the updated tarball? Thanks.
Ryan Mann
On Mon, 31 Mar 2003, Matteo Fasanella wrote:
> rmann@rmisp.net wrote:
>
> >Has anybody actually gotten that festival module to work? I checked out
> >Speakup from CVS then did the following.
> >1. untared speakup-festival.tar into a directory called sp-fest.
> >2. changed to the usr sub directory
> >3. did cp -r include /usr/include, then cp -r src /usr/src.
> >5. changed to the sp-fest/speakup directory and did "cp *
> >/usr/src/linux/drivers/char/speakup"
> >6. did "make oldconfig" and answered "y" to the Festival module.
> >7. make dep, make clean, then make bzimage
> >
> >make bzImage was where the error was.
> > Here is some of the output.
> >
> >gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
> >-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer
> >-pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc -iwithprefix
> >include -DKBUILD_BASENAME=speakup_drvcommon -c -o speakup_drvcommon.o
> >speakup_drvcommon.c
> >speakup_drvcommon.c: In function `synth_request_region':
> >speakup_drvcommon.c:136: parse error before `struct'
> >speakup_drvcommon.c:144: `parent' undeclared (first use in this function)
> >speakup_drvcommon.c:144: (Each undeclared identifier is reported only once
> >speakup_drvcommon.c:144: for each function it appears in.)
> >make[4]: *** [speakup_drvcommon.o] Error 1
> >make[4]: Leaving directory `/usr/src/linux/drivers/char/speakup'
> >make[3]: *** [first_rule] Error 2
> >make[3]: Leaving directory `/usr/src/linux/drivers/char/speakup'
> >make[2]: *** [_subdir_speakup] Error 2
> >make[2]: Leaving directory `/usr/src/linux/drivers/char'
> >make[1]: *** [_subdir_char] Error 2
> >make[1]: Leaving directory `/usr/src/linux/drivers'
> >make: *** [_dir_drivers] Error 2
> >
> >Thanks.
> >
> >Ryan Mann
> >
> >
>
> It seems like a "missing include" error; from point 5, it seems you used
> the "first" version of tarball; but after some posting on the list, I
> made a second version of tarball, with some "corrections".
> Try with it, and let me know...
>
> Matteo
>
>
>
>
> _______________________________________________
> 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: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
rmann
` Matteo Fasanella
` rmann [this message]
` Matteo Fasanella
-- strict thread matches above, loose matches on Subject: below --
Festival Module " Matteo Fasanella
` Owen Patrick Smith
` Buddy Brannan
` Matteo Fasanella
` Buddy Brannan
` Matteo Fasanella
` Jacob Schmude
` Matteo Fasanella
` Buddy Brannan
` Matteo Fasanella
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.44.0303310811470.11495-100000@rmnet \
--to=rmann@rmisp.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).