This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Update config.guess to treat cygwin 1.7 as new system name
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Christopher Faylor on 4/27/2009 10:02 AM:
>> That would be fine with me. Properly written scripts already use cygwin*
>> as the case for detecting cygwin in general.
>
> I don't see any benefits to appending the cygwin version number to the
> triplet. That just makes extra typing. So what if there is new
> functionality? That's what configure is supposed to determine.
But there's some things that configure scripts cannot determine without
guessing (namely, any runtime test in a cross-compilation environment).
But there are a number of places that exist where the current
cross-compilation guess is pessimistic because of cygwin 1.5 deficiencies,
where distinguishing from cygwin 1.7 can only be done by uname and/or
config.guess.
Reread my original mail from February, when I first suggested this, and
pointed to such an example:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=m4/printf.m4;h=4207ace;hb=f7beddb
>
> What other systems emit version numbers after the OS name? Certainly
> config.guess for linux doesn't do that and it could have done that given
> the improvements from 2.2 -> 2.4 -> 2.6.
Solaris 6 through 11. MacOS. etc. There's definitely precedence in
config.guess for including OS version number in the config.guess output.
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkn2R3UACgkQ84KuGfSFAYAklwCgui8IvnNZApOPkRCOiUIpaRAj
q1EAn39QDLRymXwGdHxTY6IXeaW7DAPV
=H3KE
-----END PGP SIGNATURE-----
--
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/