X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Date: Thu, 11 Jun 2009 20:32:45 +0200 From: Spiro Trikaliotis To: Jay Cc: Cygwin ML Message-ID: <20090611183245.GA23111@trikaliotis.net> Mail-Followup-To: Jay , Cygwin ML References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-SA-Exim-Connect-IP: 87.163.218.249 X-SA-Exim-Mail-From: an-cygwin AT spiro DOT trikaliotis DOT net Subject: Re: managing autoconf versions? X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000) X-SA-Exim-Scanned: Yes (on mail.trikaliotis.net) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Hello Jay, * On Thu, Jun 11, 2009 at 07:02:00AM +0000 Jay wrote: > [maybe should cc cygwin] Doing so. ;) For complete reference, I am citing your complete mail. As you do not seem to be subscribed, I am keeping you as a direct recipient, too. > Just noticed your guys's responses, searching > the web. Thanks. > > Spiro, I don't your answer of not including > generating files with the patch suffices. > - I think people do include them. I am doing open source projects myself. Whenever I get a patch where these generated files (auto*, bison, flex, ...) are included, I ask the sender to send a new copy without these files. There are really a pain in the ass! They are not worth the time it takes me to remove the patches. > - It is important to match versions for testing purposes. > If I test with a non matching autoconf/make, what they generate > won't likely match, and that invalidates testing. In my experience, these differences are seldom important. If they are, I will take such a patch, of course. > Dave, thanks, it is exactly binutils/gcc I'm interested in. > Thank you for proving I'm not crazy -- there really is a problem. > Could be due to your work that cygwin is the best/easiest platform > here (but so slow to fork. :( ). > I was/am not aware of what the version macros achieve. > You know, I mean...ignoring binutils/gcc, though they are relevant, > would I install versions 1.1, 1.2, 1.3, etc. (made up versions) > all to different prefix, put all the prefixes/bin in $PATH and > the version macros search $PATH? > Or do all the tools append versions to all their directories/files? > > > You know, ideally..ideally what I would do is > download "every" version of autoconf/automake > configure and install them all with no flags > put /usr/local/bin in $PATH > and as long as I defined "every" correct/sufficient, be able to > make arbitrary edits to arbitrary projects, and just run > the usual configure+make on them and the right thing would happen. > > Or even, better yet, error if I don't have the matching version > of autoconfigure/automake, perhaps guided by a flag one way > or the other. > > - Jay Best regards, Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/