LINK : fatal error LNK1104

[jj2007]

I am trying to build a Masm64 SDK source. It worked fine some weeks or months ago, but now I get:

fatal error LNK1104: cannot open file 'C:\Windows\lnk{CE6654C6-F7A8-4A03-A613-4882B36AED51}.tmp'

Any idea what that could mean?

[Vortex]

Hi Jochen,

Did you try to use a different version of link.exe? You can also try Polink.

This link by fearless to download link.exe :

https://github.com/Data-Oriented-House/PortableBuildTools

[jj2007]

You can also try Polink

Hi Erol,

I tried several versions and Polink, same result.

[Vortex]

Hi Jochen,

Can you check your environment variable TMP and TEMP?

The linker is trying to create a temporary file in the directory indicated by the TMP environment variable. Make sure that TMP is set and that it points to a directory where the linker can create files and that has enough disk space.

https://stackoverflow.com/questions/6497233/what-does-this-error-message-mean-link-fatal-error-lnk1104-cannot-open-file

[jj2007]

Thanks, Erol. It turns out that RichMasm's intention to launch x64Dbg.exe was the problem. Shouldn't be, has worked a thousand times before, but there it is, without the int 3 it builds just fine...

[greenozon]

C:\Windows\lnk{CE6654C6-F7A8-4A03-A613-4882B36AED51}.tmp'

what is this mysterious file about?
why would liker search for it... 

[TimoVJL]

Temporary file.
Remember to put TMP environment variable to point writable user folder.
Also rc.exe or cvtres.exe can be problem.

[jj2007]

It turns out that RichMasm's intention to launch x64Dbg.exe was the problem.

tmp/temp folder is writable, of course. Tons of applications would complain if it wasn't writable.

[greenozon]

Temporary file.

OK, but why does it try to use C:\Windows as a temp dir??

I'd say this dir is special, at least you need admin rights (or more?) to be able to write into it..

eg:

[jj2007]

The problem has spontaneously disappeared

No idea what it was, but it happened only when the IDE tried to launch X64Dbg (which it does automagically if there is a lowercase int 3 somewhere in the source).

Now it works fine again, even with the int 3

why does it try to use C:\Windows as a temp dir??

You are right, this is the likely cause.