From xemacs-m  Mon Jan  6 02:00:33 1997
Received: from dres.elam.org (dres@cola169.scsn.net [206.25.247.169])
          by xemacs.cs.uiuc.edu (8.8.4/8.8.4) with ESMTP
	  id CAA24545 for <xemacs-beta@xemacs.org>; Mon, 6 Jan 1997 02:00:30 -0600 (CST)
Received: (from dres@localhost) by dres.elam.org (8.7.6/8.7.3) id CAA02539; Mon, 6 Jan 1997 02:57:27 -0500
To: xemacs-beta@xemacs.org
Subject: Re: XEmacs 19.15-b7 is released.
References: <9701060520.AA20459@nquah6f> <m2afqns6fc.fsf@altair.xemacs.org>
Mime-Version: 1.0 (generated by tm-edit 7.100)
Content-Type: text/plain; charset=US-ASCII
From: James LewisMoss <dres@dres.elam.org>
Date: 06 Jan 1997 02:57:26 -0500
In-Reply-To: Steven L Baur's message of 05 Jan 1997 21:45:27 -0800
Message-ID: <hhn2unp76h.fsf@dres.elam.org>
Lines: 49
X-Mailer: Gnus v5.2.40/XEmacs 20.0

>>>>> "sb" == Steven L Baur <steve@miranova.com> writes:

>>>>> "Barry" == Barry Friedman <friedman@nortel.ca> writes:
 Barry> Patched ok, however:

 Barry> make[1]: *** No rule to make target
 Barry> `/dsk1/misc/xfer/emacs/xemacs-beta/xemacs-19.15/src/../lisp/prim/auto-autoloads.elc'.
 Barry> Stop.

 sb> Do a `make beta' or a `make all-elc' to build the new version.

 Barry> This was after a "make beta" after a "make all-elc".  Both
 Barry> stop with the same error.

 sb> How strange.  Something must not have gotten patched right, as
 sb> the full distribution was built starting from scratch.  Oh well.
 sb> I put a separated copy of auto-autoloads.elc on the ftp site.
 sb> steve@miranova.com baur Unsolicited commercial e-mail will be
 sb> billed at $250/message. "That Bill Clinton.  He probably doesn't
 sb> know how to log on to the Internet."  -- Rush Limbaugh, noted
 sb> Computer Expert

Actually same happened to me. Look in the root dir of the source. It
should be sitting right there.  Looks like patch wants the directory
to put things in in the...
Index: dynodump/Makefile.in.in
===================================================================
RCS file: /usr/local/xemacs/xemacs-20.0/dynodump/Makefile.in.in,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Makefile.in.in      1996/12/28 21:02:46     1.2
+++ Makefile.in.in      1997/01/03 03:09:47     1.3

Ok here is what it looks like.  The Index line I owuld guess is
supposed to tell you where to put things.  I don't think patch pays
any attention to it.  What it looks like patch does is.
1) any new files that it can't find any similiar file down from where
   it was run is put in the root dir.
2) any file that is found multiple times (README, Changelog, etc) it
   rejects because it can't figure out where which one to patch.
3) Any file that has a unique name is patched correctly.
At least this is exactly what patch did to me. :)

Jim
--
@James LewisMoss                 | moss@cs.sc.edu | Blessed Be!
@    http://www.cs.sc.edu/~moss  | dres@scsn.net  | Linux is cool!
@"Argue for your limitations and sure enough, they're yours." Bach

