From owner-freebsd-questions Fri May 29 16:15:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26939 for freebsd-questions-outgoing; Fri, 29 May 1998 16:15:05 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from aphrodite.harbor.ab.ca (aphrodite.harbor.ab.ca [198.161.82.75]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26872 for ; Fri, 29 May 1998 16:14:33 -0700 (PDT) (envelope-from mathezer@harbor.ab.ca) Received: from clunk.harbor.ab.ca by aphrodite.harbor.ab.ca with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1458.49) id JSF3D292; Fri, 29 May 1998 17:14:10 -0600 Date: Fri, 29 May 1998 17:14:10 -0600 (MDT) From: Stephen Mathezer Reply-To: Stephen Mathezer To: questions@FreeBSD.ORG Subject: xemacs-20.4 install problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to compile xemacs-20.4 on 2.2.6 which goes fine until I try to do a make install. I am doing this from the tar file downloaded directly from ftp.xemacs.org, not the port but I took a quick look and the port doesn't seem to patch anything much of importance. When make install tries to dump xemacs, I get the following: ... Loading /export/zips/xemacs-20.4/lisp/vc/auto-autoloads... Loading /export/zips/xemacs-20.4/lisp/viper/auto-autoloads... Loading /export/zips/xemacs-20.4/lisp/vm/auto-autoloads... Loading /export/zips/xemacs-20.4/lisp/w3/auto-autoloads... Loading /export/zips/xemacs-20.4/lisp/x11/auto-autoloads... Loading site-load... Finding pointers to doc strings... Finding pointers to doc strings...done Dumping under the name xemacs Purespace usage: 704584 of 705096 (100%). Process killed due to text file modification Process killed due to text file modification Killed *** Error code 137 Stop. *** Error code 1 Stop. Does anyone have any ideas. Thanks -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message