Re: [Mingw-w64-public] Fwd: [PATCH v1] setup: allow building with i686-w64-mingw32
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. There is one change to propkeydef.h, but and I believe incorrect. Generally, this patch makes REFIID and similar typedefs depend on CINTERFACE, which is not present in MSVC. Changing it is a serious danger for compatibility. Why is it needed? Jacek To clear things up, CINTERFACE is used for the style interface declaration, nothing to do with REFIID. In C++, it seems to be typical to use references rather than pointers to refer to IIDs, so hopefully Cygwin can fix the usage on their side. Ping, Yaakov. signature.asc Description: OpenPGP digital signature -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] specs file location
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 today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] specs file location
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.1. -John E. / TDM -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] specs file location
On Tue, Jun 5, 2012 at 10:21 PM, John E. / TDM tdra...@tdragon.net 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 sanity for MSYS. I've not tried a GCC build in a while though so I don't know the state of issues with the current process. -- Earnie -- https://sites.google.com/site/earnieboyd -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] specs file location
On 6/6/2012 7:18 AM, Earnie Boyd wrote: On Tue, Jun 5, 2012 at 10:21 PM, John E. / TDMtdra...@tdragon.net 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 sanity for MSYS. I've not tried a GCC build in a while though so I don't know the state of issues with the current process. What I mean is, MSYS' path translation can prevent the build-time machinery from making all paths relocatable, or has in the past. The build is still able to complete without any patches. -John E. / TDM -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
