Xref: utzoo comp.unix.ultrix:7148 comp.mail.elm:4096
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!pacbell.com!decwrl!pa.dec.com!nntpd.lkg.dec.com!riscy.enet.dec.com!croton.nyo.dec.com!frank
From: frank@croton.nyo.dec.com (Frank Wortner)
Newsgroups: comp.unix.ultrix,comp.mail.elm
Subject: Re: Anyone ever run elm on DECstation/Ultrix?
Message-ID: <2221@riscy.enet.dec.com>
Date: 8 May 91 14:40:48 GMT
References: <1991May06.023124.1453@cs.fau.edu> <1991May6.213607.14679@unixland.uucp> <1991May7.230339.3520@ccu.umanitoba.ca>
Sender: newsdaemon@riscy.enet.dec.com
Reply-To: frank@croton.nyo.dec.com
Followup-To: comp.unix.ultrix
Organization: NY ULTRIX Resource Center, Digital Equipment Corporation
Lines: 25

In article <1991May7.230339.3520@ccu.umanitoba.ca>, gedetil@silver.cs.umanitoba.ca (Gilbert E. Detillieux) writes:

|>The only problem I had with the installation was trying to compile the
|>thing with Gnu C, rather than the standard C compiler:  the problem seems to be
|>with inconsistencies in the Ultrix header files (e.g. typedef int time_t; was
|>in some headers, rather than using long int).  When I gave up on Gnu C's nice
|>strict type-checking and used the much more lax MIPS C compiler, everything
|>worked fine.  (Retorical FAQ:  When will DEC get Unix right?)

You gave up way too easily.  ;-)

There are two files that give gcc problems:  date.c and opt_util.c.  Both of these
are easy to fix.

In date.c, place an #ifndef __STDC__, #endif pair around the declaration of time().

In opt_util.c, place an #ifndef __ultrix__ #endif pair around the definitions of
strtok() and strpbrk().  The ULTRIX C library contains these functions.  A better
solution would be to update the Configure script to check for the existence of
these funtions.

If you make both these changes, gcc *will* compile ELM on the ULTRIX operating
system.

					Frank