dholth@bluefish tmp $ saytime /usr/bin/saytime: line 2: /mnt/hdb7/portage/festival-1.4.3-r2/work/festival/bin/festival: No such file or directory dholth@bluefish tmp $ festival -v festival: Festival Speech Synthesis System: 1.4.3:release Jan 2003 Reproducible: Always Steps to Reproduce: 1. emerge festival 2. saytime 3. hearnothing This is Bug 41164 back from the dead. Severity: lame
There is a sed to change that script and another one with the correct executable; however it fails if the current directory (as detected by whoever writes the "exec" header at the top in the first place) differs from $WORKDIR. For example, my $WORKDIR is in /var/tmp but I have /var/tmp as a symlink to /tmp, which is where the script is pointing for bin/festival. So I suggest changing that to replace the *entire* path with /usr/bin/festival, or whatever is determined to be the correct path to install into. Even better would be to hunt down the code that appends those lines of headers (as the file in the example/ directory in the source tarball doesn't have that) and fix it in the first place.
works for me, when I use the speech-tools-1.2.3-r3.ebuild for Bug 91962. Festival ebuild however is a bit broken, as it depends on -r1 (should just depend on version, and not revision. It makes portage go a bit bananas for me)
Now I understand your problem. The build-script walks out the symlinks when it builds up its paths. speech-utils use the same method (and thereby will suffer by the same problems, aswell from the bugs in the current stable ebuild that fails to install the binaries in the first place).
This is nolonger relevent with 1.4.3-r3 as the saytime script is actually not installed to /usr/bin anymore. It's placed in the examples directory in the documentation, but it does work...
