From: Roy Quitter <royq AT hotmail DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Compile problem
Date: Fri, 24 Jul 1998 23:21:24 -0500
Organization: ioNET Inc.
Lines: 24
Message-ID: <35B95D44.951AE22E@hotmail.com>
References: <35B9583A DOT 4CDC44E AT wpi DOT edu>
NNTP-Posting-Host: bartnas1-26.ionet.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Try putting allegro.h in your DJGPP \include subdirectory.  Also, once you
have compiled Allegro, make sure the liballeg.a file goes into DJGPP's \lib
directory.  By the way, when you compile Allegro, it should compile the test
files on its own (at least it did when I compiled it).

- Roy Quitter
   royq AT hotmail DOT com
   http://rquitter.home.ml.org/


Scott Ingram wrote:

> I am trying to compile one of the test files which come with allegro....
>
> Anyway, I type    gcc test.c -o test.exe -lalleg, just as specified in
> the
> allegro faq, however I get a message which says
> d:/djgpp/bin/ld.exe: cannot open -lalleg: No such file or directory
> (ENOENT)
> I have allegro.h residing in the same directory as test.c... I am
> confused.