Silverfrost Forums

Welcome to our forums

SLINK64 fails when used as Library manager

21 Dec 2020 8:47 #26823

I'm getting the following error when trying to build my library.

***SLINK64 failure - abnormally large static library

Yes, it IS a big library. But I though, perhaps, SLINK64 would be able to handle the size.

Breaking it into 'chunks' is going to be interesting, as th4e current MAKEFILE is not organized in that way.

Bill

22 Dec 2020 6:29 #26824

Now, getting this error message. The list of modules is not yet complete, meaning there are more modules left to load.

Loading F:\CMASTERF95\RELEASE\WIN64\CFUNC\REFERENCE_SPECIAL.OBJ Loading F:\CMASTERF95\RELEASE\WIN64\CFUNC\REFERENCE_SPECIAL_WINDOWS.OBJ Loading F:\CMASTERF95\RELEASE\WIN64\CFUNC\REFSCR.OBJ Loading F:\CMASTERF95\RELEASE\WIN64\CFUNC\REFSCR_WINDOWS.OBJ Loading F:\CMASTERF95\RELEASE\WIN64\CFUNC\REGISTRY_HACK.OBJ ***Unknown Slink64 record type - 0 - probably corrupt object file

But which one; the last one?

23 Dec 2020 7:50 #26825

Bil

There is an FTN95 option /DELETE_OBJ_ON_ERROR that nowadays is ON by default. Previously the default lead to an object file of zero size.

Anyway, you could list (DIR *.obj) the object files to see if any have zero size.

Alternatively you could run SLINK64 in interactive mode where (I assume) the error will be reported when the object file is loaded.

23 Dec 2020 1:40 #26827

My bad.

The last listed object file was actually compiled as 32-bit (build process fail, my mistake). Before when I had that issue and used SLINK64, it told me the module was 32-bit. Not this time! So, compile it correctly, and that issue went away.

Bill

Please login to reply.