Xref: news-dnh.mv.net comp.os.msdos.djgpp:2465
Path: news-dnh.mv.net!mv!news.sprintlink.net!newsfeed.internetmci.com!news.mathworks.com!news.kei.com!eff!news.duke.edu!godot.cc.duq.edu!nntp.club.cc.cmu.edu!cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!newsfeed.rice.edu!rice!news!sandmann
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Coprocessor nuisance...
Date: Sat, 07 Oct 1995 11:04:00 CDT
Organization: Rice University, Houston, Texas
Lines: 12
References: <DG1v9q DOT 2LJ AT jade DOT mv DOT net>
Reply-To: sandmann AT clio DOT rice DOT edu
Nntp-Posting-Host: clio.rice.edu
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

> cc1 is called.  Cc1 works fine for a little bit, but then it dies
> with the message "Coprocessor not found."  Any help on this would
> be appreciated, and if anyone needs any additional info about
> what's going on, just ask. (;

I'm assuming you are using V2 beta 3.  I have seen a similar reports before,
so there is probably a real problem with FPU-less machines.  The first 
thing I would suggest is making sure all the exe images being run have a 
date more recent than Aug 1, and there are no V1.x images in the path which
may be run.  If the problem still exists, someone with a FPU-less machine
will need to debug this, since everyone on the development team has a system
with an FPU.  Is CC1 the only image which shows this problem?