Xref: utzoo comp.mail.elm:3543 comp.sys.next:11382
Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!zazen!news
From: anderson@macc.wisc.edu (Jess Anderson)
Newsgroups: comp.mail.elm,comp.sys.next
Subject: Elm on NeXT
Message-ID: <1991Jan11.034948.8500@macc.wisc.edu>
Date: 11 Jan 91 03:49:48 GMT
Sender: news@macc.wisc.edu (USENET News System)
Organization: Madison Academic Computing Center, UW-Madison
Lines: 33


I'm running NeXT 2.0 on a 68040 cube, and having ftped a
clean Elm PL11 from dsinc.dsi.com, and heeding the advice
to use -bsd and -lsys_s in response to complier flags and
additional libraries questions during Configure, Configure
stumbled on not being able to find cc libraries in a flock
of directories it searched, starting with /usr/lib.

I canned the Configure, went looking, and it seemed to me
the library routines *were* in /usr/lib (which is linked to
another (NeXT-specific) directory (was *that* the problem,
I wonder?).  So I restarted Configure and answered /usr/lib
to that question.

At 'make all' time, the MAKELOG shows lots of messages about
incompatible types, pointers, etc. in several routines,
then crashes while trying to link bin/elm with multiple
definitions of _strpbrk.

That's where I am.  I'm unfortunately not very sophisticated
in most of these matters, but I had so few problems on my
former Ultrix system that I've become quite addicted to elm
and want to get it going on my NeXT if I can.

If some kind soul can help, that would be swell (I didn't think
it politic to send this long MAKELOG around the universe by
attaching it here).

--
Jess Anderson  Madison Academic Computing Center  University of Wisconsin
Work: Rm. 3130, 1210 West Dayton St., Madison WI 53706, Ph. 608/262-5888
Home: 2838 Stevens St., 53705, 608/238-4833  Bitnet: anderson@wiscmacc
Internet: anderson@macc.wisc.edu  UUCP:{}!uwvax!macc.wisc.edu!anderson