Date: Tue, 3 Sep 1996 08:36:39 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Potato Pigeon <potatopigeon AT easynet DOT co DOT uk>
Cc: djgpp AT delorie DOT com
Subject: Re: UNDEFINED ERRORS
In-Reply-To: <50717d$588@cherry.easynet.co.uk>
Message-Id: <Pine.SUN.3.91.960903082413.24344N-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Fri, 30 Aug 1996, Potato Pigeon wrote:

> Reading specs from c:/cprog/lib\specs
> gcc version 2.7.2
>  c:/cprog/bin\cpp.exe -lang-c -v -undef -D__GNUC__=2
> -D__GNUC_MINOR__=7 -Dunix -Di386 -DGO32 -DMSDOS -DDJGPP=2
> -DDJGPP_MINOR=0 -D__unix__ -D__i386__ -D__GO32__ -D__MSDOS__
> -D__DJGPP__=2 -D__DJGPP_MINOR__=0 -D__unix -D__i386 -D__GO32 -D__MSDOS
> -D__DJGPP=2 -D__DJGPP_MINOR=0 -Wall ex1.c c:/cprog/tmp\ccbaaaaa
> GNU CPP version 2.7.2 (80386, BSD syntax)
> #include "..." search starts here:
> #include <...> search starts here:
>  c:/cprog/include
>  c:/cprog/contrib/grx20/include

This tells that your DJGPP environment variable is set OK.

> gfx_modex, for example, is defined in the allegro.h file and is
> included in the demo.c program, so I cant understand why gcc or the
> linker doesnt know what gfx_modex is!

The fact that a function prototype appears in the header file is
irrelevant to your problem.  The linker wants to find the function's
*code*, not its *prototype*.  So what you need is a file `liballeg.a' that
includes the compiled code of these functions.  The Allegro distribution
comes only with the sources, so you should have compiled the sources to
produce `liballeg.a' as per the installation instructions included with
the package.  Did you compile them and installed `liballeg.a' in your lib/
subdirectory?