Mail Archives: djgpp/1997/03/13/01:23:06
macko AT ix DOT netcom DOT com wrote:
: Thank you very much for your help.
: Of course I have read readme.1st. The problem is that these commands
: work with certain files only, do not work with others. Unable to
: compile for example the test codes those were recommended to us by the
: instructor to try first. According to him these files can test if the
: compiler is able to handle exceptions and templates, which is a must.
: For IDE I downloaded and installed Emacs first, then Rhide. I was
: unable to use emacs at all, rhide gives me different error messages.
: E.g. I open q2.txt in rhide then try to compile it says: "Don't know
: how to build q2.o from q2.txt. I guess, it is because it can not
: handle *.txt, so I rename it to q2.c then the message is "error:
: iostream.h: no such file or directory (ENOENT)".
: Could you give me more suggestions, please.
In addition to what Eli said, can I suggest that you check that you
unpacked all the files required for C++ compilation, and not just those
for C compilation? Specifically, to compile any serious C++ programs you
need to download lgp272b.zip and gpp2721b.zip (IIRC), both from the v2gnu
section of the FTP distribution.
If you have already done this, I suggest that you get hold of John
Aldrich's DJVERIFY, which is a utility that checks your installation for
common errors and produces a report you can post here which will give
readers more information about your system setup, so that they can
identify the problem more easily.
ftp ftp.delorie.com
cd /pub/djgpp/alpha
get vrfy033a.zip
It is in alpha at the moment, and some features don't work, but it will
still check the most common problems and produce a report. If you don't
want to or can't download this, you can use RHIDE's Bug Report (on the
left-hand menu) to generate a similar report, although this won't attempt
to troubleshoot the problem for you.
--
George Foot <mert0407 AT sable DOT ox DOT ac DOT uk>
Merton College, Oxford
- Raw text -