From: "Damian Yerrick" Newsgroups: comp.os.msdos.djgpp References: <82pe7k$6fr$1 AT solaris DOT cc DOT vt DOT edu> Subject: Re: Include and Library Files Error Lines: 47 Organization: Pin Eight Software X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Message-ID: X-Trace: +rqgtgzHfJ6GH5kDskshQ6xCzCbrI9sPcwHz60xSm4fMdJEriCCSnFcdcVfhKf5IHLb/VbtmhqKG!ZE2X/VSTkyPmqmiKdhBhY7zsbLGBqJEwk5Pn6C1c8nh4Mc15e5X3qcY/v73QCsQv2wk/upn3 X-Complaints-To: abuse AT gte DOT net X-Abuse-Info: Please be sure to forward a copy of ALL headers X-Abuse-Info: Otherwise we will be unable to process your complaint properly NNTP-Posting-Date: Fri, 10 Dec 1999 01:24:54 GMT Distribution: world Date: Fri, 10 Dec 1999 01:24:54 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Supertheta" wrote in message news:82pe7k$6fr$1 AT solaris DOT cc DOT vt DOT edu... > Hello, > > I am experiencing some difficulty while trying to compile a few C files > using DJGPP with RHIDE. Considering that I get the same error regardless of > whether I'm using GCC or compiling through RHIDE, I suspect the problem lies > with the former program (or, far more likely, my usage of it). Here is an > example of what happens: > > C:\djgpp\Divida>gcc *.c > In file included from bitmaps.c:1: > bitmaps.h:5: allegro.h: No such file or directory > In file included from divida.c:1: > divida.h:5: pc.h: No such file or directory > In file included from divida.c:1: > divida.h:7: allegro.h: No such file or directory > In file included from divida.h:8, > from divida.c:1: > bitmaps.h:5: allegro.h: No such file or directory > > > stdio.h, which is also included in the C files, is correctly found. > However, both pc.h and allegro.h You might not want pc.h if you're using Allegro. pc.h totally destroys portability. > are also in the c:\djgpp\include directory > (along with stdio.h), and yet GCC apparently cannot find them. Here is some > other relevant(?) data: > > Assuming I type in the \include and \lib directories into the appropiate > spaces provided in RHIDE, as well as adding the liballeg.a file to what > RHIDE passes to the linker, the C files do compile without error. However, > at link time, I get many (> 100?) unresolved external errors, mostly > regarding Allegro. Post the smallest source file that exhibits this error.