forums.silverfrost.com

DanRRight · Posted: Sun Mar 26, 2017 4:01 am Post subject: Can not LINK

Tried to compile my older program without any changes to it and got the error

mecej4 · Joined: 31 Oct 2006 Posts: 1886

You probably ran SLINK in interactive mode (The '$' command prompt is a sign of that) and, while entering linker directives, mistakenly entered a command meant for CMD.EXE.

DanRRight · Posted: Sun Mar 26, 2017 4:31 pm Post subject:

I compile using BAT files. So nothing changed at all. Such linker diagnostics like above is like a crime against humanity :/. Sourcer also may give such cryptic message containing just couple letters, I reported that in the past. Such problems difficult to reproduce, and when the reason is found users typically do not report that. The result is existence of devilry --hidden absurdly poisonous bugs capable ruining a day. Returned to FTN95 ver 7 and still have the same error !

People, Report every sneeze of your experience, and send to developers or here into newsgroup if you like to discuss this first any suggestions for improvement of all aspects of this compiler from installation to usage of everything, anything you like and dislike!!!!! Many are lazy to write and as a results things are not updated because developers may have different priorities and many things to do in their long lists.

My suggestion to the company - please make verboze mode with 10x more info to the user and make it more like a suggestion for troubleshooting. Please review all the messages from the linker and decipher all small ones. That will exclude such messages like above and will add you many devoted novices as thankful users who initially know nothing from your advanced terminology you have got after decades of detailed treating of Fortran Standard. Right now all the super laconic diagnostics is a rudiment from the computers circa 1960 as if there is not enough memory for making things clear

mecej4 · Joined: 31 Oct 2006 Posts: 1886

Please follow your own advice and post the batch file and any scripts used. Then we can investigate what happened and why you saw that cryptic message.

DanRRight · Posted: Mon Mar 27, 2017 5:53 am Post subject:

Isn't this true that I post already way more in this NG then enough? Smile

And in this particular case i'd prefer not to do that. There are absolutely nothing with the name SALF in BAT file's command line, no such filenames, no variables called SALF

Even more, I took the BAT file from another compiling computer and moved it to not working one and it does not compile sources in this computer.

Moving BAT file and the sources from compiling computer to not compiling one and running BAT file - all works fine. That means the compiler is OK and the problem might be in the source files or the folder. But no matter what the problem is such linker diagnostics is unacceptable

The only change on non-working computer in many months was installation of MS Vis Studio and MKL

PaulLaidler · Posted: Mon Mar 27, 2017 7:42 am Post subject:

Dan

Somehow SLINK is reading the command ??SALF??? instead of LOAD or one of the other valid commands.

The only other case that I can think of that is remotely similar is when a change from one OS to another changed the maximum number of characters allowed on a command line.

Hopefully you can provide some idea of the context for the failure so that we can help you.

mecej4 · Joined: 31 Oct 2006 Posts: 1886

DanRRight · Posted: Mon Mar 27, 2017 11:19 pm Post subject: Re:

PaulLaidler · Posted: Tue Mar 28, 2017 7:33 am Post subject:

Thanks Dan. It all makes sense now. Here is an extract from the help file about SLINK...

PaulLaidler · Posted: Tue Mar 28, 2017 8:37 am Post subject:

The next release of SLINK will trap the use of a Silverfrost 64 bit object file on the command link.

mecej4 · Joined: 31 Oct 2006 Posts: 1886

Slink64 already is capable of alerting the user when it is fed 32-bit OBJ files: