Subject: Re: SV4 ??

From: Mark Crispin <[email-masked]>
Date: Tue, 20 Dec 1994 02:01:57 -0800

On Sat, 3 Dec 1994, Pete Holsberg wrote:
> In <[email-masked]> Mark Crispin <[email-masked]> writes:
> >On Mon, 28 Nov 1994, Pete Holsberg wrote:
> >> Pine developers: why do you put the "sv4" stuff in with the
> >> non-ANSI group? Is there some variant of SVR4 that is not
> >> ANSI-compatible?
> >The answer to this question is "yes"; there are SVR4 systems that do not
> >have C compilers which support ANSI prototypes.  A port is necessarily
> >limited by the worst representative of that port. 
> Not trying to anger you, Mark, but ANSI C compilers are now in widespread 
> use on mnay SVR4 systems. Perhaps you could give us a choice? 

It has nothing to do with being angry.  It has everything to do with an 
attempt to suppress misinformation being distributed as folklore, that 
subsequently comes back as support issues.

Once again, with feeling: IT DOES NOT MATTER WHICH SIDE OF THE IMAP TREE 
IS USED!!!

If you think it matters, you are mistaken.

Perhaps I should just stop distributing the ANSI side of the IMAP tree, 
and convert all the ANSI ports to non-ANSI prototypes prior to 
distribution.

Or maybe I should call the two sides of the tree imap/blurdybloop and 
imap/sarasoop.

> >There is absolutely no reason why it should matter whether or not the sv4
> >files are in .../imap/ANSI/c-client or .../imap/non-ANSI/c-client. 
> Yes, in my case there was. I needed to have -DANSI set, and there were no 
> sv4 files in .../imap/ANSI/c-client.

Which side of the imap/ANSI imap/non-ANSI tree is used has nothing to do
with -DANSI. 

The IMAP toolkit does not define the ANSI symbol.

The IMAP toolkit does not use the ANSI symbol.

A directory name has no relationship to a C compiler symbol.

> Thank you. What do you suggest I do to build sv4 (non-ANSI C) pine with 
> Unixware and an ANSI C compiler?

Send email to [email-masked] detailing the error messages 
which you are getting.

---

From: [email-masked] (R. Stewart Ellis)
Date: 21 Dec 94 14:46:36 GMT

>> use on mnay SVR4 systems. Perhaps you could give us a choice? 

Another possibility is to tell those people with SVR4 who do not have
conforming compilers that they need to install GCC.  There are a number of
packages that require one to do this for SunOS 4.1.3.

 >and convert all the ANSI ports to non-ANSI prototypes prior to 

Why not use a cpp macro that will instantiate to nothing for setups that
cannot handle this?  Jove used something like this for aa number of years.
It is an interesting hack.

-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)313-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      [email-masked]               /        / /  /  / /
  Gopher,chimera,nn,tin,jove,modems, free code is best!/________/ /  /  / /