*BSD News Article 7866


Return to BSD News archive

Xref: sserve comp.mail.elm:7074 comp.unix.bsd:7917
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!olivea!charnel!rat!usc!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!sun-barr!news2me.EBay.Sun.COM!cronkite.Central.Sun.COM!texsun!moxie!hackney
From: hackney@moxie.hou.tx.us (Greg Hackney)
Newsgroups: comp.mail.elm,comp.unix.bsd
Subject: Re: elm 2.4 for 386bsd?
Message-ID: <1992Nov18.031235.13671@moxie.hou.tx.us>
Date: 18 Nov 92 03:12:35 GMT
References: <1992Nov16.192642.26294@hippo.ru.ac.za>
Organization: Home
Lines: 26

ccfj@hippo.ru.ac.za (F. Jacot Guillarmod) writes:
> Has anyone ported elm 2.4 to 386bsd?  Any feedback appreciated.

Yes, I just compiled Elm 2.4 PL11 on 386BSD. Here's the tips:

1. /bin/sh isn't yet suitable to compile Elm. You must use bash instead,
   which comes with the system. Copy it into /bin/sh. (I'd suggest leaving
   it there permanently).

2. Edit lib/opt_utils.c around line #205

   old:  #if defined(BSD) && !defined(_POSIX_SOURCE)
   new:  #if defined(BSD) && !defined(_POSIX_SOURCE) && !defined(BSD386)

3. Run the Configure program to:
     Use "flock" for file locking
     Use these for the optional cc flags:  -traditional -DBSD386

   At the end of the Configure script you have the opportunity to
   escape to edit config.sh. Type: !vi config.sh
   and change "d_sigaction" to say "undef".

4. Type "make" and away you go.
--
Greg Hackney
hackney@moxie.hou.tx.us