Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!spool.mu.edu!uwm.edu!cs.utexas.edu!uunet!nih-csl!helix.nih.gov!crtb From: crtb@helix.nih.gov (Chuck Bacon) Subject: Re: [NetBSD 0.9] - gnu-emacs compile? HELP! Message-ID: <1993Oct28.074947@helix.nih.gov> Sender: postman@alw.nih.gov (AMDS Postmaster) Reply-To: crtb@helix.nih.gov (Chuck Bacon) Organization: National Institutes of Health References: <Added.wgnOLbG00Udb8QbU5N@andrew.cmu.edu> Date: Thu, 28 Oct 1993 11:49:47 GMT Lines: 57 In article <Added.wgnOLbG00Udb8QbU5N@andrew.cmu.edu>, Todd.Williamson@IUS4.IUS.CS.CMU.EDU writes: [ ... ] |> I downloaded the 19.19 |> gnu-emacs distribution from prep.ai.mit.edu. I ran |> "configure i386-foo-386bsd", then gmake MAKE=gmake, then I had to fix |> a few things in the config.h file like "#define HAVE_MKDIR" and |> "#define HAVE_XSCREENNUMBEROFSCREEN" to get it to compile finally. |> |> temacs runs fine, but the file that gets dumped as emacs isn't an |> executable (it gives me the error "emacs: 1: Syntax error: word |> unexpected (expecting ")")"). Wow! I've got *exactly* the same symptom, same wording and everything. The difference is: (1) I'm trying to install FreeBSD via the kcopy-aha.floppy route; (2) It happens with some of the most basic commands, like rm, mv and df. I'm afraid the upgrade has failed and that I'll have to just let the install script wipe everything. But I don't dare let it wipe my DOS partition, since I've got real work on it. |> Any ideas what I'm doing wrong? In my case, it was a case of bad judgment. I booted from a FreeBSD kernel, in place of my 386bsd (pk2.4) kernel, then exploded the cpio and bin distribs. without thinking too much. Naturally it wouldn't overwrite init and possibly some others. |> I'd be just as happy if someone could |> provide me with an emacs executable... Sorry, I subverted this thread from an emacs plea to one about this "Syntax error" message. |> Thanks, |> |> -Todd. |> For what it's worth, I've always harbored a hatred for any software that cries "syntax error" when there's no syntax error but rather some other kind of failure. This goes back to the oldest Basic interpreters which had no other error message! -- Chuck Bacon - crtb@helix.nih.gov ( alas, not my 3b1, er, FreeBSD )-: ABHOR SECRECY - DEFEND PRIVACY