Re: [Mingw-w64-public] [RFC] setup: allow building with i686-w64-mingw32

2012-08-30 Thread Ozkan Sezer
On 8/30/12, Yaakov (Cygwin/X) yselkow...@users.sourceforge.net wrote:
 On Fri, 2012-06-01 at 02:45 -0500, Yaakov (Cygwin/X) wrote:
 The attached draft patch fixes most of the issues with the build.  (I
 just added the necessary mingw64-i686-* libraries to Ports.)  ntdll.h
 needs some more work though; perhaps JonY could provide some input?

 Revised patches for mingw-w64-headers SVN HEAD attached.


 Yaakov

I applied the last winternals patch as obvious to both stable/v2.x (r5376)
and to trunk (r5377.)

--
O.S.

PS: Your work tree seems not up-to-date: patch applied with offsets.

--
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] [RFC] setup: allow building with i686-w64-mingw32

2012-08-30 Thread Yaakov (Cygwin/X)
On Thu, 2012-08-30 at 11:06 +0300, Ozkan Sezer wrote: 
 I applied the last winternals patch as obvious to both stable/v2.x (r5376)
 and to trunk (r5377.)

Thank you.

 PS: Your work tree seems not up-to-date: patch applied with offsets.

Simply a matter of applying patch 3 before patch 2 (which also touches
winternl.h).


Yaakov



--
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] mingw-w64 CRT is ABI compatible with CRT from the mingw.org project?

2012-08-30 Thread Earnie Boyd
On Wed, Aug 29, 2012 at 6:17 PM, JonY wrote:
 On 8/30/2012 05:58, niXman wrote:
 Hello,

 Can it be affirmed that mingw-w64 CRT built in 32 bit mode is ABI
 compatible with CRT from the mingw.org project?
 In other words, I am interested if there will appear problems when
 using boost(for example) built with the compiler from mingw.org in the
 project that uses the mingw-w64 CRT, and vice versa?
 Is there any difference how boost is built - dynamically or statically?



 No, it is not compatible. Do not mix compiled code between the 2.
 Dynamic or static will not matter.

You didn't say why; I assume it has to do with sjlj versus dwarf2, is
that correct?

-- 
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] mingw-w64 CRT is ABI compatible with CRT from the mingw.org project?

2012-08-30 Thread JonY
On 8/30/2012 19:29, Earnie Boyd wrote:
 On Wed, Aug 29, 2012 at 6:17 PM, JonY wrote:
 On 8/30/2012 05:58, niXman wrote:
 Hello,

 Can it be affirmed that mingw-w64 CRT built in 32 bit mode is ABI
 compatible with CRT from the mingw.org project?
 In other words, I am interested if there will appear problems when
 using boost(for example) built with the compiler from mingw.org in the
 project that uses the mingw-w64 CRT, and vice versa?
 Is there any difference how boost is built - dynamically or statically?



 No, it is not compatible. Do not mix compiled code between the 2.
 Dynamic or static will not matter.
 
 You didn't say why; I assume it has to do with sjlj versus dwarf2, is
 that correct?
 

Other than that, there were some differences in the C start up code as
well, at least the last time I tried. So the linker refused to link if
mixing libraries. You might get better chances with DLL import libraries
though.



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