I haven't had any errors since my last build from git but the git version can be a fast moving target too. That path to emacspeak-setup.el doesn't sound right to me. /lisp doesn't exist on our systems. It should be going to /usr/share/emacs/24.4/lisp... Also, the current version of tcl on my system and what is required by recent versions of emacspeak is 8.6.3. I'm not sure the complete range of tcl versions that emacspeak will work with but then there are the tclx issues and that has to be matched up properly. Too bad we can't get away from tcl and related things; might make things easier to manage. On Sat, Mar 14, 2015 at 05:36:59PM -0400, D.J.J. Ring, Jr. wrote: > I am using Gilles Casse's script for voxin users which installs and > configures emacspeak 38.0-1 so that it comes up talking. > > Some of the new users have difficulty with programmer's English and Unix > common knowledge base which they probably haven't acquired yet. > > I see when I try to upgrade my system, tcl 8.4-1 wants to update to 8.4-2 > but 8.4-2 in not compatible with voxin. > > Additionally, emacspeak 38.0-1 wants to upgrade to 41.0-1, but doing so > makes emacspeak no longer speak, as I believe it needs tcl 8.4-2. > > So for the moment, I am back to emacspeak 38.0-1 and tcl 8.4-1 and I am > using emacs 24.4-2 > . > Now that I know I can run Gille's scripts to uninstall voxin (IBM TTS / > Outloud) and then use his script to uninstall emacspeak, I will see if I > can get your emacspeak-git running. > > With the git version, I get the error Cannot open load file: no such file > or directory, /lisp/emacspeak-setup.el I am using tcl 8.4-1 and emacs > 24.4-2 and emacspeak-git (for this try). > > Best to you, > > David > > > > > > On Sat, Mar 14, 2015 at 4:34 PM, Steve Holmes <steve@xxxxxxxxxxx> wrote: > > > I wasn't aware of changes to tclx. I have it already installed on my > > system from before so never gave it a thought when building > > emacspeak-git package. You might leave comments in AUR for the tclx > > package and see if the developer can update the PKGBUILD if needed. If > > you built tclx from the AUR package, that surprises me that pacman > > didn't see that as an installed package, tclx. I assume you installed > > the tclx from the built package? > > > > Oh, by your message, it looks like you didn't use a package to build > > tclx. This would definitely not list tclx as a satisfied > > dependency. We need to get the tclx package from AUR working > > properlyh. I'll take a look at the AUR package for tclx and contact > > the package owner as appropriate. > > > > On Sat, Mar 14, 2015 at 06:07:15AM -0400, Jude DaShiell wrote: > > > The package does not build since it insists on building a tclx package > > > from aur and that tclx package is outdated and the tclx package itself > > > cannot build. > > > I downloaded the latest tclx source code and built it on this system then > > > ran the emacspeak.git package install again and the package failed to > > > recognize that tclx was installed on this system. One thing that has me > > > worried about this latest tclx install is that it failed in make test so > > I > > > don't know if this latest version will or will not crash emacspeak. I > > > tried enabling 64bit support but tclx doesn't have the magic for amd64 > > > computers now so that was disabled in configuration step. This system > > has > > > speakup running espeak running the sound card for now. > > > > > > > > > > > ----------------------------------------------------------------------------- > > > To unsubscribe from the emacspeak list or change your address on the > > > emacspeak list send mail to "emacspeak-request@xxxxxxxxxxx" with a > > > subject of "unsubscribe" or "help". > > > > > > > > > ----------------------------------------------------------------------------- > > To unsubscribe from the emacspeak list or change your address on the > > emacspeak list send mail to "emacspeak-request@xxxxxxxxxxx" with a > > subject of "unsubscribe" or "help". > > > >
|All Past Years |Current Year|
If you have questions about this archive or had problems using it, please contact us.