Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!ames!kronos.arc.nasa.gov!iscnvx!netcomsv!netcom.com!alm From: alm@netcom.com (Andrew Moore) Subject: Re: [386bsd] patches for bash 1.12 Message-ID: <1992Nov7.023401.10026@netcom.com> Organization: Netcom - Online Communication Services (408 241-9760 guest) References: <5TZTTB2w165w@tsoft.sf-bay.org> Date: Sat, 7 Nov 1992 02:34:01 GMT Lines: 79 In article <5TZTTB2w165w@tsoft.sf-bay.org> bbs.barfeau@tsoft.sf-bay.org (David Fox) writes: >Has anyone successfully compiled bash version 1.12 for 386bsd? Could >you email me those patches or tell me where I could get them? I got >the thing from GNU last night but it doesn't exactly compile correctly. here's some old postings: From: cflatter@nrao.edu (Chris Flatters) Subject: Bash (Was: Help with posting news under BSD/386 wa) Message-ID: <1992Jul23.215524.29293@nrao.edu> Sender: news@nrao.edu Reply-To: cflatter@nrao.edu Organization: NRAO References: <1992Jul23.181019.2902@mks.com> Date: Thu, 23 Jul 1992 21:55:24 GMT Lines: 19 In article 2902@mks.com, fredw@mks.com (Fred Walter) writes: >I suggest you replace the Bourne Shell that comes with 386BSD 0.1 with >GNU's Bash. > >No, I don't know if it will easily compile under 386BSD 0.1. Yes it will. The only problem is that the autoconfiguration procedures mistakenly think that 386BSD is a USGr3 system. I was too lazy to find out what the problem was and just fixed up the bash-Makefile that is generated: just change OS from USG to Bsd; remove the -DUSGr3 and remove -lPW. Alternatively, I think that there is a bash binary in the etc01 archive. Chris Flatters cflatter@nrao.edu 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