Mail Archives: djgpp/2005/05/26/05:46:46
pino <asd AT sd DOT asd> wrote:
> Thankl you but I dont have documentation.
Wrong. If you have gcc, you have its documentation, too --- it's in
the same zip file. And no, you cannot usefully expect to be able to
use a tool as complex and powerful as GCC without its documentation.
> if I compile the file future.c (that has inside the #include<<normdist.h>>)
[...]
> futures.C:4:20: error: normdist: nosuch file or directory (ENOENT)
You're contradicting yourself. First of all, the #include cannot
actually be what you said it is (becaue <<name>> is not an allowed
form of #include argument). Second, the name reported is not the one
you say you have in the #include statement: the .h has mysteriously
vanished.
> c:\ gpp -o c:\futures.exe c:\futures.c
A third discrepancy: the error message mentions futures.C (upper-case
C), the command line has a lower-case futures.c. While this makes no
big difference to DOS, it does to GCC.
You really have to be more precise in reporting what you did, and what
the results were. Copy-paste usually does the trick.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -