From:	Nebuchadnezzar <Nebuchadn AT NOSPAMquayles1 DOT demon DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Allegro problem!!
Date:	Fri, 25 Jun 1999 22:38:07 +0100
Message-ID:	<myms3EA$a$c3EwyV@quayles1.demon.co.uk>
References:	<37730D99 DOT 55368E1B AT quebectel DOT com>
	<eUFc3.305$k3 DOT 18998 AT news0 DOT telusplanet DOT net>
NNTP-Posting-Host:	quayles1.demon.co.uk
X-NNTP-Posting-Host:	quayles1.demon.co.uk:193.237.131.218
X-Trace:	news.demon.co.uk 930384199 nnrp-08:21234 NO-IDENT quayles1.demon.co.uk:193.237.131.218
X-Complaints-To:	abuse AT demon DOT net
MIME-Version:	1.0
X-Newsreader:	Turnpike (32) Trial Version 3.05 <X57Tfjb234BpiTjNHTJmyPlHTE>
Lines:	20
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

In article <eUFc3.305$k3 DOT 18998 AT news0 DOT telusplanet DOT net>, Sean Estey
<estey AT telusplanet DOT net> writes
>Make sure that in your source file you have "#include <allegro.h>" before
>main().  Also, be sure that you have liballeg.a installed in your djgpp/lib
>dir.  If you do not have this file in your allegro dir, you must run
>MAKE.EXE to create it.  Open a DOS prompt, change to your allegro dir, then
>type "make" (without the apostrophes of course).  Another possibility is
>that in RHIDE, (is you are using it), is that you didn't configure the
>allegro in your Options->libraries.  Type "alleg", then click the checkbox
>to do this.

or if you are using command line (I cannot stand RHIDE!) use:
        gcc foo.c -o foo.exe -lalleg
--____   ___  _   _ _ ____
 |  _ \ / _ \| | | | |  _ \    Email: nebuchadn AT quayles1 DOT demon DOT co DOT uk
 | | | | |_| | | | | | | | |     ICQ: 13313977
 | | | |  _  | |_| | | | | | Website: <NOT YET UP>
 | |_| | | | |\   /| | |_| |   Phone: 1100000101010110101001100011111
 |____/|_| |_| \_/ |_|____/   Career: C Programmer, Beer drinker
                          LIFE SUCKS!

- Raw text -