-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, Apr 18, 2004 at 01:31:59PM -0400, Doug Sutherland wrote: > Stephen, > > This has been mind boggling to me, but I have been trying to compile Flite > for years! Every time a new rev of slackware came out, I tried compiling > Flite, and every time it failed. I always got an internal compiler error > or something like that. Recently, I finally did succeed compiling Flite, > but that was using an LFS (Linux From Scratch) build. One thing seems very > clear, that compilation of Flite really taxes a system. I think that some > of these errors might be due to heat problems. If there is anything you > can do to make your system run cooler, maybe try that. Perhaps removing > the case cover would do the trick. Anyone else have insight into this? I too have consistantly gotten those internal errors with no solution in site! I used to have 96 megs in this p200 machine and the first diphone module would always get the internal error. Then I stuck more memory (up to 256 megs) and that module compiled but then the diphone16 module got the same error after a long pause while compiling. I finally gave up on compiling that module by getting a precompiled version of that object. The rest of the package built without further incident. Now my problem is it did not build the shared objects necessary for the Speech Dispatcher so back to rebuilding flite again <sigh>. I wonder if I can keep the pre built version of diphone16 and still obtain the needed shared objects by rebuilding the rest of the package? - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAg1T/WSjv55S0LfERAp+5AKCs3KtBFhwlz6AZ3jixsQHRff4wcgCggOIk RrqWSZDEgPlgob1x7Zt+KyM= =os7y -----END PGP SIGNATURE-----
