emacspeak finally running

The Wolf hank.smith966 at gmail.com
Thu Mar 2 21:30:56 UTC 2017

sounds like more trouble then it is worth

how is a beginner to linux supposed to understand all of this tech jargon.
not trying to upset any one but am curious.

On 3/2/2017 2:25 PM, Jude DaShiell wrote:
> What a mess!
> I had to do a whole lot of things way outside documentation to get 
> this application running.
> First, since outloud kept on insisting on compiling I did major 
> surgery on the emacspeak/servers directory and erased anything that 
> wasn't linux-espeak.  I think emacspeak was getting confused in that 
> directory.
> After make config and make emacspeak and copying the directory and all 
> subdirectories that had emacspeak-setup.el to 
> /usr/share/emacs/site-lisp and adding an (add-list "load-path 
> statement above emacspeak-setup.el line as suggested in the info page, 
> I had to start emacs which complained it couldn't find 
> emacspeak-setup.el after being loaded and then I did a load-library 
> <ret> emacspeak-setup.el <ret> and heard emacspeak finally do 
> something close to its normal startup including the organ music.
> Now I'm going to have to investigate to find out why the 
> /usr/share/emacs/site-lisp/lisp/lisp/ path wasn't liked by emacs.
> I think the Make file in the emacspeak directory inadvertently had its 
> exit statements stripped out if exit is even a valid Makefile command 
> because the stanza just below emacspeak: was you guessed it outloud:.  
> My reading of Makefile code isn't all that professional but all I 
> found was a blank line between the end of the emacspeak stanza and the 
> outloud: stanza and unless that's a valid form of exit it's entirely 
> understandable why outloud kept building even though viavoice wasn't 
> on the machine at the time. Let's not even talk about searching for 
> existing server software before building anything, that will add too 
> much complexity to the Makefile most likely.
> Now I'm going to go study Makefile syntax and see if I can learn 
> enough to figure out some valid fixes for this one.
> -- 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list at redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list

More information about the Blinux-list mailing list