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.devel Subject: Re: specifying workbook dir for dist-hook Date: Sun, 07 Apr 2002 15:55:43 -0700 Sender: guile-devel-admin@gnu.org Message-ID: References: <87y9g8nutk.fsf@zagadka.ping.de> <87bsd0tygs.fsf@zagadka.ping.de> <87vgb31wz6.fsf@zagadka.ping.de> Reply-To: ttn@glug.org NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1018224351 4545 127.0.0.1 (8 Apr 2002 00:05:51 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 8 Apr 2002 00:05:51 +0000 (UTC) Cc: guile-devel@gnu.org Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16uMfO-0001BC-00 for ; Mon, 08 Apr 2002 02:05:50 +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 16uMIZ-00017P-00; Sun, 07 Apr 2002 19:42:15 -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 16uLd8-0005ZB-00 for ; Sun, 07 Apr 2002 18:59:27 -0400 Original-Received: from ttn by giblet with local (Exim 3.33 #1 (Debian)) id 16uLZX-0000SQ-00; Sun, 07 Apr 2002 15:55:43 -0700 Original-To: mvo@zagadka.ping.de In-Reply-To: <87vgb31wz6.fsf@zagadka.ping.de> (message from Marius Vollmer on 07 Apr 2002 15:04:13 +0200) Errors-To: guile-devel-admin@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Developers list for Guile, the GNU extensibility library List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.devel:324 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:324 From: Marius Vollmer Date: 07 Apr 2002 15:04:13 +0200 Is this a real fix? As far as I can see, it only works 'accidentally' when using GNU make. Do we want to require GNU make? the mechanisms and times are as follows: * automake scanning happens at autogen.sh time. automake instantiates a Makefile.in from templates, handling "include" directives by diverting (recursively) scanning to the included file and omitting the directive in the output, and handling "if MAINTAINER_MODE" sections by prefixing "@MAINTAINER_MODE_TRUE@" to makefile var definitions (and using other generally portable constructs). * expansion of @MAINTAINER_MODE_TRUE@ happens at configure time. configure creates portable Makefile from portable Makefile.in, etc. * execution of Makefile actions happens at make time by whichever make(1) is either available on the system or specified by the user. here, the root cause of the bug seems to lie in how automake handles nested "if MAINTAINER_MODE" sections. because we see different behaviors in different versions of automake and because the documentation does not explicitly support our funky usage, i figured that the most slackful fix would be to "don't do that"; the nature of the fix is to fall back on well-supported (documented, stable) automake features and avoid conflating them. you'll also note from point 1 above that none of this has anything to do w/ GNU make (thankfully :-). thi _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel