From:	Jason Green <news AT jgreen4 DOT fsnet DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Allegro programs won't compile
Date:	Sun, 28 Jan 2001 11:04:56 +0000
Organization:	Customer of Energis Squared
Lines:	18
Message-ID:	<0lu77t073qrjt29htsv6j6hj2e3gdoamsl@4ax.com>
References:	<001401c088bd$9a1d93c0$7d012f04 AT rudycomputer>
NNTP-Posting-Host:	modem-81.lithium.dialup.pol.co.uk
Mime-Version:	1.0
X-Trace:	newsg2.svr.pol.co.uk 980679910 23975 62.136.2.81 (28 Jan 2001 11:05:10 GMT)
NNTP-Posting-Date:	28 Jan 2001 11:05:10 GMT
X-Complaints-To:	abuse AT theplanet DOT net
X-Newsreader:	Forte Agent 1.7/32.534
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Please don't post to this group in HTML, and please set your line
length to something more reasonable.

"rujasu" <rujasu AT netzero DOT net> wrote:

> Whenever I try to compile a C program using allegro.h with GCC.EXE, 
> the compiler says "f:/djgpp/tmp\(some bizzare filename):(name of 
> program to be compiled): undefined reference to (function from 
> allegro.h)`' once for Allegro every function used in the program. The 
> Allegro example programs won't compile either, even though they 
> compiled fine when I ran make & the executables work fine, so I don't 
> think that my code is the culprit.  When I compile out of RHIDE, it 
> works fine, but I can't create an executable file through RHIDE.  What 
> is my problem?

Perhaps you are not linking with the library, you need -lalleg at the
end of the command line.  This is explained in the FAQ section 8.8
"Undefined references when linking programs".

- Raw text -