From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: Problem with make: unexpected EOF while looking for ``' Date: Sun, 13 Feb 2000 16:20:08 +0200 Organization: NetVision Israel Lines: 26 Message-ID: References: <38A6A6D0 DOT 6CA8CB67 AT i DOT am> NNTP-Posting-Host: is.elta.co.il Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: news.netvision.net.il 950451788 4674 199.203.121.2 (13 Feb 2000 14:23:08 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 13 Feb 2000 14:23:08 GMT X-Sender: eliz AT is In-Reply-To: <38A6A6D0.6CA8CB67@i.am> To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Errors-To: dj-admin AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sun, 13 Feb 2000, Harri Tuomela wrote: > bash$ make > c:/Windows/Temp/dj810000: unexpected EOF while looking for ``' > c:/Windows/Temp/dj810000: c:/Windows/Temp/dj810000: line 2: syntax error > Abort! > Exiting due to signal SIGABRT > Raised at eip=0001eaaf This is a tell-tale symptom of an old port of Make trying to execute a command that requires a Unixy shell, on a system where Make cannot find Bash, or with Makefile which doesn't instruct Make to use Bash. The solution is a two-step dance: Step 1: upgrade to the latest port of Make (v2gnu/mak3781b.zip). This will cause Make to print an error message instead of aborting with SIGABRT. To have the problem solved entirely, you need Step 2: put a line "SHELL = /bin/sh" somewhere in your Makefile.in (or Makefile.am, as the case may be). For more about this subtlety, read the file README.DOS in the Make distribution, where it discusses the "SHELL = /bin/sh" issue.