From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from scaup.mail.pas.earthlink.net ([207.217.120.49]) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1AaiVH-0008Ck-00 for ; Sun, 28 Dec 2003 16:31:16 -0500 Received: from sdn-ap-018ilchicp0308.dialsprint.net ([65.176.177.54] helo=noneflzmskjmuf) by scaup.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 1AaiVE-0005vL-00 for speakup@braille.uwo.ca; Sun, 28 Dec 2003 13:31:12 -0800 Message-ID: <003c01c3cd89$ea998890$36b1b041@noneflzmskjmuf> From: "Tom and Esther Ward" To: "Speakup is a screen review system for Linux." References: <20031228071635.GA2564@lnx3.holmesgrown.com> Date: Sun, 28 Dec 2003 16:31:10 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: Re: Compiling Flite X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.3 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: Speakup is a screen review system for Linux. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Dec 2003 21:31:16 -0000 Hi, I have seen similar errors on Mandrake 9.2. I'm not exactly sure what the problem is that causes this though. The only way I was able to get flite 1.2 going was to compile it on a Red hat 9.0 partition, tar the directory, and copy it to Mandrake 9.2. Which was definately not the way I wanted to get flite working with eemacspeak and yasr. Hth. ----- Original Message ----- From: "Steve Holmes" To: Sent: Sunday, December 28, 2003 2:16 AM Subject: Compiling Flite > anyone try compiling flite lately? I'm working with flite 1.2 taken > from the original CMU website and I'm using the gcc compiler that > comes with Slackware 9.1; I believe it is gcc 3.2.3. > > What happens after compiling a bunch of its components, I get "gcc > internal error killed program cc1." Then it asks me to fill out a bug > report. I will probably do that tomorrow if I can't figure this out. > I got this once on another machine while compiling a kernel. I > re-extracted the tar file for the kernel, re configed it and > recompiled and all that stuff and the error did not re-occur for the > kernel. But with Flite, I tried untaring it again and recompiling > after the .configure and I keep getting the same internal error. > > Anyone else experiencing this? > -- > HolmesGrown Solutions > The best solutions for the best price! > http://ld.net/?holmesgrown > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup >