Date: Wed, 27 Nov 1996 08:46:47 +0200 (IST) From: Eli Zaretskii To: jdcarey AT netcomuk DOT co DOT uk Cc: djgpp AT delorie DOT com Subject: Re: MAKEing Allegro 2.1 - Humble request for help In-Reply-To: <329C085E.2A2E@netcomuk.co.uk> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 27 Nov 1996 jdcarey AT netcomuk DOT co DOT uk wrote: > I just downloaded Allegro 2.1 and tried to make it. > What I got in return is attached below. > > gcc -I. -Isrc -Wall -m486 -O3 -o obj/adlib.o -c src/adlib.c > src/internal.h: In function `enter_critical': > In file included from src/adlib.c:27: > src/internal.h:37: `__dpmi_regs' undeclared (first use this function) > > I cannot find the offending functions in the DJGPP 'info', > and apparently no-one else has had this problem. `__dpmi_regs' is not a function, it's a typedef for a struct. It is declared on which is included by allegro.h, which is in turn included by src/adlib.c *before* src/internal.h. So I don't understand how come you have this problem, unless there were some other error/warning messages during the compilation that you deleted before posting your message (you should always post *all* the messages you get). > What can I do? Try to understand why didn't GCC see or allegro.h. If you can't figure it out, post more info. The best way to do it is to redirect all output to a file, like so: redir -o problem.txt -eo <...the compilation command here...> Put the command line that you used in your original attempt to compile Allegro instead of the bracketed part above, then post the file `problem.txt' *in its entirety*, even if it is very large.