From: "Scott J. McCaughrin" Subject: Re: Error with compiling Newsgroups: comp.os.msdos.djgpp References: <86kabc$27m$1 AT news DOT netpower DOT no> <86kc5e$ell$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> Organization: CNI/Prairienet User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (SunOS/5.7 (sun4m)) Lines: 66 Message-ID: Date: Wed, 26 Jan 2000 06:44:50 GMT NNTP-Posting-Host: 192.17.3.4 X-Complaints-To: newsmgr AT prairienet DOT org X-Trace: firefly 948869090 192.17.3.4 (Wed, 26 Jan 2000 00:44:50 CST) NNTP-Posting-Date: Wed, 26 Jan 2000 00:44:50 CST To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hans-Bernhard Broeker wrote: : Netpower wrote: :> hi :> I always get an error when I try to compile a sample project. :> The error I get is: :> gcc.exe: installation problem, cannot exec 'cc1' : No such file or directory :> (ENOENT) : That's somewhat strange, indeed. So gcc seems to have found its : preprocessor, cpp.exe, and the include files, but no the compiler : itself. : You have not provided any details of how your DJGPP installation looks : like, but this raises one particular suspicion, in me: You may have : unpacked each .zip to its own subdirectory, instead of having them all : spit their contents directly below the main DJGPP directory. That does not sound like a satisfactory solution to me. Since you already have a `bin' directory under DJGPP and RHIDE has its own `bin', you will get a conflict from the unzipper (such as `winzip') requesting if you want to over-write. Now you may indeed want to merge the two bins, but that will make for a larger `bin' and you will no longer have the convenience of keeping RHIDE separate. This wouldn't be a problem if RHIDE had an automatic `uninstall' but it does not, and since it is not a mature IDE, I wouldn't recommend a merge of bins without an automatic uninstall. Of course, if RHIDE had an automatic install, these compile problems involving environments would not occur. I am rather surprised at this late date in the evolution of RHIDE that it is still such an amaeurish product from the standpoint of auto-install and documentation. : Check: in the name of the directory you added to your path, is there : any path component like 'gcc???b'? If so, that's your problem. Re-read : README.1st and unpack your whole DJGPP tree freshly, after deleting : the previous one. If RHIDE works with absolute pathnames in its environment, why should it have to be unpacked at the DJGPP level? I have never had an environment problem with any other DJGPP product and when I unpacked RSXNTJ, I was able to start developing with it immediately. (Likewise with CYGWIN.) : Otherwise, read up on 'bug reports' in the DJGPP FAQ, and send us the : info it requests you to. :> The compiler finds the include files and I suppose it also finds the lib :> file. I've included all include. lib paths in the Rhide IDE preferences :> dialog. : That should never be necessary. RHIDE doesn't need to be told where : the DJGPP includes are, because gcc is able to find them on its own, : if it was unpacked correctly. Yes, and that claim squares with all the RHIDE docs I have read. Yet (as I said above), I have never had an environment problem (such as inability to find includes) before RHIDE. Also -- based upon e-mail responses I have been getting -- I am not alone. Perhaps it would be nice if the next release of RHIDE got smart and -- instead of just complaining -- announced some remedy to the user as to how to fix up environments. Wading through layers of documentation doesn't cut it. : -- : Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) : Even if all the snow were burnt, ashes would remain.