Bugzilla Bug 205274

There is a small error in the way the Espeak GNOME Speech driver checks which
revision of the ESpeak API to use which causes it to call espeak_Initialize
incorrectly. I submitted it to upstream and it's in their SVN. See the URL for
the patch.

app-accessibility/gnome-speech-0.4.17 is affected too:
Making all in espeak
make[3]: Entering directory
`/var/tmp/portage/app-accessibility/gnome-speech-0.4.17/work/gnome-speech-0.4.17/drivers/espeak'
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../..
-I../../gnome-speech -DORBIT2=1 -pthread -I/usr/include/bonobo-activation-2.0
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/orbit-2.0
-I/usr/include/libbonobo-2.0   -Wall -Wmissing-prototypes -Wnested-externs
-Wpointer-arith -Wno-sign-compare  -I/usr/include/espeak    -march=athlon64 -O2
-pipe -fno-strict-aliasing -MT espeaksynthesisdriver.o -MD -MP -MF
.deps/espeaksynthesisdriver.Tpo -c -o espeaksynthesisdriver.o
espeaksynthesisdriver.c
espeaksynthesisdriver.c: In function ‘espeak_driverInit’:
espeaksynthesisdriver.c:174: error: too few arguments to function
‘espeak_Initialize’
make[3]: *** [espeaksynthesisdriver.o] Error 1
make[3]: Leaving directory
`/var/tmp/portage/app-accessibility/gnome-speech-0.4.17/work/gnome-speech-0.4.17/drivers/espeak'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/app-accessibility/gnome-speech-0.4.17/work/gnome-speech-0.4.17/drivers'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/app-accessibility/gnome-speech-0.4.17/work/gnome-speech-0.4.17'
make: *** [all] Error 2

Created an attachment (id=142059) [edit]
Patched ebuild

Ebuild that includes the patch - for those who need this before the next
version comes out

Created an attachment (id=142061) [edit]
Patch from previous link (modified for pathing)

The patch to go along with the ebuild.
Name it espeak.patch, and place into the gnome-speech/files directory

I have added 0.4.18 to the tree, which consists only of your patch, David.
However I have no means to really test this out of the box, as the espeak
driver appears to be not built right now for old keywording reasons. Should
that be handled in a separate bug?
Please mark as fixed or let us know if it can be marked as fixed, as I don't
have testing capabilities for this right now to be sure.

The keywording reason referred to in the previous comment is for bug #163285.
\
Now, the only arch that doesn't have keywords for espeak 1.36 is ia64.  Would
it be possible to have espeak be the default driver for the arches it is
keyworded for?  It needs to be >=espeak-1.36.

Thanks,

William