Re: [Mingw-w64-public] [Patch] Make build environment consistent

[David Wohlferd]

On 10/17/2016 2:34 AM, JonY wrote:
> On 10/17/2016 10:17, David Wohlferd wrote:
>> Is that the same as "approved for push?"  Or am I still waiting to
>> hear from someone?  I'm told you are the 'makefile' approver.
>>
> Yes, you can go ahead and push.

Thank you.  Pushed.

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
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Patch] Make build environment consistent

[David Wohlferd]

On 10/15/2016 5:04 PM, JonY wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 10/16/2016 07:21, David Wohlferd wrote:
>> I'm asking that my current patch (which does NOT use the beta
>> files) be approved.  If there is a reason to use the beta files,
>> let's do that as a separate checkin, along with an explanation as
>> to WHY we are doing it.
>>
> We can put the newer version back if someone complains.

Agreed.

> I have no strong preferences either way.

Is that the same as "approved for push?"  Or am I still waiting to hear 
from someone?  I'm told you are the 'makefile' approver.

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
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Patch] Make build environment consistent

[JonY]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 10/16/2016 07:21, David Wohlferd wrote:
> I'm asking that my current patch (which does NOT use the beta
> files) be approved.  If there is a reason to use the beta files,
> let's do that as a separate checkin, along with an explanation as
> to WHY we are doing it.
> 

I have no strong preferences either way. We can put the newer version
back if someone complains.


-BEGIN PGP SIGNATURE-

iF4EAREIAAYFAlgCxAQACgkQk721PNTrx0C7nwD8C2gIDsNcqvnYjaitrusQcgzc
CWuuPqoSvFqFqN4ig8kBAJlINziWPmMAaCIEn1a2stxH/GdC0MV7D6xsTY3JVj5Y
=YHoo
-END PGP SIGNATURE-
--
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
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Patch] Make build environment consistent

[Ozkan Sezer]

On 10/16/16, David Wohlferd  wrote:
[...]
> config.guess files downloaded from the current automake build tree.
>
> sezero has been checking in these beta versions, but no one seems to
> know why (and he hasn't responded to explain).

There are no beta or release versions of config.guess/config.sub, they
just are what they are. The ones included in automake-1.15 just happen
to be current at the time automake-1.15 was released. I usually update
them from git://git.sv.gnu.org/config.git in all my projects.

There is no immediate benefit or harm in [not] doing so, although when
cross-compiling on a weird platform, it is good to have the latest.

I have no objections if you or anyone else wants to replace them with
the ones from automake-1.15.

--
O.S.

--
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
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

[Mingw-w64-public] [Patch] Make build environment consistent

[David Wohlferd]

I have a patch to bring all the mingw-w64 build files up to the latest 
version (1.15).  Due to size, it is at 
http://www.LimeGreenSocks.com/gen2.7z and is unchanged since I posted it 
back on Oct 2.  This patch is 100% regenerated files from running 
"autoreconf -fiv" in all the directories.  While the patch has been 
debated, no one has approved it yet.

As has been discussed (see 
https://sourceforge.net/p/mingw-w64/mailman/message/35418338/), there is 
some question about whether we should be using beta versions of the 
config.guess files downloaded from the current automake build tree.

sezero has been checking in these beta versions, but no one seems to 
know why (and he hasn't responded to explain).  To be clear, the files 
currently checked in to mingw-w64 are NEWER than the most recently 
released version of automake.  A review of the differences doesn't 
reveal any obvious benefit.

I'm asking that my current patch (which does NOT use the beta files) be 
approved.  If there is a reason to use the beta files, let's do that as 
a separate checkin, along with an explanation as to WHY we are doing it.

Ok to push?

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
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public