Mail Archives: djgpp/2002/08/05/06:18:05
Alex Vinokur <alexvn AT bigfoot DOT com> wrote:
> %cd C:\DJGPP\allegro\demo
> % gcc demo.c
> demo.c:22:21: allegro.h: No such file or directory (ENOENT)
This is your first real problem. It should have found that file on
its own. The reason it didn't is that you didn't properly read the
installation instructions of ALLEGRO any more than you did those of
GCC-3.1, it seems. If you had read them, you'ld have known that you
must 'make install' for the whole Allegro system before you can use
it.
> File demo.c has been changed
> Line
> #include "allegro.h"
> has been changed by the line
> #include "../include/allegro.h"
> ------------------------------------------
That's the wrong plan to fix that problem.
> % gcc demo.c
> In file included from ../include/allegro/base.h:26,
> from ../include/allegro.h:27,
> from demo.c:22:
> c:/djgpp/lib/gcc-lib/djgpp/3.1/include/stdarg.h:110: conflicting types for `va_list'
> c:/djgpp/include/stdio.h:35: previous declaration of `va_list'
This error is independant of the first, and it happens because you
didn't read the GCC-3.1 installation instructions (readme.djgpp, as
pointed out by Andris). Do what that chunk at the end of that README
says.
> So, how can I compile the Allegro demo ?
You first compile and install Allegro itself, then you'll be able to
compile the demo. It may even compile the demo for you as part of the
process --- I haven't looked into it for a while.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -