This is the mail archive of the
mailing list for the Cygwin project.
Re: config.guess and config.sub older than new Cygwin64
- From: Robert McBroom <mcforum at bellsouth dot net>
- To: cygwin at cygwin dot com
- Date: Thu, 05 Sep 2013 09:43:31 -0400
- Subject: Re: config.guess and config.sub older than new Cygwin64
- Authentication-results: sourceware.org; auth=none
- References: <CA+sc5m=2OdnsCHodCK-MTFHojC7DRPns5F=p9C7rm6h8A1ax_Q at mail dot gmail dot com> <5227B0A3 dot 6050104 at cwilson dot fastmail dot fm> <CA+sc5m=awBQ5dii43XaZR3aeJNmy0B5gs5Y_5ShJjwDAMiCkXQ at mail dot gmail dot com> <522877FC dot 9050201 at cs dot utoronto dot ca>
On 9/5/2013 8:24 AM, Ryan Johnson wrote:
That is what you get if you pull a source tar ball off the source tree.
Sometimes there is a clue on a next step along a path to accomplish an
update and sometimes not.
On 05/09/2013 8:08 AM, Earnie Boyd wrote:
I would think that cygwin64 is the least of your worries if you're
using an 11 year-old config.guess...
On Wed, Sep 4, 2013 at 6:13 PM, Charles Wilson wrote:
On 9/4/2013 5:43 PM, Earnie Boyd wrote:
The versions installed into /usr/share/automake-X.Y/ have all been
to be the latest upstream as of mid-July -- for all X.Y from 1.4 to
Just a note to those of you using Cygwin64 to build packages. You
will need to most likely replace the config.guess and config.sub files
in those packages with newer ones from
ftp://ftp.gnu.org/pub/gnu/config/ because it won't guess your system
Twice now I've seen on config-patches a report submitted because of
Also, cygport itself ships with an identical copy, and modifying
to call 'gnuconfigize' during src_compile() will update them as well.
That's fine if the user is using cygport but from the two I've seen on
config-patches is that the user is executing a package configure where
the package has an 11 year old config.guess and is not using cygport
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple