Re: emacspeak finally running

Another tip that was posted to this list a while ago, that I'll try next 
time I update Emacspeak, unless I switch to the method Tim recommends, 
is the following:

Try running
touch servers/linux-outloud/atcleci.so
from the root of the emacspeak source tree.
make will be fooled into installing a dummy atcleci.so.  That's fine,
since you don't have outloud on that machine.

Chris posted this.

On 02/03/17 18:01, Jude DaShiell wrote:
> Thanks Christopher, I'll find that and adjust and can probably have
> emacspeak living under builds without so much major surgery that way.
> On Thu, 2 Mar 2017, Christopher Chaltain wrote:
>
>> Date: Thu, 2 Mar 2017 18:45:57
>> From: Christopher Chaltain <[email protected]>
>> Reply-To: Linux for blind general discussion <[email protected]>
>> To: Linux for blind general discussion <[email protected]>
>> Subject: Re: emacspeak finally running
>>
>> To get around the Makefile trying to compile the server for Outloud, I
>> just commented out the following line in the Makefile:
>>
>> #     $(INSTALL)  -m 755 ${OUTLOUD}  $(libdir)/servers/linux-outloud
>>
>> On 02/03/17 15:25, 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
>>> [email protected]
>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>>
>

-- 
Christopher (CJ)
chaltain at Gmail