Golink goes wrong when linking Jwasm 64 bits file.

[PauloH]

    Hi,

I did a 64 bits program using Jwasm and tried to link it with golink without success, but with polink the linking process is successfull.

I use Vista 64 home premium.

The project (for RadAsm) is attached. There are two build.bat files to do the compilation. Perhaps you have to change the path inside them.

My question is: what am I doing wrong? Is there any switch I'm missing?

I want to use golink to be free of .lib files!

Thanks for your help.

Paulo H. Duarte

PS.: Golink+Jwasm 32 bits programming goes without any issue!

[wjr]

If you zip up your DialogAsMain64.obj and DialogAsMain64.res it would be easier for me to try to duplicate any errors or difficulties that you encountered using GoLink...

[PauloH]

Thanks for your answer, wjr.
This new attachment has the .obj and .res files you asked for.

Kind regards,

Paulo H. Duarte

[wjr]

The easier part - to answer your questions, you are not missing a switch and are not doing anything wrong. However, I tend to use the following order to build:

Code Select Expand

GoLink.exe DialogAsMain64.obj DialogAsMain64.res kernel32.dll user32.dll

The not so easy part would now be up to Jeremy. Although the JWasm obj IMAGE_RELOCATION and SYMBOL_TABLE look fine, something still has thrown GoLink off with the call offsets to the IAT. The partial calculation would appear to omit an offset taking into account the size of the Jump Table and IMPORT Descriptors, and a 2 is used which looks like it should multiply a 4 giving instead multiples of 8 to point into the IMPORT Address Table...

[PauloH]

Hi,
I found the following: using the jWasm includes, leads to the error I've described in my first post. Now, I made a new project and this one doesn't use the jWasm includes and the compilation goes ok.
If anyone has some interest, the attachment contains the project and a build.bat. Please, correct your paths in the build. bat as you want.

Thanks,

Paulo H.