On 6/6/2012 7:18 AM, Earnie Boyd wrote:
> On Tue, Jun 5, 2012 at 10:21 PM, John E. / TDM wrote:
>> (2) MSYS' path
>> translation can get in the way, or at least has gotten in the way for me in
>> the past when building GCC.
> When I was maintaining MSYS I wouldn't release it if GCC would not
> bui
On Tue, Jun 5, 2012 at 10:21 PM, John E. / TDM wrote:
> (2) MSYS' path
> translation can get in the way, or at least has gotten in the way for me in
> the past when building GCC.
When I was maintaining MSYS I wouldn't release it if GCC would not
build. Building the GCC package was my test of san
On 6/6/2012 4:20 AM, xunxun wrote:
> Hi John
>
>An off-list question
>
>GCC4.7.1 will be released soon. Will you build it for your new
> edition?
>
I've been working with 4.7.0 as time permits. If 4.7.1 is released
before I get a usable 4.7.0 build, then yes, I'll start working with 4.7.
Hi John
An off-list question
GCC4.7.1 will be released soon. Will you build it for your new edition?
--
Best Regards,
xunxun
--
Live Security Virtual Conference
Exclusive live event will cover all the ways tod
On 6/4/2012 18:00, JonY wrote:
> On 6/4/2012 17:04, Jacek Caban wrote:
>> On 06/03/12 17:45, JonY wrote:
>>> Forwarding to mingw-w64 list.
>>>
>>> Some of the headers modified is generated from WINE widl, so the
>>> preprocessor should be changed instead, jacek?
>>>
>>
>> Where? I don't see any. Th
