Re: [Swarm-Support] Followup: found work-around for missing~/swarmarchiver.scm too

[Marcus G. Daniels]

Paul Johnson wrote:
> If those people who make gcc can cause havoc with a little thing like 
> the handling of the number 50, what devistation can they wreak when 
> they start talking about executable stacks, trampolines, and other 
> abstractions that I can barely grasp.
As you know, Swarm has a regression suite that's exists catch important 
changes to behavior.   Currently, the code in CVS passes "cd tests; make 
check" for me after a build on updated FC5/i386/gcc version 4.1.1 
20060525.   Does it for you?   If there are other constraints you think 
should always be satisfied, all that's needed is a Swarm program that 
exits with a non-zero value when something is measurably wrong...

Maybe the nil lispAppArchiver behavior has gone away with recent 
versions of GCC?

Marcus