Un*xcompiling in OS4

[AMC258]

Before I get started pulling my hair out trying to figure this one out does anyone have a quick answer?

What the heck is going wrong here:


and here:

[Hans_]

Data storage interrupt means that a program tried to read/write memory that does not belong to it. It could just be a stack overflow. Some of the configure scripts require a lot of stack. Try entering "stack 1000000" before running configure.

BTW, if you click more, you get more information about the crash. You can even save a detailed crash log.

Hans

[AMC258]

I had tried 200000, which I thought would be plenty.  Now, I tried 2000000, which doesn't help.

I have never found any useful information in the 'more' section of the GR.  Except the Ignore DSI button which rarely helps.  In fact, in this case, if I do that, every command in the script generates DSI errors.

Is there something wrong with my shell?  Of is this just a problem with OS4 Classic??

[AMC258]

My shell must be broken.  I can 'cd', and that's about it.  Everything else I do results in a DSI.  Right down to 'ls'.

[Hans_]

That's strange. There's a new version of abc-shell on os4depot (here. It's newer than the one in the SDK.

Hans

[AMC258]

Okay, this shell works.

But, now, I get a system deadlock at the checking C compiler's default output file part.
I'm starting to think it would just be easier to cross-compile this on a Sparc.