StormC4 compilates not running on OS1.3

[thyslo]

Hi all,
the title says it all.

I've tested it with a little C program. When I compile it with StormC4 gcc compiler the binary is not running on OS 1.3. On OS 2.04 and above it is running, though.

But the same little C program compiled with SAS-C does run fine on OS 1.3.

What could be the reason for this?

[Minuous]

There are some hunk types that aren't supported on OS1.x, maybe the StormC linker is emitting these.

[thyslo]

Thank you, Minuous, that clears it

[phx]

Either that, or the startup code opens a V36+ library.
Does it crash/freeze or return an error code? If so, look at the error code. With unsupported hunks LoadSeg will just refuse starting the executable.

[thyslo]

Originally Posted by phx

Does it crash/freeze or return an error code?

It exits normally without an error code . It just does nothing. This happens regardless if started from Workbench or from CLI.

By the way / slightly off-topic: With StormC4 I'm not able to return an error code to the CLI. If I "return 20;" from main() the CLI takes this as an normal program termination. When I then type "Why" it states that the last command did not set an error code.

But I vaguely remember that I read somewhere that it is the normal behavior of StormC to not set return codes back to CLI at all.

[thomas]

The Why command does not examine the return code, it examines the IoErr code. What you return from the main() function can only be used in scripts with IF WARN/ERRROR/FAIL:

0 = OK
5 = WARN
10 = ERROR
20 = FAIL

To set the IoErr for Why in 1.3 you have to poke the value into the corresponding fields of the Process and CommandLineInterface structures.

[thyslo]

Many thanks, Thomas, for bringing clarity to this!