On 10/3/2016 10:31 PM, Adrien Nader wrote:
> I quickly went through the diff and I've found the following:
>
>> + amd64:MSYS*:*:* | x86_64:MSYS*:*:*)
>> + echo x86_64-unknown-msys
>> + exit ;;
> There are also changes that could be related to ARM support ("earm").
>
> Oh and iOS and ASM.js but I think they don't matter much to us (although
> maybe we'll soon have that portable POSIX environment in javascript and
> we'll build boost with it).
>
> Most of the diff is either quoting or removed and added platforms but
> there are also a couple other changes.
You are reading it backward. Since the version of config.guess that is
checked in is the beta, when I 'downgrade' it to the released version
(1.15), it adds back the things the beta removed.
IOW, the beta doesn't "add" support for amd64:MSYS*:*:*, it's removing it.
> I think it's safer to keep the version that is currently checked in. I
> prefer versions from released tarballs but sometimes we'll also need to
> handle new platforms. For these cases, I'm perfectly fine with
> unreleased versions (autotools perfectly enables such usecases)
Since we aren't grabbing these files at a fixed point (ie a release),
the version we are using could have any amount of weirdness in it that
would get deleted the next day. IOW, "perfectly enables" might work
when taking the 1.15 files and back-proping them to 1.14. But grabbing
"today's" checkin seems really risky. Other than at a release, how can
we know what's "stable?"
> but I'd
> like to see a request somewhere or a slightly more complete commit
> message (i.e. "adds support for X and Y") so it's easier to track in the
> future.
This is the key point. The risk from mixing/matching can only be
justified if there is some clear benefit. But nowhere in this (1 month
old) thread has anyone stated that reason. Maybe the reason we were
doing this got fixed a long time ago, but since no one remembers what it
was, we just keep grabbing random config.guess files.
My vote is to check in code using the released/supported version of the
software. If someone wants/needs to update to a later config.guess, let
them post a patch (and a reason) and get approval.
FWIW, the patch (with 100% regenerated files) using the 'released'
version of config.guess is still at
http://www.LimeGreenSocks.com/gen2.7z. If using a beta config.guess is
what is needed to get this approved, just let me know specifically where
I should get it from (and the other support files [config.sub? Others?]
you want me to grab) and I'll update, retest and resubmit this patch.
Jony? Ktietz? Decision time?
dw
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
