Re: config.[guess|sub] (WAS: Re: Is this a bug in autoconf? (patchincluded))
Hi, But anyway, let's apply this patch, it is a basis for further changes. For instance we might implement --update which could wget the files if possible, and --report which could automatically send the message. We have already talked about this some time ago. I'm happy to apply this patch as a step in the right direction. It's been needed for quite some time. I made a minor grammatical fix to your output, plus this important fix to the config.sub patch (you did test it, right?) --version | --vers* | -V ) echo "$version" ; exit 0 ;; ^ `- was just "version" I'm checking the patches in now. Thanks, Ben
Re: config.[guess|sub] (WAS: Re: Is this a bug in autoconf? (patchincluded))
Quoth Akim Demaille: First of all, there are still no easy means to compare two versions and decide which one is the most recent. Well ... | $ ./config.guess --version | i586-pc-linux One could probably easily use $Date$ or $Revision$ from CVS for arranging this. The problem, however, is that config.guess is nowadays neither forward nor backward compatible and it's becoming increasingly difficult to keep track of what it is supposed to print. Just a few weeks ago it printed i586-pc-linux-gnu for this machine. Now this happens: | $ ./config.guess | i586-pc-linux | $ ./config.sub `config.guess` | i586-pc-linux-gnu | $ ./config.sub i586-linux | i586-pc-linux-gnu And just for fun: | $ ./config.sub i586-unknown-linux-gnu | i586-unknown-linux-gnu (Somebody please explain how this machine is supposed to differ from the above.) I hope that convinces everyone about $build != $host. I wonder, is there some sort "release" of these config tools I should be using for "production" work? PS: And I'll bet lunch that no longer differentiating elf and non-elf freebsd (as of a week ago) is going to break something. -- Peter Eisentraut Sernanders väg 10:115 [EMAIL PROTECTED] 75262 Uppsala http://yi.org/peter-e/Sweden
