Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3C4DAAED.6060100@ece.gatech.edu> Date: Tue, 22 Jan 2002 13:09:49 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Charles Wilson CC: "Parker, Ron" , cygwin@cygwin.com Subject: Re: Cygwin Autotool Wrappers References: <3C4DAA41.10607@ece.gatech.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Charles Wilson wrote: > > I *really* don't know what the right answer is, here...perhaps (in empty > directory) > > aclocal --version: report DEVEL > automake --version: report DEVEL > autoconf --version: report DEVEL > autoheader --version: report DEVEL > > because these four are often checked by configure scripts, and are > sometimes (re)used by automated build procedures outside of the "real" > srcdir. > > autoheader --version: status quo ^^^^^ I meant autoreconf > autoscan --version: status quo > autoupdate --version: status quo > ifnames --version: status quo > libtool --version: stutus quo > libtoolize --version: status quo > > because none of these should ever be caused by automated build > procedures outside of the "real" srcdir. --Chuck -- 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/