Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!mips!decwrl!sdd.hp.com!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!odin!chet From: chet@odin.INS.CWRU.Edu (Chet Ramey) Subject: Re: Bash (Was: Help with posting news under BSD/386 wa) Message-ID: <1992Jul24.195432.29759@usenet.ins.cwru.edu> Sender: news@usenet.ins.cwru.edu Nntp-Posting-Host: odin.ins.cwru.edu Organization: Case Western Reserve University, Cleveland, OH (USA) References: <1992Jul23.181019.2902@mks.com> <1992Jul23.215524.29293@nrao.edu> Date: Fri, 24 Jul 92 19:54:32 GMT Lines: 30 In article <1992Jul23.215524.29293@nrao.edu> cflatter@nrao.edu writes: >Yes it will. The only problem is that the autoconfiguration procedures >mistakenly think that 386BSD is a USGr3 system. (It actually doesn't find anything it recognizes, so it defaults to `generic' 386 Unix -- System V.3.) Try adding this to the `i386' section of machines.h (with the rest of the i386 descriptions). This is what I currently have for Bash 1.13. /* BSDI BSD/386 running on a 386 or 486. */ # if !defined (done386) && defined (bsdi) # define done386 # define M_MACHINE "i386" # define M_OS Bsd # define HAVE_SYS_SIGLIST # define HAVE_SETLINEBUF # define HAVE_GETGROUPS # define HAVE_VFPRINTF # define HAVE_STRERROR # define VOID_SIGHANDLER # define HAVE_DIRENT # endif /* !done386 && bsdi */ -- ``The use of history as therapy means the corruption of history as history.'' -- Arthur Schlesinger Chet Ramey, Case Western Reserve University Internet: chet@po.CWRU.Edu