From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.lisp.guile.bugs Subject: Re: guile-snarf writes to $srcdir, which is not kosher Date: Mon, 08 Apr 2002 12:34:52 -0700 Sender: bug-guile-admin@gnu.org Message-ID: References: <87bscvjez9.fsf@zagadka.ping.de> <873cy6f8av.fsf@zagadka.ping.de> Reply-To: ttn@glug.org NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1018294765 26730 127.0.0.1 (8 Apr 2002 19:39:25 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 8 Apr 2002 19:39:25 +0000 (UTC) Cc: bug-guile@gnu.org Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16uez6-0006x1-00 for ; Mon, 08 Apr 2002 21:39:25 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16ueyq-0002K3-00; Mon, 08 Apr 2002 15:39:08 -0400 Original-Received: from ca-crlsbd-u4-c4c-174.crlsca.adelphia.net ([68.66.186.174] helo=giblet) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16ueyR-0002Iy-00 for ; Mon, 08 Apr 2002 15:38:43 -0400 Original-Received: from ttn by giblet with local (Exim 3.33 #1 (Debian)) id 16ueui-0001b7-00; Mon, 08 Apr 2002 12:34:52 -0700 Original-To: mvo@zagadka.ping.de In-Reply-To: <873cy6f8av.fsf@zagadka.ping.de> (message from Marius Vollmer on 08 Apr 2002 18:45:44 +0200) Errors-To: bug-guile-admin@gnu.org X-BeenThere: bug-guile@gnu.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Bug reports for GUILE, GNU's Ubiquitous Extension Language List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.bugs:110 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.bugs:110 From: Marius Vollmer Date: 08 Apr 2002 18:45:44 +0200 A VPATH build is when you compile in a directory other than the source directory. This is useful when you want to compile a package for different configurations but from a common source. The name stems from the fact that it is implemented using the VPATH variable of make. could you describe VPATH as "configure in place, make from elsewhere"? or is configure done elsewhere also? i've heard the latter referred to as srcdir!=builddir (and usually make is done where configure is). > if you remove cleaning you need to promote SCM_MAGIC_SNARFER to required > status and document accordingly. It is already. all i see is this: During snarfing, the pre-processor macro @code{SCM_MAGIC_SNARFER} is defined. i'm assuming that whatever changes made to branch_release-1-6 that are long-term applicable would be also made in HEAD roughly concurrently, but i guess this is saved for later? thi _______________________________________________ Bug-guile mailing list Bug-guile@gnu.org http://mail.gnu.org/mailman/listinfo/bug-guile