Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: Soren A Subject: Re: cygwin's autoconf? Date: Mon, 2 Dec 2002 00:36:38 +0000 (UTC) Organization: Sporadically, Occasionally Lines: 60 Message-ID: References: <3DE8CDE5 DOT 8060307 AT lapo DOT it> <012101c2987f$67c9eb70$78d96f83 AT pomello> <3DE8E77D DOT 3000603 AT lapo DOT it> <3DE9114C DOT 1070309 AT ece DOT gatech DOT edu> <3DE9E769 DOT 7010104 AT lapo DOT it> <3DEA4653 DOT 10401 AT ece DOT gatech DOT edu> NNTP-Posting-Host: 46.syracuse-05-10rs.ny.dial-access.att.net X-Trace: main.gmane.org 1038789398 31381 12.89.4.46 (2 Dec 2002 00:36:38 GMT) X-Complaints-To: usenet AT main DOT gmane DOT org NNTP-Posting-Date: Mon, 2 Dec 2002 00:36:38 +0000 (UTC) User-Agent: Xnews/5.04.25 X-Archive: encrypt Lapo got me started. "Blame" him ;-)... Charles Wilson wrote in news:3DEA4653 DOT 10401 AT ece DOT gatech DOT edu: >> >> The client machine shouldn't need autotools or the know-how to use >> them, right? > > Not necessarily. If configure.in doesn't have AM_MAINTAINER_MODE, > then the default behavior is for all of the "maintainer rules" to be > active all the time. That means configure searches for automake, > autoconf, etc. and uses them to rebuild the infrastructure if > necessary. Now, even if the maint-mode rules never get invoked, > during *configure* you might get "test" invocations -- and it looks > like those test invocations are failing. Autotools are SO broken, and been for so long. Yeah. This is why I go into hyperrant mode. Lapo, the behavior you expect might be considered reasonable. But the ptb at Autotools Central have decreed that providing some theoretical package maintainer "Joe Blow" with the ability to update his package with one hand on the wheel while eating a sandwich and watching "Attack of the Clones" with 65% of his attention, was more important than preserving that principle (that Autotool Build Configurations should be robust and transparent for the end user, and that as Point One the user won't have to install Autotools herself). AM_MAINTAINER_MODE is the Autotools ptb retroactive bandaid applied instead of recognizing that 'automation' had been allowed to run amok in Autotools and a huge step "backward" needed to be taken. Mostly I think it is the fault of Automake which needed the Autotools structure to be distorted, warped for it to have the 'hooks' it needed in order to work the way it (theoretically) does. The disfiguring of Autoconf, by this unhappy marriage with Automake, is pretty horrific. I commmend you for putting effort into learning Autotools. As Gandalf says at one point, "it isn't comfortable knowledge [the lore of the Rings of Power]". Of course he also says "study not too deeply the arts and devices of the Enemy." Not that any individuals at AutoTools are our "Enemy"; Chuck and others here have in fact got considerable amounts of code they've written in Autotools by now. But I still cannot shake the feeling I am confronted with something warped and a bit malevolent, when I contemplate Autotools. At the very LEAST, something that does what AM_MAINTAINER_MODE causes, should have been the *default* for all autotool'd packages, and only by significant contortions should it have been made possible to cause all that "default" behavior to get activated. But instead it's the other way around, and users are at the mercy of package maintainers' ignorance or awareness of the importance of (at the very MINIMUM) placing AM_MAINTAINER_MODE in their configuration file. Soren A -- What do Internet Mailing Lists and crowded neighborhoods have in common? Both will either drive you out or teach you how to ignore barking dogs. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/