topic Re: Emacs on Freeware disk in Operating System - OpenVMS

Emacs on Freeware disk

Gareth Williams_2 — Wed, 01 Sep 2010 14:54:55 GMT

I've been trying to compile emacs 21.2-3 from
the Freeware disk. I've printed out Edgar
Zamora's log of his successful compilation, as
posted in the forum on 2009 Mar. 5.
Unfortunately, I'm not having his success.
I follow the instructions, comparing my output
to Edgar's. There are no problems until the
following step:

$ mmk/ignore=warn
%MMK-I-ACTNOUPD, action did not update target FRC.SRC.PATHS.H
set def [.vms]
MMS /IGNORE=WARN routines.tpu$section
if "" .nes. "" then define /nolog sys ,sys$disk:[]
if "" .eqs. "" then define /nolog sys sys$disk:[]
%MMK-I-ACTNOUPD, action did not update target ROUTINES.TPU$SECTION
set def [-]
%MMK-I-ACTNOUPD, action did not update target [.VMS]ROUTINES.TPU$SECTION
Producing `[.src]paths.h' from `AXPA:[EMACS.EMACS212_3.src]paths.h_in'.
%DIFF-F-OPENIN, error opening AXPA:[EMACS.BUILD.SRC]PATHS.H_TMP; as input
-RMS-E-FNF, file not found
%MMK-F-ERRUPD, error status %X106C109C occurred when updating target PATHS-FORCE

I note that Edgar's log did not show the
ACTNOUPD messages about TPU$SECTION.

I've done a search to see if anyone else
has had this problem, but I couldn't find
anything. Has anyone any thoughts?

Gareth

Re: Emacs on Freeware disk

EdgarZamora_1 — Thu, 02 Sep 2010 18:09:54 GMT

Please attach your AXPA:[EMACS.BUILD]BUILD_EMACS21.COM file. Rename the attachment to .txt before attaching.

Re: Emacs on Freeware disk

Gareth Williams_2 — Fri, 03 Sep 2010 16:12:43 GMT

Try this again. Stupid Comcast mail...

Gareth

Re: Emacs on Freeware disk

Gareth Williams_2 — Fri, 03 Sep 2010 16:25:46 GMT

Hmm. There doesn't appear to be a way for
someone to delete one of their postings.
That's annoying...

Gareth

Re: Emacs on Freeware disk

H.Becker — Sat, 04 Sep 2010 12:33:02 GMT

It looks like you have a conflict with a DCL symbol which makes edit/tpu fail. As I already suggested in the I64 text file, do a
$ del/symbol/global ed
or any whatever your related symbol is.

The VMS build environment for emacs is a mess. It is longing for a cleanup or rewrite. With not much interest in emacs on VMS - wasn't its support dropped? - it is unlikely to happen.

Re: Emacs on Freeware disk

Gareth Williams_2 — Sat, 04 Sep 2010 19:53:23 GMT

Aha. That did the trick. Another problem
cropped up during the compile: xmenu.h was
not found at one point, I just copied the
version from AXPA:[EMACS.EMACS212_3.OLDXMENU].

When trying to add GNU_STARTUP to
SYSTARTUP_VMS.COM I get the following error:

%GNU_STARTUP-I-SETTING_UP, setting up Emacs version 21.2
%INSTALL-E-FAIL, failed to REPLACE entry for DISK$SDATA1EMACS-21_2.EXE
-INSTALL-E-IMGTRACED, /TRACEBACK image cannot be a privileged, execute_only, or resident image

I didn't see any mention of TRACEBACK in
the log of your successful compile.

Gareth

Re: Emacs on Freeware disk

Dennis Handly — Sat, 04 Sep 2010 20:21:28 GMT

That previous emacs thread:
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1319164

>There doesn't appear to be a way for someone to delete one of their postings.

If there are privacy concerns with your attachment, you can ask the moderators to remove that reply by asking in this or similar thread:
July/August/September 2010 Issues Requiring Moderator Intervention Thread
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1437415

I'll make the request.

Re: Emacs on Freeware disk

H.Becker — Sat, 04 Sep 2010 21:10:14 GMT

>>> Another problem
cropped up during the compile: xmenu.h was
not found at one point, I just copied the
version from AXPA:[EMACS.EMACS212_3.OLDXMENU].

Is it that the build aborts with "%MMS-F-ABORT, for target XMENU.OBJ..."? You can just restart mms as decribed in the i64 text file.

>>> I didn't see any mention of TRACEBACK in
the log of your successful compile.

I'm sure, I didn't run GNU_STARTUP and didn't install the image. It seems the executable is installed with privileges. So I would expect the non-debug version to be linked with /notrace. So the link command seems wrong/different. I doubt it is another symbol, but I would check. To find out what happened, you have to check the build log or dive into the mms files and find the link command.