Game Development Community

Error executing link.exe

by Jared Hosh · in Torque Game Engine · 01/24/2002 (12:43 am) · 6 replies

greets to all,

I've recently moved, and in doing so changed the computer that I am compiling the torque source on. While setting up CVS, and MSVC++ was relatively problem free. I have, however, encountered a new problem when I try to compile on the new machine. I've installed MS Service Pack 5 for VC++, and I believe I've done everything else necessary to compile. I'm compiling Release 1.1.1 and I'm wondering what I might be missing. Here's the error:

Linking...
..\engine\collision\abstractPolyList.cc : fatal error LNK1136: invalid or corrupt file
Error executing link.exe.

survival_DEBUG.exe - 1 error(s), 0 warning(s).

Something to do with link.exe..what is this executable?

Any help is appreciated, thanks advanced.

#1
01/24/2002 (2:45 am)
Its the linker..it means you are having trouble linking....try doing a rebuild and see if that fixes the problem.

-Tim aka Spock
#2
01/24/2002 (1:54 pm)
Nope already tried that. I'm sure I need the linker but don't know how/where to get it.

Is it supposed to be part of VC++, SP5, one of the Torque tools, anything??
#3
01/29/2002 (2:29 am)
Your not missing the linker...if you look at your error it tells you what is wrong.

Quote:
..\engine\collision\abstractPolyList.cc : fatal error LNK1136: invalid or corrupt file

engine/collision/abstractPolyList.cc seems to be the problem...it says it is an invalid or corrupt file....try checking it out.
#4
01/30/2002 (4:39 pm)
Thanks very much for the help Tim.

I checked out engine/collision/abstractPolyList.cc, it's unmodified from it's origional state, so I doubt it's directly causing the problem. It is, however, the first file that gets run through the linker, and if the linker is misused it will be the one to create the error.

*bump*

I'm now using Release 1.1.1 checked out to a fresh dir, not modifying anything, but the error is still occuring. Has anyone else encountered this problem?
#5
02/13/2004 (5:07 pm)
That exact same problem happened to me when i tried to take the individual .dsp file of one of the tools, make a workspace for it, and then build it...

To fix it, use the existing Torque SDK.dsw and build the tools from there by changing the active configuration...
#6
02/13/2004 (6:06 pm)
[cough]2 year old thread[/cough]