From:	Vic <tudor AT cam DOT org>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: 99% sure bug.But i dunno if it's allegro or djgpp's fault..
Date:	Thu, 30 Oct 1997 19:23:26 -0500
Organization:	Communications Accessibles Montreal, Quebec Canada
Lines:	28
Message-ID:	<345924FE.7027@cam.org>
References:	<199710301806 DOT TAA02169 AT free DOT polbox DOT pl>
NNTP-Posting-Host:	dynppp-140.hip.cam.org
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

=?ISO-8859-2?Q?Robert_Darmochwa=B3?= wrote:
Hey, nice name!
> 
> So here it is ..
> my frogram 
<lame racist joke>
Your *frog*ram? What are you, french?
</lame racist joke>
> everything seems t be ok, but when i ling gcc -g main.c liballeg.a foo.o,
> after compiling foo.c off course (gcc -c foo.c)
> gcc says: unresolved external play_memory_fli...
Frankly? I just think he doesn't like you... 
> and here's most exciting part:
Wow! 
> when i add a line to my main() function, stored in file main.c
> which calls play_memory_fli too, it compiles then...
Really? Like, DUH.
 
Think about this: The libs must be linked LAST. Otherwise you link a
file AFTER you link the lib and you will get errors like that.
try this for a change:
gcc -g main.c foo.o liballeg.a .The lib LAST. I'll work, trust me. 

not in my nicest moods,
-- 
--> http://www.cam.org/~tudor <--
Go ahead and build another Messiah
We dig another grave...

- Raw text -