Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3DE9E769.7010104@lapo.it> Date: Sun, 01 Dec 2002 11:41:45 +0100 From: Lapo Luchini User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021122 X-Accept-Language: it, en, fr, es MIME-Version: 1.0 To: Mailing List: CygWin Subject: Re: cygwin's autoconf? References: <3DE8CDE5.8060307@lapo.it> <012101c2987f$67c9eb70$78d96f83@pomello> <3DE8E77D.3000603@lapo.it> <3DE9114C.1070309@ece.gatech.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit > > >> Doing "aclocal && automake && autoconf" as the autobook suggests >> doesn't change things... =( >> (or: it does seldom work, but usually doesn't.. that's why I'm >> thinking about granularity in NT's timekeeping) > > automake 1.7.x and later require autoconf-2.54 or newer. Ordinarily, > the wrapper scripts in the cygwin autotools suite ensure that > "matching" versions are called -- unless your installation is not > fully uptodate. That's not the point: I have no problem on my cybwin developement machine: the problem is that ./configure-generated Makefile tries to call the autotools on each different machine, even in no-one changed configure.in or Makefile.am The client machine shouldn't need autotools or the know-how to use them, right? -- Lapo 'Raist' Luchini lapo@lapo.it (PGP & X.509 keys available) http://www.lapo.it (ICQ UIN: 529796) -- 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/