From xemacs-m  Mon Dec 16 02:33:40 1996
Received: from cs.utah.edu (cs.utah.edu [128.110.4.21]) by xemacs.cs.uiuc.edu (8.8.3/8.8.3) with ESMTP id CAA21790 for <xemacs-beta@xemacs.org>; Mon, 16 Dec 1996 02:33:39 -0600 (CST)
Received: from fast.cs.utah.edu by cs.utah.edu (8.8.4/utah-2.21-cs)
	id BAA11260; Mon, 16 Dec 1996 01:33:39 -0700 (MST)
Received: by fast.cs.utah.edu (8.6.10/utah-2.15-leaf)
	id BAA20106; Mon, 16 Dec 1996 01:33:39 -0700
Date: Mon, 16 Dec 1996 01:33:39 -0700
Message-Id: <199612160833.BAA20106@fast.cs.utah.edu>
X-Mailer: VM 5.95 (beta)/19.15 XEmacs Lucid (beta4)
From: Bart Robinson <lomew@cs.utah.edu>
To: xemacs-beta@xemacs.org
Subject: 19.15b4 on HPBSD success story + bug fixes

More stuff after config info.

---------------------------------------------------------------------
Configured for `hppa1.0-hp-bsd'.

  Where should the build process find the source code?    /n/liberty/arch3/tmp/lomew/xemacs-19.15-b4
  What installation prefix should install use?		  ${srcdir}
  What operating system and machine description files should XEmacs use?
        `s/hppa-bsd4-3.h' and `m/hp800.h'
  What compiler should XEmacs be built with?              /usr/bin/gcc  -g -O 
  Should XEmacs use the GNU version of malloc?            yes
  Should XEmacs use the relocating allocator for buffers? no
  What window system should XEmacs use?                   x11
  Where do we find X Windows libraries?                   /usr/new/lib/X11R4
  Additional header files:                                /afs/cs.utah.edu/home/lomew/include /usr/local/share/contrib/include/xpm-include
  Additional libraries:                                   /afs/cs.utah.edu/home/lomew/lib /usr/local/contrib/lib
  Compiling in support for XAUTH.
  Compiling in support for XPM.
  Compiling in support for X-Face headers.
  Compiling in support for GIF image conversion.
  Using the Lucid menubar.
  Using the Lucid scrollbar.
  Using the Athena dialog boxes.
  Compiling in extra code for debugging.
---------------------------------------------------------------------


1) Whenever I'd find a file XEmacs would ask me "Set local
   variables in -*- line...?" even though the file had no -*-
   magic.  This was because `hack-local-variables-prop-line'
   would call `hack-local-variables-p' even if no -*- magic was
   found.  Here is a patch, it just wraps the (let ...) with an
   (if result ...)

   [I have `enable-local-variables' set to 'ask-me, this might
    be why other people haven't noticed this.]

---------------------------------------------------------------------
--- xemacs-19.15-b4/lisp/prim/files.el	1996-12-15 23:28:04-07	1.1
+++ xemacs-19.15-b4/lisp/prim/files.el	1996-12-15 23:32:26-07
@@ -1279,22 +1279,23 @@
 		   (setq result (cons (cons key val) result))
 		   (skip-chars-forward " \t;")))
 	       (setq result (nreverse result))))))
-	
-    (let ((set-any-p (or force (hack-local-variables-p t)))
-	  (mode-p nil))
-      (while result
-	(let ((key (car (car result)))
-	      (val (cdr (car result))))
-	  (cond ((eq key 'mode)
-		 (setq mode-p t)
-		 (funcall (intern (concat (downcase (symbol-name val))
-					  "-mode"))))
-		(set-any-p
-		 (hack-one-local-variable key val))
-		(t
-		 nil)))
-	(setq result (cdr result)))
-      mode-p)))
+
+    (if result
+	(let ((set-any-p (or force (hack-local-variables-p t)))
+	      (mode-p nil))
+	  (while result
+	    (let ((key (car (car result)))
+		  (val (cdr (car result))))
+	      (cond ((eq key 'mode)
+		     (setq mode-p t)
+		     (funcall (intern (concat (downcase (symbol-name val))
+					      "-mode"))))
+		    (set-any-p
+		     (hack-one-local-variable key val))
+		    (t
+		     nil)))
+	    (setq result (cdr result)))
+	  mode-p))))
 
 (defvar hack-local-variables-hook nil
   "Normal hook run after processing a file's local variables specs.

---------------------------------------------------------------------


2) The ebuff-menu patch didn't get into b4.  I mean the keymap
   related one that changed the fillarray's to for-loops.


3) I run configure with --verbose and get a message like

	checking whether localtime caches TZ
	checking whether cross-compiling
		yes
		defining LOCALTIME_CACHE

   But I'm not really cross-compiling (it doesn't really set
   $cross_compiling, just looks like it.)  This happens because
   AC_TEST_PROGRAM calls AC_C_CROSS if it hasn't been already.
   Unfortunately this prints stuff in the wrong place.  Looks
   like an autoconf bug, but I suggest a call to AC_C_CROSS be
   placed earlier in configure.in.  It won't hurt anything.  I
   think AC_PROG_CC calls AC_C_CROSS but it doesn't always get
   called (it doesn't when --compiler is given, which I also
   do.)

   I don't have autoconf-1.9 handy so I can't fiddle with this.


4) signal_handler_t is not defined unless HAVE_SIGPROCMASK is,
   yet it is needed in other places, e.g., sysdep.c:2630.  Here
   is a patch:

---------------------------------------------------------------------
--- syssignal.h	1996-12-15 18:33:37-07	1.1
+++ syssignal.h	1996-12-15 18:34:55-07
@@ -88,11 +88,12 @@
    the risk of someone forgetting this convention and calling
    signal() directly. */
 
+typedef SIGTYPE (*signal_handler_t) (int);
+
 #if defined (HAVE_SIGPROCMASK)
 
 /* The POSIX way (sigaction, sigprocmask, sigpending, sigsuspend) */
 
-typedef SIGTYPE (*signal_handler_t) (int);
 extern signal_handler_t sys_do_signal (int signal_number,
 				       signal_handler_t action);
 /* Provide our own version of signal(), that calls sigaction().  The
---------------------------------------------------------------------


-- bart

