delorie.com/archives/browse.cgi | search |
From: | "Travis" <slardy AT erols DOT com> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: allegro troubles |
Date: | Fri, 16 Jul 1999 22:32:36 -0400 |
Lines: | 17 |
Message-ID: | <7moq5p$5j3$1@autumn.news.rcn.net> |
References: | <378F9063 DOT 1D1 AT iquest DOT net> |
X-Trace: | i7Hv1v2DISAgB6EkVz+vLKulMPrs596gMgtoiu4G/7A= |
X-Complaints-To: | abuse AT rcn DOT com |
NNTP-Posting-Date: | 17 Jul 1999 02:35:37 GMT |
X-Newsreader: | Microsoft Outlook Express 4.72.3110.1 |
X-MimeOLE: | Produced By Microsoft MimeOLE V4.72.3110.3 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
all you have to do is when you compile attach the -lalleg to the compile command Jeremy Brown wrote in message <378F9063 DOT 1D1 AT iquest DOT net>... >Help, > > When I compile a program that uses allegro. I get an "undefined >reference to.." then it states the allegro part and some weird hex >valiesa and a file location in the allegro files. This is extremely odd >to me due to the fact that I when I made allegro the example programs >compiled without trouble. Please Help, > >Thanks, > >jeremy
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |