Message-Id:	<199710301806.TAA02169@free.polbox.pl>
From:	"=?ISO-8859-2?Q?Robert_Darmochwa=B3?=" <kacmajor AT polbox DOT com>
To:	"DJGPP Mailing List" <djgpp AT delorie DOT com>
Subject:	99% sure bug.But i dunno if it's allegro or djgpp's fault..
Date:	Thu, 30 Oct 1997 07:10:04 +0100
MIME-Version:	1.0

So here it is ..
my frogram has  for exemple 3 files.(accurately it has much more, but it's
a example)

let it be:
main.c
foo.c
liballeg.a


some uforulz() function from file foo.c calls allegoro's func 
play_memory_fli like:

uforulz()
{
 play_memory_fli(lameani,screen,0,NULL);
}

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...

and here's most exciting part:

when i add a line to my main() function, stored in file main.c
which calls play_memory_fli too, it compiles then...

for example :

main()
{
  uforulz();
  return;
}                     //gcc says unresolved external in file foo.c func
uforulz()
      
main()
{
  uforulz();
  return;
  play_memory_fli(blah,blah,blah,blah)
}   // in this case gcc compiles correctly!! notice that play_memory_fli 
 is after return, so this is a dead code...but without that gcc cannot 
find P_M_F function at all....


       

- Raw text -