Re: es and gcc-2.5.0

[haahr@kaleida.com (Paul Haahr)]

>I don't claim that this is the best fix.  System prototypes don't belong
>in user code and es still has some scattered in its code,

agreed.  they are a work-around for things missing from header files,
only.

>but I didn't
>track them down and remove them since the following two fixes seem to be
>enough.

as to the fixes, i strongly recommend *not* applying the part which
removes the volatile void definition for noreturn.  (it sounds to me
as though fixproto should add volatile for exit and longjmp, since
i assume that fixproto is meant to be used in conjunction w/gcc.)

paul