UFO:Alien Invasion

Technical support => Windows => Topic started by: Kaerius on September 05, 2009, 06:28:09 pm

Title: Undefined reference to mcount - compiling errors.
Post by: Kaerius on September 05, 2009, 06:28:09 pm
I have no idea what's causing these... but I just installed the newest codeblocks, and set up all the paths and stuff, did everything the wiki told me for setting it up, including adding directories to my windows path and copying dlls to UFO:AI dir.

Code: [Select]
||=== ufo2map, windows ===|
.objs\ufo2map\src\common\ioapi.o||In function `fopen_file_func':|
C:\Program\UFO-SVN\src\common\ioapi.c|72|undefined reference to `mcount'|
.objs\ufo2map\src\common\ioapi.o||In function `fread_file_func':|
C:\Program\UFO-SVN\src\common\ioapi.c|95|undefined reference to `mcount'|
.objs\ufo2map\src\common\ioapi.o||In function `fwrite_file_func':|
C:\Program\UFO-SVN\src\common\ioapi.c|107|undefined reference to `mcount'|
.objs\ufo2map\src\common\ioapi.o||In function `ftell_file_func':|
C:\Program\UFO-SVN\src\common\ioapi.c|116|undefined reference to `mcount'|
.objs\ufo2map\src\common\ioapi.o||In function `fseek_file_func':|
C:\Program\UFO-SVN\src\common\ioapi.c|127|undefined reference to `mcount'|
.objs\ufo2map\src\common\ioapi.o:C:\Program\UFO-SVN\src\common\ioapi.c|151|more undefined references to `mcount' follow|
||=== Build finished: 6 errors, 0 warnings ===|
Title: Re: Undefined reference to mcount - compiling errors.
Post by: Mattn on September 05, 2009, 09:17:40 pm
run a clean before - you maybe mixed debug and release builds
Title: Re: Undefined reference to mcount - compiling errors.
Post by: Kaerius on September 06, 2009, 03:46:08 pm
Actually I wasn't mixing, it was just so long since I last updated my SVN that I guess the effect was similar...

Cleaned out the folder and reupdating now...
Title: Re: Undefined reference to mcount - compiling errors.
Post by: harish96 on February 04, 2010, 11:59:27 am
This may be caused due to '-pg' option during build. '-pg' is used to generate profile information. If the target doesn't support this feature you may get this kind of error.