[Matrixbob]

Come non detto, quella sopra è 1 marmellata.
Provo a vedere se ho intuito la vera installazione.

Con Cygwin installato.

Questo passaggio NON lo capisco a fondo, ma mi pare dica che vada compilato x primo la directory speech_tools:

All executables are linked to from speech_tools/bin and you should add
that to your PATH in order to use them.

Include files are speech_tools/include/ and the three generated
libraries are speech_tools/lib/libestools.a,
speech_tools/lib/libestbase.a and speech_tools/lib/libestring.a. For
most cases a three will be required.

Poi lancio appunto il $./configure che dovrebbe autoconfigurare il PC, ed in fine lancio il $make:

BUILDING IT
Configuration

All compile-time configuration for the system is done through GNU
configure. On most systems you can configure the system
by

unix$ ./configure

This creates the file config/config which for most machines will be
suitble. In some circumstances the default.s generated from this
may not be what you want and you may wish to edit this file.

For Linux we now fully support shared libraries and even recommend
them. However if you are going to do alot of development and don't
understand the consequences of shared libraries and getting
LD_LIBRARY_PATH correct (or what that is) we recommend you compile
unshared, the default. If you are going to simply run the speech tools
(and festival) then shared is a reasonable option. Uncomment the line
in the config file

# SHARED = 1

Shared support under Solaris is complete for all the speech tools. If
you need to exec festival scripts using a version of festival built
with shared libaries, you must either execute them from a featureful
shell (e.g. bash), install the shared libraries in a standard place or
explicitly set LD_LIBRARY_PATH. Solaris's standard shell doesn't
support script excutaiton of shells within shells.

Simple choices for common set ups are given near the top of this
file. But for some sub-systems you will also need to change pathnames
for external library support.

Compilation

Once you have configured config/config you can compile the system.

unix$ gmake

Note this must be GNU make, which may be called make on your system,
or gmake or gnumake. This will compile all library functions and all
the executables. If you wish to only compile the library itself then
use

unix$ gmake make_library

Note that if you compile with -g (uncommenting DEBUG = 1 is
config/config the library and the corresponding binaries will be
large. Particulary the executables, you will need in order of 150
megabytes to compile the system, if your C++ libraries are not
compiled as shared libraries. If you compile without -g the whole
library directory is about 12 megabytes on Linux (which has shared
libraries for libstdc++ or about 26 megabytes of Sparc Solaris (which
does not have a shared library libstdc++ by default). This is almost
entirely due to the size of the executables. C++ does not make small
binaries.

In general we have made the system compile with no warnings. However
for some compilers this has proved to be near impossible. SunOS
include files have a number of system declarations missing, so many
system functions (e.g. fprintf) will appear to be undeclared. Sun's CC
compiler also likes to complain about missing source for some code
even though the code exists within our system and is deliberately in
separate files ro make it modular.

To test the system after compilation

unix$ gmake test

Es di output dopo X minuti di compilazione: